IntelÃ‚Â® Server System Server System "Emerald Ridge ... - CTL

More documents

Recommendations

Info

Intel® Server System "Emerald Ridge” ” Integrated Baseboard Management Controller EPS 錯誤 ! 尚未定義樣式。5. BMC Flash Update5.1 Logical Firmware Image BlocksThe BMC firmware is divided into four main functional blocks: Boot Block: Small firmware image containing a bootloader and cursory hardwareinitialization. It allows re-download of the operational code if it somehow becomes corrupted.Operational Code: The main runtime firmware. This includes the embedded Linux kernel,and all applications.Platform Information Area (PIA): Contains all the read/write configuration/status data usedby the Operational Code. This includes IPMI configuration, SEL, SDR, etc.Intel ® Remote Management Module 3 (Intel ® RMM3) (optional): Contains executables andread-only data needed by the advanced features. Resides on the Intel ® RMM3 Add-in cardflash.Firmware in any block may be updated individually. A normal update consists of updating theOperational Code and Intel ® RMM3, while preserving the contents of the PIA. In general, theboot block should not be updated on production systems.These blocks are mapped onto the following pieces of the Linux architecture: Boot Block: Uboot boot loader code. The Uboot environment variables data section is notmapped into any update block so it is never directly updated.Operation Code: Linux kernel and built-in drivers, and the Compressed ROM File system(CRAMFS) Root file system including all applications and loadable drivers. It includes theseparately built CRAMFS for the embedded web server, mounted as /usr/local/www.PIA: The Parameters section, a Journaling Flash Filesystem (JFF2) read/write flash filesystem that contains configuration and status files, mounted as /conf.Intel ® RMM3: An optional CRAMFS residing on the Intel ® RMM3 flash and mounted into theRoot file system when the Intel ® RMM3 is present as /usr/local/rmm3.Each block is preceded in the flash image by a Device Information Block (DIB) headeridentifying the type of block and what flash addresses it comprises. The update utilities use theDIBs to decide what ranges of flash need to be written to during an update.5.2 Firmware Transfer Mode UpdateThe BMC provides a Firmware Transfer mode that allows the BMC firmware to be updated.Data is sent to the BMC to be written into flash. Once complete, Firmware Transfer mode isexited and the BMC resets itself to resume normal operation. This mode is different from forceupdatemode.While in this mode only the firmware transfer commands are guaranteed to be supported, aswell as a few commands needed by the update process. Other commands may haveunpredictable results and should be avoided.The additional commands are:Revision 1.1Intel ® Confidential 73
BMC Flash UpdateIntel® Server System "Emerald Ridge” Integrated Baseboard Management Controller EPSGet Device ID: Used to determine the current revision of the firmware, get the platform ID,and find out whether the BMC is in operational or update mode.Get Self Test Results: Used to see if the BMC has errors.Get Buffer Size: Used to indicate that larger KCS buffers are supported (at least 128 bytesverses the old 32 byte limit), for better KCS update performance.Get Advanced Support Configuration: Used to indicate if the Intel ® RMM3 card is present ornot. If present, it is normally updated when the Operational code is.Firmware Transfer mode is entered when the BMC receives the Enter Firmware Transfer Modecommand while in normal operational mode. While in this mode the BMC continues to functionwith the caveat that any writes to the PIA section do not go to flash but to a RAM shadow copy.This means that after the Exit Firmware Transfer Mode command is received and the BMCreturns to normal operation, any SEL, SDR, or IPMI configuration changes made while inFirmware Transfer mode will be lost.Firmware Transfer commands allow any area of the BMC flash to be updated. These functionsunderstand the sector structure of the flash device used on the server board, so the updateutility cannot issue sector erase commands. Instead flash sectors are implicitly erased asnecessary before the first write to a sector.After the Exit Firmware Transfer Mode command is successfully completed, the BMC resets,and the new image runs immediately after the bootloader boots the BMC. If there is a problembooting the new image, such as an invalid checksum, the BMC stays in the boot block. Formore information refer to the Boot Recovery mode section.No system events are logged when the BMC enters or exits firmware transfer mode.5.2.1 Command Support during Firmware Transfer ModeThe following commands are supported while the BMC is in forced-firmware update mode. Seesection 5.3 for more information on this mode.Table 33. Firmware Update Mode CommandsIPMI NetFunctionCommand NumberCommand NameApplication (06h) 01h Get Device IDApplication (06h) 04h Get Self Test ResultsApplication (06h) 37h Get System GUIDFirmware (08h) 00h Enter Firmware Transfer ModeFirmware (08h) 01h Firmware ProgramFirmware (08h) 02h Firmware ReadFirmware (08h) 03h Get Firmware Range ChecksumFirmware (08h) 04h Exit Firmware Transfer ModeFirmware (08h) 05h Set Program SegmentStorage (0Ah) 10h Get FRU Area InfoIntel General (30h) 66h Get Buffer SizeIntel General (30h) 71h Get Advanced Support Configuration74Intel ConfidentialRevision 1.1
Page 1:
Intel ® Server System "Emerald Rid
Page 4 and 5:
錯誤 ! 尚未定義樣式
Page 6 and 7:
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41: 錯誤 ! 尚未定義樣式
Page 70 and 71: Intel® Server System "Emerald Ridg
Page 140 and 141:
Intel® Server System "Emerald Ridg
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Intel® Server System "Emerald "Rid
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
show all

IntelÃ‚Â® Server System Server System "Emerald Ridge ... - CTL

Create successful ePaper yourself

Delete template?

Save as template?