Get Device Action Result
更新时间： 2026/08/06
在Gitcode上查看源码Get Device Action Result
Change History
| openUBMC Version | Revision Date | Description |
|---|---|---|
| 25.06 | 2025/06/26 | Initial draft: add command details |
Basic Information
Function Description
This API is added to obtain the chip operation result.
Privilege
Command Information
Request Information
| Byte | Data Field |
|---|---|
| NetFn | 30h |
| CMD | 93h |
| 1:3 | Manufacturer ID, LS 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 | Sub command, sub command = 54h |
| 5:8 | Position: indicates the position number. (The 8100 slot ID may be repeated. The position is added to locate a card. For other products, 0x00000000 can be filled in.) |
| 9 | SlotID: indicates the slot ID. |
| 10 | Operated device ID: 0: indicates all device numbers. Others: specified device ID For the DIMIN chip, the value ranges from 1 to 4. For other operation types, the chip ID range depends on the actual situation. The chip of the video compression card does not support the query operation. For the FPGA card, there is only one device, which is represented by 0. For the MCU, there is only one device, which is represented by 0. |
| 11 | Type of the operation to be queried. Not all devices support the following operation types: 1: The chip is reset. (The query result is the result of the latest reset operation.) 2: FPGA card self-healing 3: Reset the MCU. |
Response Information
| Byte | Data Field |
|---|---|
| 1 | Completion Code |
| 2:4 | Manufacturer ID, LS 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. |
| 5:N | Operation result: When the query operation type is 1: If the request is for all chips, N = Total number of chips + 4. 0: The chip is reset successfully. 1: The chip fails to be reset. 2: The chip reset status is unknown. When the query operation type is 2, the options are as follows: To query the FPGA self-healing status Btye5: 0: idle 1: Self-healing is in progress. 2: Self-healing is not supported in the current state, for example, during MCU upgrade. 3: self-healing failure Btye6: When BYTE5 is set to 1, the self-healing progress is displayed. The value ranges from 0 to 100. When the query operation type is 3, the options are as follows: Byte5: 0: idle 1: restarting 2: Failed to restart the MCU. (The result of the latest MCU reset is queried.) 3: The MCU is restarted. (The result of the latest MCU reset is queried.) |
Command Example
Obtain the chip reset result.
Request:
bash
ipmicmd -k "0f 00 MM NN" smi 0Response:
text
0f MM NN