Skip to end of banner
Go to start of banner

Firmware validation for LFW(Protocol stacks) and APP-FW --Troubleshooting guide if MFW failed to start an updated firmware

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Q

MFW (Maintenance Firmware) is responsible for firmware updates. Before MFW installs the new firmware, it will verify the device header of the new firmware(*.nxi, *.nai or fwupdate.zip) based on the information on the hardware device. If the information on your hardware matches firmware device header information, the new firmware will be installed and then be started automatically. Otherweise, MFW will refuse to install the firmware with an error code. The system led will turn yellow. After power-on reset, the old firmware will start again.

A

The following four fields on the hardware device will be validated against firmware device header. The information are defined in FDL (flash device label)  and HWC (hardware configuration) on your device.

  • Manufacturer
  • Device Class
  • Hardware Compatibility
  • Hardware Assembly Options

The first three fields are defined in Basic Device Data of your FDL file.

The Hardware assembly Options are configured in your HWC file.

Validation for LFW (Protocol stacks)

Edit Device Header in netX Tag List Editor

Validation for APP-FW (user application)

Device Info are defined in "netx90_app_header.c" of your application.

  • No labels