|
8
|
Directory creation error
|
Reprogramming could not create a directory on the internal file
system. User should try again, but the session may fail again.
|
|
12
|
Missing update file
|
Check that all update files have been correctly saved to the
USB drive (all files listed in ManifestFile.sdm should be on the drive
in their proper path).
|
|
14
|
File read error
|
Reprogramming was not able to read one of the update files.
Check for file corruption when the files were saved to the USB drive.
|
|
16
|
File write error
|
Reprogramming was not able to write one of the update files
to internal flash. File system cleanup problem, reboot the display
and try again.
|
|
37
|
Invalid file handle
|
Reprogramming received a file handle that was not valid, check
validity of USB drive to make sure it matches the original image.
|
|
44
|
Checksum failed
|
Reprogramming calculated a checksum that did not match the expected
checksum. Check that all files match the original image.
|
|
45
|
Controller file invalid
|
Reprogramming parsed a file for a PF controller that was invalid.
Check that all files match the original image.
|
|
47
|
Incompatible hardware
|
Customer is using an incorrect hardware revision version as
the reprogramming image for the display. Make sure you have the correct
image for the display hardware.
|
|
48
|
Update file invalid
|
The reprogramming ManifestFile.sdm file has been corrupted.
Make sure the file matches the original image.
|
|
51
|
User aborted
|
User removed the USB drive during a reprogramming session. Repeat
the reprogramming process with the drive inserted the entire session.
|
|
55
|
Controller flash erase failed
|
A PF controller could not erase its flash memory.
|
|
56
|
Message missing colon
|
A PF controller received a record that was missing a colon.
Customer could try reprogramming the controller again in case of a
bus error.
|
|
57
|
Record too long
|
A PF controller received a record that was too long. Customer
could try reprogramming the controller again in case of a bus error.
|
|
58
|
Invalid record length
|
A PF controller received a record that was not the expected
length. Customer could try reprogramming the controller again in case
of a bus error.
|
|
59
|
Sequence error
|
A PF controller received a record that was out of the expected
sequence. Customer could try reprogramming the controller again in
case of a bus error.
|
|
60
|
Controller received odd address
|
A PF controller received a record that had an invalid address.
Customer could try reprogramming the controller again in case of a
bus error.
|
|
61
|
Controller timed out
|
A PF controller stopped responding to the display during a reprogramming
session. Check connection to the controller, may require a power cycle.
If communication is resumed, repeat the reprogramming session.
|
|
62
|
NOR flash reprogramming problem
|
There was an error with trying to reprogram the NOR flash boot
application image.
|
|
63
|
Unknown controller response
|
A PF controller returned a response that the display did not
know how to interpret.
|
|
81
|
Reprogramming session failed
|
Generic notification that some part of the reprogramming session
failed. Another error will be reported in addition to this one to
indicate the specific failure mode.
|