E.4.17.2 waiting for the command to execute, E.4.17.3 checking command execution results – Intel Extensible Firmware Interface User Manual
Page 950

Extensible Firmware Interface Specification
E-84
12/01/02
Version 1.10
// Array of packet fragment descriptors. The first byte of the
// media header is the first byte of the first fragment.
struct {
// Address of this packet fragment.
PXE_UINT64
FragAddr;
// Length of this packet fragment.
PXE_UINT32
FragLen;
// Reserved, must be set to zero.
PXE_UINT32
reserved;
} FragDesc[n];
} PXE_CPB_FILL_HEADER_FRAGMENTED;
#pragma pack()
E.4.17.2
Waiting for the Command to Execute
Monitor the upper two bits (14 & 15) in the
CDB.StatFlags
field. Until these bits change to
report
PXE_STATFLAGS_COMMAND_COMPLETE
or
PXE_STATFLAGS_COMMAND_FAILED
,
the command has not been executed by the UNDI.
StatFlags Reason
COMMAND_COMPLETE
Command completed successfully. Frame is ready to transmit.
COMMAND_FAILED
Command failed. StatCode field contains error code.
COMMAND_QUEUED
Command has been queued.
INITIALIZE
Command has been not executed or queued.
E.4.17.3
Checking Command Execution Results
After command execution completes, either successfully or not, the
CDB.StatCode
field
contains the result of the command execution.
StatCode Reason
SUCCESS
Command completed successfully. Frame is ready to transmit.
INVALID_CDB
One of the CDB fields was not set correctly.
INVALID_CPB
One of the CPB fields was not set correctly.
BUSY
UNDI is already processing commands. Try again later.
QUEUE_FULL
Command queue is full. Try again later.
NOT_STARTED
The UNDI is not started.
NOT_INITIALIZED
The UNDI is not initialized.