E.4.18.2 waiting for the command to execute, E.4.18.3 checking command execution results – Intel Extensible Firmware Interface User Manual

Page 954

Advertising
background image

Extensible Firmware Interface Specification

E-88

12/01/02

Version 1.10

E.4.18.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. Use the Get Status command to see
when frame buffers can be reused.

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.18.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. Use the Get Status command to see
when frame buffers can be reused.

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. Wait for queued commands to complete. Try again
later.

BUFFER_FULL

Transmit buffer is full. Call Get Status command to empty buffer.

NOT_STARTED

The UNDI is not started.

NOT_INITIALIZED

The UNDI is not initialized.

Advertising