GSi TYMPSTAR 1, Service Manual

Page: 205 / 224

Troubleshooting
CP Error codes
3303 ABORT_HW_SEREE_WAIT_FOR_ACK SEREE never acknowledged request for write
Subcodes: none
Likely Causes: As each byte is shifted out to the EE, the CP
software checks to ensure that the EE is ready to accept a
write request. The most likely cause for this would be a
faulty EE or a problem with the data/control lines that run
from the EE on the probe to the Digital board. Noise on
these lines would also be a problem.
3304 ABORT_HW_SEREE_NACK EE NACKed the previous byte write.
Subcodes: none
Likely Causes: As each byte is shifted out to the EE, the CP
software checks the ACK line to ensure that writes are
proceeding correctly. The most likely cause for this would be
a faulty EE, or problems with the data/control lines that run
from the EE on the probe to the Digital board. Noise on
these lines would also be a problem.
3306 ABORT_HW_SEREE_PROBE_VER_INCOMPAT Probe EE was incompatible version - could not upgrade.
Subcodes: current probe ver #
Likely Causes: An unknown probe version has been attached
to the TympStar. For example, a future release 3 probe
attached to a release 2 system. The release 2 system cannot
upgrade this format probe. A probe with bad data could
result in this failsafe, but only if it managed to get through the
probe-present check and hamming code to ensure that the
integrity of the EE was good.
3400 ABORT_KEY_NEWSK_SETOPMODE_SEREE Fetch of Serial EE shadow took too long
Subcodes: none
Likely Causes: A maximum time of 30 seconds is put on the
probe EE shadow read. This code can indicate a large
number of retries with the SEREE read and can indicate a
problem with the EE or the data/control path back to the CP
(including noise that may be causing retried reads). Less
likely is a software problem that sees the shadow read task
failing and this would indicate an internal software failure.
GSI TympStar Version 1 and Version 2 Service Manual 8 - 15