• Topic ID: id_18718239
  • Version: 1.0
  • Date: Sep 20, 2018 2:05:01 PM

GDAS(4/8) Power-Up Diagnostics

Whenever power is turned on to the DAS or a DAS Reset is performed, the DAS runs a series of Power-Up diagnostics. The sequence of tests is as follows.

DAS / DCB BOOT SEQUENCE AFTER POWER-ON OR RESET

  1. MCU Initialization

  2. RAM Test

  3. Boot Flash CRC Test

  4. Application CRC/size Test

  5. Load the code into RAM (Application code from Flash)

  6. Start the Application code

Once Application code is booted successfully in the DCB, then the DCB establishes itself with the ORPand the DAS Converter boards in the following sequence of initialization and tests:

  1. Platform Software and Hardware Driver initialization.

  2. DCB Hardware self-tests.

  3. Initialize Application Hardware and communication tasks.

  4. Initializes Converter boards, 2 boards at a time, and does this 6 times. This is when the Converter board LEDs flash several short times in sequence from board 1 through 48. The Converter board initialization consists of:

    • Converter board access (Read/writes)

    • Initialization

    • Reading of EEPROM

    • Set of Temperature sensors

    • Setting of Offset Trim

    • Calibration

    • Fault line test

  5. When all the converter boards are initialized, the DCB performs the following tasks:

    • Updates configure Tracker and version verification data

    • Reads Converter board temperature tests

    • Runs a quick data path test (2 views worth of data)

  6. Ready to Interface with ORP.

In an error condition, the error is reported to the DCB, if possible (depending on the type of fault). The DCB then relays the information to the ORP, and finally to the system error log. If the DCB is at fault and cannot communicate with the ORP, then a DAS Communication Error is logged.