Use Cases
Three general "Use Cases" are defined when using a netX hardware and must be handled by the maintenance firmware:
- Case A: netX90 minimal - iFLash only / INTRAM only
- Case B: netX90 - iFLASH / INTRAM + SQI Flash (for APP CPU / MFW)
- Case C: netX90 / netX4000 + SQI Flash + SDRAM
Supported Drivers
The following drivers are used by the maintenance firmware for the different use cases.
Driver | netX90 | netX4000 | Description | ||
---|---|---|---|---|---|
A | B | C | C | ||
INT FLASH | For access to IntFlash0-1 for the COM CPU and IntFlash2 for APP CPU updates. | ||||
SPI | For access to the external SPI flash. | ||||
SPI FLASH | For access to the external SPI flash. | ||||
Serial | Communication with maintenance firmware (downloading/starting update). | ||||
USB | Communication with maintenance firmware (downloading/starting update). | ||||
DPM | Communication with maintenance firmware (downloading/starting update). |
Once the following issue is resolved, the SPI and SPI FLASH drivers in use case A and use case B can be removed, too.
Additional Services
In addition to the drivers, rhe maintenance firmware must also provide standard services necessary for external apllications.
- Flash device Label
Device specific infomation, including firmware update areas or file system information Device Data Provider (DDP)
The DDP is used to retrieve information like hardware compatibility or locations of FLASH areas from the FDL.Marshaller (Diagnostics interface)
For the communication between Host and netX the Marshaller is used in the following configuration.- Middleware packet handling
For file related packet handling it has to be distinguished between FLASH and filesystem area and between (regular) loadable firmware (LFW) and the maintenance firmware (MFW).
On this page