MPCBL0050N02Q Intel, MPCBL0050N02Q Datasheet - Page 228

• Manufacturer Part Number: MPCBL0050N02Q
• Manufacturer: Intel

Specifications of MPCBL0050N02Q

• Lead Free Status / RoHS Status: Supplier Unconfirmed

Table 78.
Intel NetStructure
Technical Product Specification
228
®
Warning and error messages (Sheet 7 of 11)
E749
E751
E752
E753
E754
E755
E756
E757
E758
E759
E760
E761
E762
Number
MPCBL0050 Single Board Computer
File %1 cannot be opened: %2.
Unknown hex record type encountered
at line %1.
Hex record checksum incorrect at line
%1.
Unable to allocate memory while parsing
file.
No EOF hex record found. Supplied file
appears to be corrupt.
Unknown open failure for file %1.
The supplied file has an unsupported
opcode header version (%1).
The supplied file does not contain a valid
operational code header.
Invalid record length encountered at line
%1.
Errors occurred while running
prechecks. Aborting.
The specified file %1 is an unknown file
type.
Staged FRU updates are not supported.
Cannot downgrade the firmware from
version %1 to version %2 without the
--force-fw-update flag.
Message
This error message is displayed if the provided
filename cannot be opened. Examples are the file is
missing or permissions are insufficient. %1 is replaced
with the supplied filename, and %2 is replaced with the
error.
This error message is displayed if the supplied file
contains a record not conforming to the HEX record
standard for Intel. This could indicate that the supplied
file is corrupt. %1 is replaced by the line number in the
file where the bad record was found.
This error message is displayed if the two’s
complement checksum of the hex record line does not
match the line’s checksum. This format is defined by
the HEX record standard for Intel. This could indicate
the supplied file is corrupt. %1 is replaced by the line
number in the file where the bad record was found.
This error message is displayed when the supplied
filename is being read into memory, and the operating
system runs out of available memory. This indicates
that the client machine is running a large program, or
may be running a program with a memory leak.
This error message is displayed when the supplied file
has no HEX EOF (end-of-file) record. This is defined by
the HEX record standard for Intel. This could indicate
the supplied file is corrupt.
This error message is displayed when an unknown
error occurs while attempting to open the supplied file.
This message is the last catch-all message to detect
unknown failures. %1 is replaced with the supplied
filename.
This error message is displayed if the supplied filename
contains a data format for the operational code that is
not supported. The data format could differ when
major enhancements are made to the operational
image. %1 is replaced with the opcode header version
that was found in the supplied file.
This error message is displayed if the header portion of
the operational code image cannot be found. This could
indicate the supplied file is corrupt.
This error message is displayed if the HEX record
specifies a certain length for a record, but the data
does not match that length. This could indicate the
supplied file is corrupt.
This error message is displayed if all other known
checks and messages cannot catch the error. This
message should not be seen in practical operation.
This error message is displayed if a file is specified that
has an unknown file extension. Valid file extensions
are: .hex, .cfg, .fru, .bsdr, and.bfru.
This error message is displayed if an FRU update is
being performed, and the mode is staged.
This flag is required to show the user's intention to
downgrade the firmware. If this is really the intended
operation, supply the switch and this error no longer
appears.
MPCBL0050—Firmware Update Utilities
Description
Order Number: 318146-001
September 2007