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

put into the buffer.
The sender can be identified by the IP address and port number reported in the sockaddr_in structure
API_RECVFROM can only return complete UDP datagrams at the user provided buffer. If the next waiting
datagram at the internal socket receive queue has a higher size than the specified
recv_param.bufferlength, API_RECVFROM returns errorcode 240 (Message too long) without writing
the datagram into the user buffer. You can use API_GETRCV_BYTES to detect the size of the next waiting
datagram at the internal receive queue of this socket.
Related Topics
Top of list
Index page
API_SENDTO - Send UDP datagram
API_RECV - Receive TCP data
API_GETRCV_BYTES - Get waiting bytes on a socket
Interrupt 0xAC service 0x06: API_SENDTO, Transmit a UDP datagram
Parameters
AH
BX
DX:SI
For UDP only, transmits message to another transport end-point.
0x06 (= API_SENDTO)
Socket descriptor
Pointer to a send_params structure which caller must fill in prior to call.
Return Value
Comments
DX = 0 success AX: number of bytes sent
DX != 0 AX: contains error code
This function will output up to send_params.bufferLength bytes from the buffer at
send_params.bufferPtr to the IP address specified by the sockaddr_in structure referenced by the
send_params.toPtr pointer. The return value indicates the actual number of bytes sent.
Related Topics
Top of list
Index page
API_RECVFROM - Receive UDP datagram
API_SEND - Send TCP data
Page 109 / 400