Pre-update Check
更新时间： 2026/09/02
在AtomGit上查看源码Pre-update Check
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 26.09 | 2026/09/02 | Initial draft: add command details |
Basic Information
Function Description
Triggers the pre-update check for firmware and checks whether the specified firmware can be updated. The success of this command only indicates that the pre-check has been triggered, not that the firmware can be updated. The result must be obtained through 9Ah. If the check is still in progress, the 9Ah return value is 2.
Privilege
BasicSetting
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| Cmd | 93h |
| 1:3 | Manufacturer ID, LB Byte first. The length is fixed to three bytes. For example, if the vendor ID is 2011 and the corresponding hexadecimal value is 0x0007DB, the first byte is DBh, the second byte is 07h, and the third byte is 00h. |
| 4 | SubCmd, subcommand=99h |
| 5 | FruId |
| 6:7 | ComponentID: firmware ID. LB Byte first. For the value definition, see Firmware ID Management. |
| 8:11 | ComponentIDEx: firmware extended ID. LB Byte first. For the value definition, see Firmware ID Management. If FruId, ComponentID, and ComponentIDEx are all f, the pre-check is triggered for all firmware. |
| 12:13 | Reserved. Set this field to 0. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code |
| 2:4 | Manufacturer ID, LB Byte first. The length is fixed to three bytes. For example, if the vendor ID is 2011 and the corresponding hexadecimal value is 0x0007DB, the first byte is DBh, the second byte is 07h, and the third byte is 00h. |
Command Example
Trigger the pre-check for all firmware
Request:
bash
ipmitool raw 0x30 0x93 0xdb 0x07 0x00 0x99 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x00 0x00Response:
text
0xdb 0x07 0x00Trigger the pre-check for a single firmware
Request:
bash
ipmitool raw 0x30 0x93 0xdb 0x07 0x00 0x99 0xff 0x18 0x01 0x00 0x00 0x00 0x00 0x00 0x00Response:
text
0xdb 0x07 0x00