LIST OF ERROR AND WARNING MESSAGES

Author: Richard R. Carrillo, Seven Solutions S.L. <rcarrillo(AT)sevensols.com>
Website: http://www.ohwr.org
Website: http://www.sevensols.com
Revision: 1.2 (Last modifications: 6/5/2012)

This documents describes all the possible messages which can be reported during the execution of PTS of the FMC-DIO-5chTTLa board. These messages can reveal the cause of a test failure.


Error messages
--------------

DIOERR00: PRESENT line is not asserted in FMC. Is the fmc-dio-5chttla correctly inserted into the carrier?
The PRESENT line of the FMC connector is not asserted. This line is used to state that an adequate board in connected in the FMC connector of the SPEC board (carrier).
Possible causes:
-	FMC-DIO-5chTTLa-board is not correctly connected.
-	Faulty electrical connectivity in the PRESENT line circuit or FMC connector.
-	Incorrect FPGA configuration (bitstream file).

DIOERR01: I2C core is not enabled
The internal flags corresponding to the I2C core are not active.
Possible causes:
-	Incorrect FPGA configuration (bitstream file).

DIOERR02: No I2C device found
No device has responded to any address in the I2C bus.
Possible causes:
-	I2C bus is not working properly. Check for short-circuits in any of the bus lines.

DIOERR03: Device not found. Only x I2C devices found
The DAC or the EEPROM does not respond to their expected address.
Possible causes:
-	Wrong address configuration. If the number of devices found (x) is 3, check the list of devices (addresses) found in the generated log files. For those devices (addresses) which are not listed, check their address configuration lines (chip soldering and FMC GA0 and GA1 lines connectivity).
-	Faulty electrical connection. If the number of devices found (x) is less than 3, check the list of devices (addresses) found in the generated log files. For those devices (addresses) which are not listed, check their I2C lines and power pins (chip soldering).

I2C device EEPROM (24AA64T) at addr 0x50 produced the error: DIOERR04: Initializing: x
This error message is reserved for future uses.
Possible causes:
-	None

I2C device DAC (DAC5578) at addr 0x48 produced the error: DIOERR05: Initializing: x
The DAC did not respond correctly during the configuration process.
Possible causes:
-	An incorrect DAC IC is mounted.
-	Defective DAC IC soldering (I2C lines or power-supply pins of DAC).
The message x may give an extra clue about the error cause.

I2C device DAC (DAC5578) at addr 0x48 produced the error: DIOERR06: Setting channel value: x
The DAC did not respond correctly to the set-channel voltage commands.
Possible causes:
-	An incorrect DAC IC is mounted.
-	Defective DAC IC soldering (I2C lines or power-supply pins of DAC).
The message x may give an extra clue about the error cause.

Error in I2C bus. (Addr: x): DIOERR07: Device not initialized
The I2C-device access library has not been properly initialized. This error should never be reported when executing the original FMC-DIO-5chTTLa-board tests.
Possible causes:
-	Test-program programming bug.
-	An error during device initialization impedes its usage

I2C device DAC (DAC5578) at addr 0x48 produced the error: DIOERR08: Getting channel value: x
The DAC did not respond correctly to the get channel-voltage configuration commands.
Possible causes:
-	An incorrect DAC IC is mounted.
-	Defective DAC IC soldering (I2C lines or power-supply pins of DAC).
The message x may give an extra clue about the error cause.

Error in OneWire bus. (Addr: x): DIOERR09: Getting unique ID: y
The OneWire device DS1820 did not respond correctly during the process for obtaining the chip unique ID (first commands).
Possible causes:
-	An incorrect IC is mounted.
-	Defective chip soldering (OneWire line or power-supply pins of DS1820).
-	Electrical connectivity problems (short-circuits or open-circuits) in the OneWire line (FMC connector, OneWire pull-up resistors).
The message y may give an extra clue about the error cause.

Error in OneWire bus. (Addr: x): DIOERR10: Device not initialized
The OneWire-device access library has not been properly initialized. This error should never be reported when executing the original FMC-DIO-5chTTLa-board tests.
Possible causes:
-	Test-program programming bug.

Error in OneWire bus. (Addr: x): DIOERR11: Getting temperature: y
The OneWire device DS1820 did not respond correctly during the process for obtaining the temperature.
Possible causes:
-	An incorrect IC is mounted.
-	Defective chip soldering (OneWire line or power-supply pins of DS1820).
The message y may give an extra clue about the error cause.

