Someone recently pointed me to this link:
While a good start, it is only about 1/3 of the possible error codes that you can see on a Motorola DCT. Here, then, is the complete list:
General Error codes:
These errors will display at boot time (in the case of a failure) or can also be seen by launching the OSD and selecting 'd 01 General Status'. Error codes display on the LED and the OSD. In the case of multiple errors, the last error logged is displayed:
EP00 No error
EP01 Not connected
EP03 DRAM error
EP04 SRAM error
EP07 ROM verification failure
EP08 RAM test failure
EP09 Battery test failure
EP11 Invalid unit address
EP12 Power on self test failure
EP14 GITV startup failure
EP15 TSI structure corrupt
EP18 Driver initialization failure
Download error codes and informationals:
The following are displayed on the front panel LEDs of the set-top during and just after the code download process.
"| dl" This display indicates that an out-of band platform code object download is in progress. The first segment in the display is a crawling ant progress indicator, which moves one position for each segment of the platform code received.
"EF" This display indicates that the flash memory area is being erased.
"FP" This display indicates that the flash memory area is being programmed.
"----" This display indicates that a network platform code object download has completed.
"hunt" This display indicates that the bootloader is hunting for an out-of-band frequency.
"Fr [number]" This display indicates that the bootloader is attempting to lock on to the frequency indicated by [number].
"Au" This display indicates that a platform code is being authenticated after it has been downloaded.
The following are error codes that can be displayed if there is a problem with the download:
Eb01 The platform code object failed a validation check, before being loaded into the flash memory area from RAM.
Eb02 The platform code object download failed due to a time out or other failure.
Eb03 The bootloader failed to erase the flash memory area.
Eb04 The bootloader failed to program the flash memory area.
Eb05 Invalid Frequency. The frequency specified in the download control message is invalid. If an upgrade download was attempted, the invalid frequency encountered was read from the Startup-Database.
Eb06 Hardware initialization failed.
Eb07 The platform code object failed a validation check, after it was loaded into the flash memory area.
Eb08 This is a reserved error code.
Eb09 A sanity check failure has occurred. The code execution check bit for the loader flags field was not cleared.
Eb10 The start up database in NVMEM did not pass the CRC check, and was rebuilt to the default state. This error only occurs if both the primary and secondary copy of the start up database has been corrupted.
Eb11 The bootloader failed to lock the out-of-band tuner.
Eb12 The bootloader failed to receive a conditional access message.
Eb13 The bootloader failed to receive a download control message or no matching Platform ID entry found.
Eb14 An attempt to load a platform code object with the wrong object class or object type.
Eb15 No matching platform ID was found.
Eb16 An unexpected flash memory erasure or program was in progress at start up.
Eb17 The flash memory area is not responding.
Eb18 The platform code object size is mismatched.
Eb19 The platform object size failed the range check.
Eb20 The start up database pointer is not located within the appropriate NVMEM range, or the pointer does not lie on a 32-bit boundary.
Note: A number of these error codes indicate a problem at the headend and should almost never be seen in the field.