Software architecture
15/70
2.2.2.2
Use case B: Small footprint slave device with FW update area in SQI flash
This use case is similar to use case A, i.e. the communication firmware is
running with INTRAM COM and INTFLASH01 and does not require
external SDRAM or SQI flash.
However, in this case the firmware update area is moved to the external
SQI flash, thus allowing the communication firmware to use more of the
INTFLASH. This means also that the APP CPU is responsible for the
firmware update, because only the APP CPU has access to the SQI flash.
Use case B applies to “traditional” Fieldbus protocol firmware (protocol
stack running in channel 0 of DPM) and “standard” Real-Time Ethernet
protocol firmware including a basic web server (protocol stack running in
channel 0 and “network services” running in channel 1 of DPM).
·
Communication firmware size is ≤ 880 KByte and located in
INTFLASH01
·
Firmware update area is located in external SQI flash
–
APP CPU places new firmware in this area
–
COM firmware does not have access to external SQI flash
–
new firmware can be installed with the help of the maintenance
firmware
·
APP CPU may use external SQI Flash and external SDRAM exclusively
(as defined in hardware configuration)
netX 90 | Production guide
DOC190101PG03EN | Revision 3 | English | 2019-07 | Released | Public
© Hilscher 2019