Error in I2C bus. (Addr: x): DIOERR012: Device not initialized
The I2C EEPROM access library has not been properly initialized. This error should never be reported when executing the original FMC-DIO-5chTTLa-board tests.
Possible causes:
-	Test-program programming bug.

I2C device EEPROM (24AA64T) at addr 0x50 produced the error: DIOERR13: Writing memory data: x 
The EEPROM did not respond correctly to the write data commands.
Possible causes:
-	An incorrect EEPROM IC is mounted.
-	Defective EEPROM IC soldering (I2C lines or power-supply pins of EEPROM).
The message x may give an extra clue about the error cause.

I2C device EEPROM (24AA64T) at addr 0x50 produced the error: DIOERR14: Reading memory data: x 
The EEPROM did not respond correctly to the read data commands.
Possible causes:
-	An incorrect EEPROM IC is mounted.
-	Defective EEPROM IC soldering (I2C lines or power-supply pins of EEPROM).
The message x may give an extra clue about the error cause.


TSTERR00: Operation of fmc-dio-5chttla-board LEDs failed
The user answered “N” indicating that the FMC-DIO-5chTTLa-board LEDs did not operate properly.
Possible causes:
-	Soldering problems of the LED circuit (LED, current-limiting resistor or switch transistor).
-	Electrical connectivity problems in the LED activation lines of the FMC connector.

TSTERR01: Operation of fmc-dio-5chttla-board ports as output failed
The user answered “N” indicating that the FMC-DIO-5chTTLa-board ports did not provide the correct voltage to turn on and off the test-cable LEDs.
Possible causes:
-	Soldering problems (short-circuits and open-circuits) of the corresponding LEMO 00 connectors, corresponding lines (fuses) or voltage clamping components (short-circuits).
-	Soldering problems of the corresponding port driver IC and the LVDS-to-LVCMOS IC.
-	Electrical connectivity problems of the corresponding port control lines of the FMC connector.
Execute test06 to obtain more information which could be useful to isolate the problem.

TSTERR02: Proper voltage reading not obtained in ports: [x] when output enable=1
Apparently the voltage obtained in the ports x is out of the expected range when the port output is set to a high or low level. Alternatively, a misleading wrong voltage could have been measured due to a DAC or comparator operation problem.
Possible causes:
-	Something is connected to the LEMO-00 connectors of the ports. Ensure that nothing is connected to the ports while executing the corresponding test.
-	Soldering problems (short-circuits) of the corresponding LEMO-00 connectors, corresponding lines (fuses) or voltage clamping components.
-	Soldering problems of the corresponding port driver IC or the LVDS-to-LVCMOS IC.
-	Soldering problems of the DAC or the corresponding voltage comparator.
-	Electrical connectivity problems of the corresponding port control lines of the FMC connector.
-	An incorrect port current-driver IC is mounted.
Check the log files to obtain more information about what caused the error.
Check the results of this test to isolate the problem.

TSTERR03: Proper voltage reading not obtained in ports: [x] when output enable=0
Apparently the voltage obtained in the ports x is out of the expected range when the port output is set to a high level, the termination resistor is disabled and the output-enable circuit is disabled. Alternatively, a misleading wrong voltage could have been measured due to a DAC or comparator operation problem.
Possible causes:
-	Soldering problems of the corresponding port driver IC or the LVDS-to-LVCMOS IC.
-	Soldering problems of the DAC or the corresponding voltage comparator.
-	Electrical connectivity problems of the corresponding port control lines of the FMC connector.
Check the log files to obtain more information about what caused the error.
Check the results of test06 to isolate the problem.

TSTERR04: Proper voltage reading not obtained in ports: [x] when termination resistors enabled
Apparently the voltage obtained in the ports x is out of the expected range when the port output is set to a high level and the termination resistor is enabled. Alternatively, a misleading wrong voltage could have been measured due to a DAC or comparator operation problem.
Possible causes:
-	Something is connected to the LEMO-00 connectors of the ports. Ensure that nothing is connected to the ports while executing the corresponding test.
-	Soldering problems (short-circuits) of the corresponding LEMO-00 connectors, corresponding lines (fuses) or port input-voltage clamping components.
-	Soldering problems of the corresponding port driver IC or the LVDS-to-LVCMOS IC.
-	Soldering problems of the DAC or the corresponding voltage comparator.
-	Electrical connectivity problems of the corresponding port control lines of the FMC connector.
-	An incorrect port current-driver IC is mounted.
Check the log files to obtain more information about what caused the error.
Check the results of test06 to isolate the problem.

