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.

DS:SI<br />

Output Parameter: Pointer to a 6 byte array where the generated Ethernet multicast address will be written.<br />

Return Value<br />

Comments<br />

DX = 0, AX = 0: Success, storage at DS:SI contains the generated Ethernet address<br />

DX = -1, AX = -1: Invalid IP address<br />

This API function computes the MAC address in the following manner: To map an IP multicast address to a<br />

corresponding Ethernet multicast address place the low-order 23 bits of the IP multicast address into the low<br />

order 23 bits of the special Ethernet multicast address 01 00 5E 00 00 00<br />

e.g. IP multicast address 224.0.0.1 becomes Ethernet address 01 00 5E 00 00 01<br />

Related Topics<br />

Top of list<br />

Index page<br />

API function ADD_IGMP_MEMBERSHIP - Install an IP multicast address entry<br />

API function DROP_IGMP_MEMBERSHIP - Delete an IP multicast address entry<br />

Interrupt 0xAC service 0xA0: DEV_OPEN_IFACE, Install user device driver<br />

Open and install a user TCP device driver/interface at the internal TCP/IP stack of the <strong>@CHIP</strong>-<strong>RTOS</strong>.<br />

Add a new link layer for TCP/IP communication.<br />

Parameters<br />

AH<br />

ES:DI<br />

0xA0 (=DEV_OPEN_IFACE)<br />

Pointer to user filled DevUserDriver structure, which contains all needed information (device driver functions,<br />

etc.) for the user's driver implementation.<br />

Return Value<br />

Comments<br />

DX = 0, AX = 0 (or =236): Success<br />

The IfaceHandlemember of DevUserDriverstructure at [ES:DI] contains the valid Device Handle,<br />

which will be required as a parameter for most of the other device interface API for this device.<br />

If member variables iface_typeand use_dhcpwere set to 1, AX should contain code 236. In this<br />

case, the user must make the additional call to DEV_WAIT_DHCP_COMPLETEAPI to wait for<br />

completion of the IP configuration by DHCP.<br />

DX = -1: AX contains error code. Installation failed<br />

This is the first function to use when adding your own interface to the TCP/IP stack of the <strong>@CHIP</strong>-<strong>RTOS</strong>.<br />

The TCP/IP API calls 0xA0 - 0xA7 allow the application developer to implement an additional TCP/IP driver<br />

interface for a connected hardware device (e.g. connected UART or an Ethernet controller). This new<br />

Page 149 / 400

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

Saved successfully!

Ooh no, something went wrong!