E.4.2.2 waiting for the command to execute, E.4.2.3 checking command execution results – Intel Extensible Firmware Interface User Manual
Page 908

Extensible Firmware Interface Specification
E-42
12/01/02
Version 1.10
E.4.2.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. StatFlags contain operational state.
COMMAND_FAILED
Command failed. StatCode field contains error code.
COMMAND_QUEUED
Command has been queued. All other fields are unchanged.
INITIALIZE
Command has not been executed or queued.
E.4.2.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. StatFlags contain operational state.
INVALID_CDB
One of the CDB fields was not set correctly.
BUSY
UNDI is already processing commands. Try again later.
QUEUE_FULL
Command queue is full. Try again later.
If the command completes successfully, use
PXE_STATFLAGS_GET_STATE_MASK
to check the
state of the UNDI.
StatFlags Reason
STOPPED
The UNDI is stopped.
STARTED
The UNDI is started, but not initialized.
INITIALIZED
The UNDI is initialized.