Advantech MicroTCA UTCA-5503, User Manual

Page: 46 / 66

UTCA-5503 User Manual 34
5.1 MCH Field Updateable Components
The MCH provides HPM.1 compliant in field updates, supporting a total of four com-
ponents:
1) MCMC Boot Loader
2) MCMC Application
3) MCMC FRU Data
4) FPGA
The HPM.1 update works through several IPMB capable interface, e.g. RMCP, KCS
interface (optional) from PCB3, serial debug interface.
5.1.1 MCMC Boot Loader
Located at the beginning of the user memory space of the H8S processor is a small
software component called the boot loader, which has several important tasks to per-
form for the MCMC boot process. As the boot loader is not rollback capable, it can
potentially be damaged through a failed upgrade operation. Therefore Advantech do
not plan to release boot loader updates for end customers.
5.1.2 MCMC Application
The active MCMC firmware (application) is located in the user memory space, right
behind the boot loader. An external flash holds two FW copies, an active as well as a
backup one, providing roll back features in case of failed FW upgrades. Advantech
will provide bug fixes, updates and new features through FW application images.
5.1.3 MCMC FRU Data
Although realized as HPM.1 compliant component, the MCMC FRU data is pro-
grammed during manufacturing and is not intended to be reprogrammed at a later
stage. Therefore this feature is reserved, Advantech do not plan to release FRU
update images.
5.1.4 FPGA
The FPGA is a HPM.1 compliant component without rollback support. However the
FW implements an automatic recovery mechanism: If the FPGA POST detects a
faulty configuration, it will automatically reload a failsafe image that has been pro-
grammed during manufacturing. Advantech will provide bug fixes, updates and new
features for the FPGA as necessary.
5.2 MCH HPM.1 Upgrade Process
As mentioned above, the MCMC Application supports a rollback mechanism. This
means that the FW will create a backup copy of the current (active) configuration
each time a new FW is downloaded through HPM.1, thus allowing to switch back to
the old version in case of upgrade problems.
All components have separate upgrade and activation phases. For the MCMC Appli-
cation this means that the new configuration will only be activated through a HPM.1
Activation command, resulting in a FW restart.
For the boot loader and FPGA this means that the new configuration will either auto-
matically become active at the next reboot or when a reboot is manually invoked
through the HPM.1 Activation command.