01.06.2013 Views

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Related Topics<br />

Top of list<br />

Index page<br />

Example - User's Device Send Function<br />

Interrupt 0xAC service 0xA7: DEV_WAIT_DHCP_COMPLETE, Wait for DHCP<br />

Waits for completion of IP configuration process by DHCP ("Dynamic Host Configuration Protocol "). This call<br />

must be used if DEV_OPEN_IFACE API was called with DHCP enabled (see use_dhcp ) in DevUserDriver<br />

structure.<br />

Parameters<br />

AH<br />

CX<br />

ES:DI<br />

0xA7 (=DEV_WAIT_DHCP_COMPLETE)<br />

Timeout seconds. This value will depend on the DHCP server used. A minimum value of 15 seconds is<br />

recommended.<br />

Pointer to same DevUserDriver structure used at the DEV_OPEN_IFACE call.<br />

Return Value<br />

Comments<br />

DX = 0, AX = 0: Success<br />

The variables IPAddrand Netmaskin the DevUserDriver structure contain the valid IP<br />

configuration. The Dhcp_Datastructure member points to the full configuration dataprovided by the<br />

DHCP server.<br />

DX = -1: AX contains error code: 260 Timeout.<br />

Before calling this function, the device receiver task must be running.<br />

For more detailed description see How to add an TCP/IP device driver/link layer interface<br />

You will find all needed types, constants and prototypes in the CLIB header files TCPIPAPI.H and TCPIP.H.<br />

Clib TCPIP.C implementation of this function:<br />

int Dev_Wait_DHCP_Complete(<br />

DevUserDriver far * DriverInfo,<br />

unsigned int time_s,<br />

int * errorcode)<br />

Related Topics<br />

Top of list<br />

Index page<br />

Example - User's receiver task<br />

Page 155 / 400

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!