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

Interrupt 0xAC service 0x19: API_REGISTERCALLBACK, Register a user callback function
Parameters
AH
BX
CX
ES:DI
Register a user callback function for events occurring on a TCP socket.
0x19 (= API_REGISTERCALLBACK)
Socket descriptor
Event flag mask (see below)
Pointer to callback function (see below)
Return Value
Comments
DX = 0 success
DX != 0 AX: contains error code
The TCP/IP stack of the IPC@CHIP is able to execute a registered user callback function, if one or more some
specified events happens on a TCP socket connection.
The callback function must be of the following type (Borland C):
void huge socketCallBackFunc(int socketdescriptor,
int eventFlags)
Before closing a socket, you should remove the callback function. This is done by calling this API function with
a null pointer in ES:DI and value 0 in register CX.
The input parameter eventFlags to the callback is a bit field indicating the event(s) that have occurred.
The set of events for either the CX event mask argument to this API or the eventFlags callback parameter
are defined in TCPIPAPI.H as follows:
#define CB_CONNECT_COMPLT 0x0001 // Connection complete
#define CB_ACCEPT 0x0002 // Remote client has established
// a connection to our listening server.
#define CB_RECV 0x0004 // Incoming data arrived
#define CB_SEND_COMPLT 0x0010 // Sending of data has been acked by the peer
#define CB_REMOTE_CLOSE 0x0020 // Peer has shutdown the connection
#define CB_SOCKET_ERROR 0x0040 // An error occurred on the connection
#define CB_RESET 0x0080 // Peer has sent a rest on the connection
#define CB_CLOSE_COMPLT 0x0100 // close has been completed
Related Topics
Top of list
Index page
API_REGISTERCALLBACK_PASCAL For Pascal callback functions
Page 121 / 400