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