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

Page 927

Advertising
background image

32/64-Bit UNDI Specification

Version 1.10

12/01/02

E-61

E.4.8.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. UNDI and network device have been
reset. Check StatFlags.

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.8.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. UNDI and network device have been
reset. Check StatFlags.

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.

NOT_STARTED

The UNDI is not started.

NOT_INITIALIZED

The UNDI is not initialized.

DEVICE_FAILURE

The network device could not be initialized.

NVDATA_FAILURE

The nonvolatile storage is not valid.

StatFlags

Check the StatFlags to see if there is an active connection to this network device. If the no media
StatFlag is set, the UNDI and network device are still reset.

PXE_STATFLAGS_RESET_NO_MEDIA

Advertising