Table of Contents
Advertisement
Restarting the System
You can initialize the system to a known state in three different ways:
reset, abort, and break. Each has characteristics which make it more
appropriate than the others in certain situations.
The debugger has a special feature upon a reset condition. This feature is
activated by depressing the RESET and ABORT switches at the same
time. This feature instructs the debugger to use the default setup/operation
parameters in ROM versus your setup/operation parameters in NVRAM.
This feature can be used in the event your setup/operation parameters are
corrupted or do not meet a sanity check. Refer to the ENV command
(Appendix A) for the ROM defaults.
Reset
!
When the RESET button on the controller is depressed for an
extended length of time (varies from board to board), DRAM refresh
Caution
may be inhibited and memory contents may be lost. To ensure that the
contents of DRAM will not be altered, press and release the RESET
button as quickly as possible.
Pressing and releasing the controller's front panel RESET switch initiates
a system reset. COLD and WARM reset modes are available. By default,
the 162Bug is in COLD mode. During COLD reset, a total system
initialization takes place, as if the controller had just been powered up. All
static variables (including disk device and controller parameters) are
restored to their default states. The breakpoint table and offset registers are
cleared. The target registers are invalidated. Input and output character
queues are cleared. Onboard devices (timer, serial ports, etc.) are reset, and
the two serial ports are reconfigured to their default state.
During WARM reset, the 162Bug variables and tables are preserved, as
well as the target state registers and breakpoints.
Reset must be used if the processor ever halts, or if the 162Bug
environment is ever lost (vector table is destroyed, stack corrupted, etc.).
http://www.mcg.mot.com/literature
Restarting the System
3-9
3
Advertisement
Table of Contents
