2-4 Computer Group Literature Center Web Site
Startup and Operation
2
During cold resets, these system initialization processes occur, as if the
MBX had just been powered up:
❏ All static variables are restored to their default states.
❏ Breakpoint table and offset registers are cleared.
❏ Target registers are invalidated.
❏ Input and output character queues are cleared.
❏ On-board devices are reset, and the console/terminal serial port is
reconfigured to its default state.
During warm resets, the EPPCBug variables and tables are preserved, as
are the target state registers and breakpoints.
Note Early revisions of the EPPCBug firmware do not support the
“warm” reset feature.
You need to reset the system if the processor ever halts or if the EPPCBug
environment is ever lost (vector table destroyed, stack corrupted, etc.).
Break
Occasionally, you may wish to terminate a debugger command before its
completion (for example, during the display of a large block of memory).
A break allows you to terminate the command.
To invoke a break, press and release the BREAK key on the terminal
keyboard. Breaks do not generate an interrupt. A break is only recognized
when characters are sent or received by the console port. A break removes
any breakpoints in the user code and keeps the breakpoint table intact. A
break also takes a snapshot of the machine state if the function was entered
using an EPPCBug system call (see the EPPCBug Firmware Package
User’s Manual listed in Appendix B, Related Documentation). This
machine state is then accessible to you for diagnostic purposes.
For details on the firmware or the programming aspects of the MBX series
embedded controller, refer to the EPPCBug Firmware Package User’s
Manual or to the MBX Series Embedded Controller Version B
Programmer’s Reference Guide respectively.
To Next Page
Loading...
Need help?
General
