Software architecture
46/70
2.4.3
Alternative boot mode
In
alternative boot mode
, the ROM code starts the “maintenance”
instead of the “regular” communication firmware. The maintenance
firmware is capable of installing a new firmware (firmware update).
Potential use cases are:
·
Firmware update procedures:
A new firmware received via web server or host interface is stored
either on-chip in INTFLASH1 or off-chip in an externally connected SQI
Flash. A software reset cycle initiated by a software command or a
hardware reset cycle while RUN pin is connected to GND starts the
maintenance firmware, which installs the new firmware.
·
Multiple firmware versions:
The netX 90 has the maintenance firmware stored in INTFLASH1 and
holds multiple firmware versions for different Real-Time Ethernet
protocols in an externally connected SQI Flash. The maintenance
firmware installs the firmware selected by the system integrator, e.g. via
a rotary DIP-switch or by a parameter in the software reset command.
The alternative boot mode is entered on the following conditions:
·
After a software reset cycle if the firmware has initiated the alternative
boot mode by “software command” beforehand
·
After a hardware reset if the RUN pin has been connected to GND
beforehand (see figure
Pin configuration for operating modes
above)
(See also
Boot mode flow chart
Note:
If console mode and alternative boot mode are both enabled by the
RDY / RUN pins, the console mode always has priority over the
alternative boot mode. If the ROM code is in alternative boot mode
but cannot find a valid maintenance firmware, it automatically enters
console mode.
Note also that if e.g. a power loss disrupts the installation of the new
firmware, the ROM code detects that the procedure is incomplete
and re-starts the maintenance firmware without prior selection.
netX 90 | Production guide
DOC190101PG03EN | Revision 3 | English | 2019-07 | Released | Public
© Hilscher 2019