User guide

86 DC 900-1338I
Protocol Software Toolkit Programmer Guide
Press <ctrl>C to exit this mode.
Type one of the following commands, depending on which ICP you are using.
SingleStep displays a few messages, followed by “Reset complete.”
SingleStep> debug -p /dev/ttya=9600 -N sps24.lo
SingleStep> debug -p /dev/ttya=9600 -N sps32.lo
SingleStep> debug -p /dev/ttya=9600 -N sps60.lo
If you are working on a PC, type one of the following commands, depending on which
ICP you are using:
SingleStep> debug -p com1=9600 -N sps24.lo
SingleStep> debug -p com1=9600 -N sps32.lo
SingleStep> debug -p com1=9600 -N sps60.lo
(You must have a terminal emulation program in order to have I/O through the serial
port.)
After “Reset complete” has been displayed, all SingleStep commands can be used. For
example, type the following command at the SingleStep prompt to show the source for
start.s:
SingleStep> where
Consult the SingleStep Debugger for the 68000 Microprocessor Family manual for com-
plete instructions on commands, aliases, and so on.
5.4 System Panic Codes
The OS/Impact system software generates an illegal instruction trap (using the ILLE-
GAL
instruction) when it encounters a non-recoverable error condition. Before execut-
ing the
ILLEGAL instruction, the operating system stores a “panic code” in the gs_panic
field of the global system table. The format and location of the global system table is
described in the OS/Impact Programmer Guide, and Appendix A in that document
describes the OS/Impact panic codes.