Debugger General Information
SYSFAIL* Assertion/Negation
| Upon a reset/power up condition the debugger asserts the VMEbus SYSFAIL* | ||
| line (refer to the VMEbus specification). SYSFAIL* stays asserted if any of the | ||
3 | |||
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
After debugger initialization is done and any of the above situations has not occurred, the SYSFAIL* line is negated. This indicates to the user or VMEbus masters the state of the debugger. In a
MPU Clock Speed Calculation
The clock speed of the microprocessor is calculated and checked against a user definable parameter housed in NVRAM (refer to the ENV command). If the check fails, a warning message is displayed. The calculated clock speed is also checked against known clock speeds and tolerances.
Memory Requirements
The program portion of 197Bug is approximately 1 megabyte of code, consisting of download, debugger, and diagnostic packages and contained entirely in the flash memory. The flash memory on the MVME197LE is mapped starting at location $FF800000.
197Bug requires a minimum of 64KB of contiguous read/write memory to operate.
The ENV command controls where this block of memory is located. Regardless of where the onboard RAM is located, the first 64KB is used for 197Bug stack and static variable space and the rest is reserved as user space. Whenever the MVME197LE is reset, the target IP is initialized to the address corresponding to the beginning of the user space, and the target stack pointers are initialized to addresses within the user space, with the target Pseudo Stack Pointer (R31) set to the top of the user space.
Installation Guide |
