13.07.2015 Views

Intel® Server System Server System "Emerald Ridge ... - CTL

Intel® Server System Server System "Emerald Ridge ... - CTL

Intel® Server System Server System "Emerald Ridge ... - CTL

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix B: FirmwareDevice Information Block FormatIntel® <strong>Server</strong> <strong>System</strong> "<strong>Emerald</strong> <strong>Ridge</strong>” Integrated BaseboardManagement Controller EPSAppendix B: : Firmware Device InformationBlockFormatThe BMC hex file contains Device Info Blocks (DIBs) that utilities may use to perform updaterelatedoperations. These device info blocks are formatted as shown in the following tables.Table 97: Operational Code Info Block Version 6FieldSize (bytes)DescriptionCookie 16 String “*OpCodeInfo*” stored in hex file that indicates whether or not thehex file is valid.Version of Info Block 1 Version of info block that the hex file is compatible with. Version is 6 for thisspecification.Structure Size 1 Size of this structure, including checksum.Reserved (1) 2Start of Op Code 4 Offset of start of operational code image in flash.End of Op Code 4 Offset of last byte of operational code.Op Code Run 4 Offset of first instruction to execute in operational code.Reserved (2) 2Major FW Version 2 Major operational code firmware version.Minor FW Version 2 Minor operational code firmware version.Build Date 12 Hex file build date – formatted as __DATE__Build Time 12 Hex file build time – formatted as __TIME__Reserved (3) 2Checksum 2 Info block checksum, starting from “Cookie” to “Reserved (3)”Table 98: Boot Code Info Block Version 6FieldSize (bytes)DescriptionCookie 16 String “*BootInfo*” stored in hex file that indicates whether or not thehex file is valid.Version of Info Block 1 Version of info block that the hex file is compatible with. Version is 6 forthis specification.Structure Size 1 Size of this structure, including checksum.Platform Name 16 Platform name such as “IMM_BootBlock”. This field is used by theutility to verify that the hex file is intended for the target system.Microcontroller Name 5 Microcontroller acronym name such as “BMC”, “HSC”, etc.Primary Address 1 IPMB slave address of microcontrollerSecondary Address 1 IPMB slave address of secondary identical controllers such as HSC2.Flash Type 1 Flash type of the microcontroller’s flash being updated.Reserved (1) 2Start of Boot Code 4 Offset of start of boot code image in flash.End of Boot Code 4 Offset of last byte of boot code.Reserved (2) 8Major FW Version 2 Major boot code firmware version.Minor FW Version 2 Minor boot code firmware version.Build Date 12 Hex file build date – formatted as __DATE__Build Time 12 Hex file build time – formatted as __TIME__174Intel ConfidentialRevision 1.1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!