GSi TYMPSTAR 1, Руководство по обслуживанию

Страница: 200 / 224

Chapter 8
CP Error codes
2300 ABORT_FPGA_PROGRAM_READBACK_FAIL FPGA Failed to program correctly.
Subcodes: none
Likely Causes: During bootup, the CP software reads the
FPGA.BIN file from disk and programs the FPGA one byte
at a time (through the parallel port). At the end of the
programming sequence, a known special byte pattern is
requested from the FPGA; if this fails, the FPGA is not
running. Possible causes are faulty FPGA hardware, a
bad connection between the FPGA on the digital board and
the PC104 (there is a ribbon cable that runs between them).
It could also be a faulty FPGA.BIN file on the disk but that is
less likely.
2302 ABORT_FPGA_PROGRAM_STATUS_FAIL2 FPGA indicating bitstream failure during writing of
FPGA.BIN.
Subcodes: none
Likely Causes: The FPGA is programmed one byte at a time
by the CP software. During the programming, after each byte
is written the status line is checked to ensure that the FPGA is
still accepting data. If the FPGA status indicates it is not still
programming, this error code is generated. The most likely
problem is a faulty FPGA or the entire parallel data path from
the PC104 to the FPGA (there is a ribbon cable that runs
between them).
2400 ABORT_DAT_BAD_READ_ITEM Data read item invalid
Subcodes: none
Likely Causes: The data file system was asked to read an
item that it does not recognize. There is a look-up table that
describes all of the possible data read/write items (both to
binary files on the disk, INI files on the disk and to SEREE
on the probe). If the software requests access to an item that
is not listed in the look-up table, this failure occurs. The
most likely cause is an internal CP software failure or
possibly a corrupt memory/stack.
2401 ABORT_DAT_BAD_WRITE_ITEM Data write item invalid
Subcodes: none
Likely Causes: The data file system was asked to read an
item that it does not recognize. There is a look-up table that
describes all of the possible data read/write items (both to
binary files on the disk, INI files on the disk and to SEREE
on the probe). If the software requests access to an item that
is not listed in the look-up table, this failure occurs. The
most likely cause is an internal CP software failure or
possibly a corrupt memory/stack.
2402 ABORT_DAT_WRITE_ITEM_FAIL Data write item failed
Subcodes: none
Likely Causes: A low level write to the disc has failed. This
can occur if the DOC has filled, or there is a problem with the
DOC on the PC104. The PharLap OS provides the file
handling, so any software error here would be located in the
OS kernel for file access, and is very unlikely.
Grason-Stadler
8 - 10