Table of Contents
Advertisement
Issue
Burning tool fails with the following error:
-E- Burning FS3 image failed: The component is
not signed.
Burning tool fails with the following error:
-E- Burning FS3 image failed: Rejected
authentication.
Burning tool fails with the following error:
-E- Burning FS3 image failed: Component is not
applicable.
Burning tool fails with the following error:
-E- Burning FS3 image failed: The FW image is
not secured.
Burning tool fails with the following error:
-E- Burning FS3 image failed: There is no Debug
Token installed.
Burning firmware on a secure device fails with
one of the following messages:
•
-E- Burning FS3 image failed: Rejected
authentication
•
The FW image is not secured
•
The key is not applicable
Secure Firmware fails when using mstflint
brom and drom commands.
When the CR space is in read only mode, the
tracers may demonstrate an unexpected
behavior.
Applying token on the device fails with one of
the following messages:
•
Component is not applicable
•
The manufacturing base MAC was not
listed
•
Mismatch FW version
•
Mismatch user timestamp
•
Rejected forbidden version
Burning the firmware using the "--
use_dev_rom" flag has no effect and the ROM
is replaced with the one on the image.
Cause
The image is not signed with an RSA
authentication.
The image authentication is
rejected.
The image does not match the
device (Wrong ID).
The image is not secured and is not
accepted by the device.
The debug firmware was burnt
before the debug token was
installed on the device.
The image was not secured in a the
proper way.
mstflint brom and drom commands
are not supported.
A writing permission is required for
them to work properly.
The token was not generated or
signed in the proper way.
Controlled firmware does not
support changing boot image
component.
Solution
Contact Support to
receive a signed
firmware image.
Contact Support
to
receive a signed
firmware image.
Contact Support
to
receive the firmware
image for the device.
Contact Support
to
receive a signed
firmware image.
Install the debug
token using mstconfig
and then re-burn the
firmware.
Ask for a secure
image with the right
keys that match the
device.
N/A
N/A
Generate and sign
tokens.
Use "--no_fw_ctrl".
90
Advertisement
Table of Contents
