3-10
Computer Group Literature Center Web Site
Debugger General Information
3
Abort
Abort is invoked by pressing and releasing the ABORT switch on the
controller’s front panel. Whenever Abort is invoked when executing a user
program (running target code), a "snapshot" of the processor state is
captured and stored in the target registers. For this reason, abort is most
appropriate when terminating a user program that is being debugged.
Abort should be used to regain control if the program gets caught in a loop,
etc. The target PC, register contents, etc., help to pinpoint the malfunction.
Pressing and releasing the ABORT switch generates a local board
condition which may interrupt the processor if enabled. The target
registers, reflecting the machine state at the time the ABORT switch was
pressed, are displayed on the screen. Any breakpoints installed in your
code are removed and the breakpoint table remains intact. Control is
returned to the debugger.
Break
A "Break" is generated by pressing and releasing the BREAK key on the
terminal keyboard. Break does not generate an interrupt. The only time
break is recognized is when characters are sent or received by the console
port. Break removes any breakpoints in your code and keeps the
breakpoint table intact. Break also takes a snapshot of the machine state if
the function was entered using SYSCALL. This machine state is then
accessible to you for diagnostic purposes.
Many times it may be desirable to terminate a debugger command prior to
its completion; for example, during the display of a large block of memory.
Break allows you to terminate the command.
SYSFAIL* Assertion/Negation
Upon a reset/powerup condition the debugger asserts the VMEbus
SYSFAIL* line (refer to the VMEbus specification). SYSFAIL* stays
asserted if any of the following has occurred:
❏
confidence test failure
❏
NVRAM checksum error
❏
NVRAM low battery condition
❏
local memory configuration status
❏
self test (if system mode) has completed with error
❏
MPU clock speed calculation failure
Summary of Contents for MVME162LX 200 Series
Page 1: ...MVME162LX 200 300 Series Embedded Controller Installation and Use V162LX2 3A IH3 ...
Page 6: ......
Page 14: ...xiv ...
Page 66: ...1 52 Computer Group Literature Center Web Site Board Level Hardware Description 1 ...
Page 84: ...2 18 Computer Group Literature Center Web Site Hardware Preparation and Installation 2 ...
Page 108: ...3 24 Computer Group Literature Center Web Site Debugger General Information 3 ...
Page 158: ...C 2 Computer Group Literature Center Web Site C ...
Page 164: ...Ethernet Interconnections E 2 Computer Group Literature Center Web Site E ...
Page 200: ...J 4 Computer Group Literature Center Web Site J ...
Page 208: ...Index IN 8 Computer Group Literature Center Web Site I N D E X ...