TSTERR05: No communication could be performed between any two ports
No communication could be established between any of the board ports (when the interconnection cables are plugged). That is, the test could not find a port working as input and another as output.
Possible causes:
-	The interconnection cables are not connected to the LEMO 00 ports while executing this test.
-	Soldering problems (short-circuits and open-circuits) of the corresponding LEMO 00 connectors, corresponding lines (fuses) or voltage clamping components (short-circuits).
-	Soldering problems of the corresponding port driver IC or the LVDS-to-LVCMOS IC.
-	Soldering problems of the DAC or the corresponding voltage comparator.
-	Electrical connectivity problems of the corresponding port control lines of the FMC connector.
Check the log files to obtain more information about what caused the error.

TSTERR06: Ports x appear no to be correctly connected
No communication could be established through ports x (when the interconnection cables are plugged). That is, the test could use ports x neither as input nor output to communicate with the rest of the ports.
Possible causes:
-	Some of the interconnection cables are not correctly connected to the LEMO 00 ports while executing the corresponding test.
-	Soldering problems (open-circuits) of the corresponding LEMO 00 connectors or corresponding lines (fuses).
-	Soldering problems of the corresponding port driver IC or the LVDS-to-LVCMOS IC.
-	Soldering problems of the DAC or the corresponding voltage comparator.
-	Electrical connectivity problems of the corresponding port control lines of the FMC connector.
Check the log files to obtain more information about what caused the error.

TSTERR07: Correct data not read when verifying EEPROM writting operation
Possible causes:
-	An incorrect EEPROM IC is mounted.
-	Defective EEPROM or IC soldering (I2C lines or power-supply pins of EEPROM).


Warning messages
----------------

TSTWRN00: Strangely-low voltage value obtained in ports: [x] when output=1
Apparently the voltage measured in the ports x is unusually low (but still within the operating range) when the port output is set to a high level.
Possible causes:
-	Something is connected to the LEMO-00 connectors of the ports. Ensure that nothing is connected to the ports while executing the corresponding test.
-	Soldering problems of the termination-resistor activation circuit (switching transistor)
-	Electrical connectivity problems of the corresponding port termination-resistor control lines of the FMC connector.
-	An incorrect port current-driver IC is mounted.
Check the log files to obtain more information about what caused the error.

TSTWRN01: Strangely-high voltage value obtained in ports: [x] when output=0
Apparently the voltage measured in the ports x is unusually high (but still within the operating range) when the port output is set to a low level.
Possible causes:
-	Electrical connectivity problems of the corresponding port control lines of the FMC connector.
-	An incorrect port current-driver IC is mounted.
Check the log files to obtain more information about what caused the error.

TSTWRN02: Strangely-high voltage value obtained in ports: [x] when output enable=0
Apparently the voltage measured in the ports x is unusually high (but still within the operating range) when the port output-enable circuit is disabled.
Possible causes:
-	Electrical connectivity problems of the corresponding port control lines of the FMC connector.
-	An incorrect port current-driver IC is mounted.
Check the log files to obtain more information about what caused the error.

TSTWRN03: Strangely-low voltage value obtained in ports: [x] when termination resistors enabled
Apparently the voltage measured in the ports x is unusually low (but still within the operating range) when the port output is set to a high level and the termination resistor is enabled.
Possible causes:
-	Something is connected to the LEMO-00 connectors of the ports. Ensure that nothing is connected to the ports while executing the corresponding test.
-	Electrical connectivity problems of the corresponding port termination-resistor control lines of the FMC connector.
-	An incorrect port current-driver IC is mounted.
Check the log files to obtain more information about what caused the error.

TSTWRN04: Strangely-high voltage value obtained in ports: [x] when termination resistors enabled
Apparently the voltage measured in the ports x is unusually high (but still within the operating range) when the port output is set to a high level and the termination resistor is enabled.
Possible causes:
-	Soldering problems of the termination-resistor activation circuit (switching transistor or resistors)
-	An incorrect port current-driver IC is mounted.
Check the log files to obtain more information about what caused the error.

TSTWRN05: Strange temperature value measured
Apparently the temperature measured through the OneWire temperature acquisition I.C. is out of a reasonable range.
Possible causes:
-	The test is run in extreme temperature conditions.
-	Board overheating.
-	Faulty temperature acquisition I.C.
Check the log files to obtain the concrete temperature value measured.
