Kontron AT8902 - Manual (Page 81)

AT8902 Software Description
Page 4 - 14 AT8902 User Guide
4.4.2 Field Replaceable Unit (FRU) Information
4.4.2.1 Base Board FRU Information
This FRU information contains the IPMI defined Board and Product Information areas that hold
the part number and serial number of the board and the Multirecord Information Area that con-
tains the PICMG defined Point to Point Information records.
The Internal Use Area is preallocated to 384 bytes and is free for customer use.
This FRU information responds to FRU ID #0, which is the ID for the IPMC.
4.4.2.2 Mezzanine FRU Information
The FRU information of any optional Mezzanine Extension responds to FRU ID #3 and is
manged by the IPMC. This FRU information contains the IPMI defined Board and Product In-
formation Areas and contains the part number and serial number of the mezzanine.
4.4.3 E-Keying
E-Keying has been defined in the PICMG 3.0 Specification to prevent board damage, prevent
misoperation, and verify fabric compatibility. The FRU data contains the board point-to-point
connectivity record as described in Section 3.7.2.3 of the PICMG 3.0 specification.
When the board enters M3 power state, the shelf manager reads in the board point-to-point
connectivity record from FRU and determines whether the board can enable the Gigabit Eth-
ernet ports to the back plane. Set/Get Port State IPMI commands defined by the PICMG 3.0
specification are used for either granting or rejecting the E-keys.
Additional E-Keying is prodived for connectivity between the AMC carrier and the AMC bays
as described the in Section 3.9 and 3.7 of the AMC.0 RC.1.1 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.
4.4.4 IPMC Firmware Code
IPMC firmware code is organized into boot code and operational code, both of which are stored
in a flash module. Upon an IPMC reset, the IPMC executes the boot code and performs the
following:
1. Self test to verify the status of its hardware and memory.
2. Calculates a checksum of the operational code.
3. Communicates with the Firmware Upgrade Manager (FUM) in order to inform the IPMC
watchdog that the current IPMC firmware is suitable for execution.
Upon successful verification of the operational code checksum, the firmware will jump to the
operational code.