Motorola MVME162P-242, Installation And Use Manual

Page: 63 / 134

162Bug Implementation
http://www.motorola.com/computer/literature 3-3
3
If you have used one or more of Motorola’s other debugging packages, you
will find the CISC 162Bug very similar. Some effort has also been made
to improve the consistency of interactive commands. For example,
delimiters between commands and arguments may be commas or spaces
interchangeably.
162Bug Implementation
Physically, 162Bug is contained in a single 27C040 DIP EPROM installed
in socket XU2, providing 512KB (128K longwords) of storage.
Optionally, the 162Bug firmware can be loaded and executed in a
28F016SA Flash memory chip. The executable code is checksummed at
every power-on or reset firmware entry, and the result (which includes a
precalculated checksum contained in the memory devices) is tested for an
expected zero. Users are cautioned against modification of the memory
devices unless precautions for re-checksumming are taken.
Note MVME162P2 boards ordered without the VMEbus interface
are shipped with Flash memory blank (the factory uses the
VMEbus to program the Flash memory with debugger code).
To use the 162Bug package, be sure that switch S4 segment
5 is configured to select the EPROM memory map.
If you subsequently wish to run the debugger from Flash
memory, you must first initialize Flash memory with the
PFLASH command, then reconfigure S4. Refer to Step 14
(Note) under
Bringing up the Board on page 2-5 for further
details.