Firmware update

How is a running loadable firmware on COM-side (LFW - .nxi file) or APP-side (*.nai file) replaced by a newer version in the field?

The following steps are necessary

1. Transfer new firmware (*.nxi file and/or *.nai file) to netX 90
2. Store the new fimware binary in a flash memory
3. Trigger the start of the maintenance firmware - MFW - (alternative firmware)
4. The maintenance firmware installs the new loadable firmware on COM-side (LFW - .nxi file) and/or APP-side (*.nai file). I.e. the old firmware is updated.
5. The maintenance firmware reboot the netX90 and the new LFW is started

1) Transfer of new firmware to netX 90

The new firmware can be transferred through

1. HTTP protocol over the network (Ethernet), using the basic webserver functionality of a running LFW
2. Custom TCP/IP based protocol over the network (Ethernet), using the socket interface functionality of a running LFW
3. From an external Host-Controller, via the host interface - HIF: parallel DPM or serial SPM (SPI)
   using the cifX API function xChannelDownload() or the underlaying mailbox packet service "HIL_FILE_DOWNLOAD_REQ"
   in this case the host application communicates with a running LFW or the MFW on COM-side
4. From the APP-side of netX 90 via the internal DPM
   using the cifX API function xChannelDownload() or the underlaying mailbox packet service "HIL_FILE_DOWNLOAD_REQ"
   in this case the host application communicates with a running LFW or the MFW on COM-side

2) Store the new fimware binary in a flash memory

The flash programming is performed by the running LFW or MFW on COM side. The user application on APP-side or an external host is not responsible for flash programming.
The new firmware is stored in the so called "update area". I.e. after flash programming there are two firmware files inside the flash: a) the active firmeare, b) the new firmware