GSi TYMPSTAR 1, Service Manual

Page: 197 / 224

Troubleshooting
CP Error codes
1202 ABORT_SP_FAILED_TO_RUN SP never started running after reset.
Subcodes: none
Likely Cause: When the system is first booted, the DPRAM
is enabled and the SP is taken out of reset (i.e. initialized).
We can detect the SP state of being initialized since the SP
writes to key DPRAM locations that we monitor. If the SP
does not initialize, there could be an internal SP problem or
the hardware path between the SP and CP could be faulty.
1203 ABORT_SP_TIMEOUT_ON_CMD_WAIT Timeout on wait for SP to complete current “blocking”
command.
Subcodes: none
Likely Cause: There are numerous commands that travel
between the CP and SP; if the SP is not responding for any
reason this error code will likely occur. It is most likely a
problem with the SP itself (for example, if the SP gets reset
by high-current power spike) or with a faulty hardware path
between the SP and CP.
1300 ABORT_INST_OPT_BAD_CTSRTS_STATE Instrument Options - CTS/RTS selection invalid.
Subcodes: none
Likely Cause: This is an internal check for the CTS/RTS menu
handler. The user should never be allowed to select any
CTS/RTS choice except those presented on screen, so this
indicates an internal software failure.
1400 ABORT_MNU_INVALID_KEYCODE Menu handler - invalid (non soft-key) keycode received.
Subcodes: keycode
Likely Causes: This is an internal check for the softkey value
passed into the main CP menu handler. This key is expected
to be one of the 6 softkeys (SK1-SK6) and if it is another
hardkey, it should have been handled previously. This
indicates an internal software failure.
1401 ABORT_MNU_INVALID_REPEAT Menu handler - invalid key status (repeat key detected)
Subcodes: keycode
Likely Causes: Repeated softkeys are handled at different
layers. The menu handler does not deal with repeated keys
and so will failsafe with this code should a repeat key be
passed to it. This indicates an internal software failure.
1500 ABORT_TESTTSK_INVALID_MSG An invalid message type was received by the test task
scheduler.
Subcodes: message type
Likely Causes: This error occurs when the Test Task receives
a message request that it cannot process. There is a software
look-up table of test procedures that can be run as part of a
test task, if a request comes in to run something that is not on
this list, this failsafe will occur. This is an internal check and
indicates an internal software failure. It is also possible that
either the Test Task or the calling task have corrupted stack
memory that led to this error. It is also possible that the
PharLap tasking code has errored, but this is less likely.
1600 ABORT_PAGE_NOT_AVAIL Page - try to store a test but no pages available in memory.
Subcodes:
0 = num_free_pages = 0
1 = num_free_pages > 0 but all pages indicate already data
stored.
Likely Causes: This is an internal check; problems indicate
an internal software failure. Corrupted CP memory could also
account for this.
GSI TympStar Version 1 and Version 2 Service Manual 8 - 7