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

More documents

Recommendations

Info

Intel® Server System "Emerald Ridge” Integrated Baseboard Management Controller EPSIPMI Command InterfaceCode00h01h02hCommandEnterFirmwareTransferModeFirmwareProgramFirmwareReadTable 61. BMC Firmware Transfer CommandsNet Function = Firmware (08h), LUN = 00Request, Response DataRequest:Byte 1:5 – I,N,T,E,LResponse:Byte 1 – Completion codeRequest:Byte 1 – Start address (LS byte)Byte 2 – Start address (MS byte)Byte 3:n – Data to programResponse:Byte 1 – Completion code81h = Address not in flashByte 2 – Address (LS byte)Byte 3 – Address (MS byte)Byte 4 – Number of bytesprogrammed0 = FailureRequest:Byte 1 – Start address (LS byte)Byte 2 – Start address (MS byte)Byte 3 – LengthResponse:Byte 1 – Completion code81h = Addr not in flashByte 2 – Start address (LS byte)Byte 3 – Start address (MS byte)Byte 4:n – DataDescriptionThis command directs the BMC to enter firmware transfer mode.The BMC has limited functionality in this mode. The onlycommands guaranteed to be accessible are the firmware transfercommands, the IPMI Get Device ID and Get Self Test Resultscommands, and the OEM command Get Advanced SupportConfiguration to indicate if an Intel ® Remote Management Module3 (Intel ® RMM3) add-in card is present or not.The ASCII characters I, N, T, E, L are used as a key to guardagainst unintentional entry into this mode.The Firmware Program command requests that given bytes bewritten to the BMC flash starting at the specified address. If thenumber of bytes to be transferred exceeds the end of writeableflash, the write will occur but the transfer will be truncated.The actual number of programmed bytes may be less than thenumber passed in the request if the requested transfer exceedsavailable internal buffer space, or if the requested transfer spansover the end of alterable flash space. The appropriate nonzerocompletion code is returned if a truncation occurs or if the transferis not performed.This command may take up to 20.9 seconds to complete,because the first write to a block in the flash silicon initiates a timeconsuming erase of that block. 20.9 seconds is the worst-casespec for main block erase. The typical timing is approximately 0.5seconds. The start address specifies the lower 16 bits of theprogram address. Use the ‘SetProgramSegment’ to set the upper16 bits of the address before issuing this command.The addresses are flash device relative. They range from zero tothe size of the flash device minus one. The flash size is systemdependent.The completion code 81h is returned if the address specified isnot in flash. One possible use for this is to attempt to program theIntel ® RMM3 flash address and if the Intel ® RMM3 is not present,this completion code is returned.The starting address from the request is returned in the responseto help match the response with the request. The actual numberof bytes returned may be less than the requested number, if therequested transfer size exceeds available internal buffer space orif the requested transfer spans over the end of alterable FLASHspace.Addresses do not wrap. For example, if the starting address plusthe length exceeds the last address for the ROM, the number ofdata bytes returned will be less than the number requested. Theaddress byte in the request is the lower 16 bits of the address ofinterest. Use the SetProgramSegment command to set the upper16 bits of the address.See the Firmware Program command for the definition of theaddress.Revision 1.1Intel ® Confidential 123
IPMI Command InterfaceIntel® Server System "Emerald Ridge” Integrated Baseboard Management Controller EPSCode03h04h05h06h07hCommandGet FirmwareRangeChecksumExit FirmwareTransferModeSet ProgramSegmentReservedEnter BootRecoveryModeNet Function = Firmware (08h), LUN = 00Request, Response DataRequest:Byte 1 – Start address (LS byte)Byte 2 – Start address (MS byte)Byte 3 – End address (LS byte)Byte 4 – End address (MS byte)Response:Byte 1 – Completion codeByte 2 – Address (LS byte)Byte 3 – Address (MS byte)Byte 4 – Checksum (LS byte)Byte 5 – Checksum (MS byte)Request: N/AResponse:Byte 1 – Completion codeRequest:Byte 1 – Segment address (LSbyte)Byte 2Response:Byte 1 – Completion codeRequest:Byte 1:5 – I,N,T,E,LResponse:Byte 1 – Completion codeDescriptionThe Get Firmware Range Checksum command returns a 2’scomplement checksum for a specified area from the startingaddress through the ending address, inclusive. Valid starting andending addresses must be passed in this request. The resultingresponse cannot be guaranteed if the starting or endingaddresses are set to values that are past the end of FLASH, orthe ending address is less than the starting address. 16 bitchecksum start and end addresses are the lower 16 bits of the(actual 32 bit) address. Use the SetProgramSegment commandto set the upper 16 bits of the address.See the Firmware Program command for the definition of theaddress.When the Exit Firmware Transfer Mode command is received, theBMC returns a successful completion code and then resets itselfto return to normal operation. Because this command causes theBMC to reset itself, a Get Device ID command should berepeatedly sent until a valid response is received indicating thatthe BMC is now in normal operational mode.The supported segment values are system dependent.This command sets the upper 16 bits of the address used for theFirmware Read, Firmware Program, and Get Firmware RangeChecksum commands.This command directs the BMC to enter boot recovery mode. TheBMC will reset itself and stay in the Uboot boot loader rather thanbooting its Linux operational code.This command is for debugging purposes only. Applicationsshould use the Enter Firmware Transfer Mode command toupdate the BMC.Table 62. SOL 2.0 CommandsNet Function = Transport, LUN = 00CodeCommandRequest, Response Data20h SOL 2.0 Activating Not Supported.21h22hSet SOL 2.0 ConfigurationParametersGet SOL 2.0 ConfigurationParametersPer the Intelligent Platform Management Interface SpecificationSecond Generation v2.0Per the Intelligent Platform Management Interface SpecificationSecond Generation v2.0124Intel 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 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Intel® Server System "Emerald Ridg
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91: Intel® Server System "Emerald Ridg
Page 156 and 157: Intel® Server System "Emerald "Rid
Page 172 and 173: 錯誤 ! 尚未定義樣式
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?