Board Features
9
FRU information in the AM4330 includes data describing the AM4330 board as per AMC.0 R2.0
specification requirements. This information is retrieved by the Carrier AMC, enabling reporting of
board-specific information through an standardized mechanism.
Following are the definitions for the multirecord implemented by the firmware as part of Module
data.
2.4.4
E-Keying
E-Keying has been defined in the AMC.0 R2.0 Specification to prevent module damage, prevent
misoperation, and verify bay connection compatibility. The FRU data contains the AMC point-to-
point connectivity record as described in Section 3.9.2 of the AMC.0 R2.0 specification.
The Set/Get AMC Port State IPMI commands defined by the AMC.0 specification are used for either
granting or rejecting the E-keys.
2.4.5
MMC Firmware Code
MMC firmware code is organized into boot code and operational code, both of which are stored in a
flash module. Upon an MMC reset, the MMC executes the boot code and performs the following:
1 Self test to verify the status of its hardware and memory.
2 Performs a checksum of the operational code.
3 Communicates with the Firmware Upgrade Manager (FWUM) in order to inform the MMC watchdog that the
actual MMC firmware is suitable for execution.
Upon successful verification of the operational code checksum, the firmware will jump to the
operational code.
2.4.6
MMC Firmware Upgrade Procedure
It is important to use compatible, MMC, FWUM versions. Since all these software and hardware
solution are exchanging information, they must be in synch. Please always follow Kontron
documentation for all your upgrade.
The recommended upgrade sequence must be:, FWUM, MMC,.
MMC Firmware upgrades can be done by using IPMITOOL from the AMC Carrier or remotely on the
chassis. It has been design to upgrade through any IPMI interface without payload impact
