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.

Releases a block of allocated memory.<br />

Parameters<br />

AH<br />

DX:SI<br />

0x0B (= API_FREE)<br />

Pointer to the buffer<br />

Return Value<br />

Comments<br />

Top of list<br />

Index page<br />

DX = 0 , AX = 0 success<br />

DX != 0 , AX = 0 free failed<br />

This out dated function releases memory allocated with API_MALLOC. It is maintained here only for<br />

compatibility with earlier <strong>@CHIP</strong>-<strong>RTOS</strong> versions (before version 1.00).<br />

For new applications, the DOS interrupt 0x21 memory allocate service 0x48 and release service 0x49 are<br />

recommended.<br />

Interrupt 0xAC service 0x0C: API_GETRCV_BYTES, Get waiting bytes count<br />

Parameters<br />

AH<br />

BX<br />

Get the number of bytes on a socket, waiting for read.<br />

0x0C (= API_GETRCV_BYTES)<br />

socket descriptor<br />

Return Value<br />

Comments<br />

DX = 0 success, AX contains the number of bytes ready<br />

DX != 0 failed, AX contains error code<br />

If the specified socket is an UDP socket, API_GETRCV_BYTES will return the size (in bytes) of the next<br />

waiting datagram at the internal socket receive queue.<br />

Related Topics<br />

API_RECVFROM - UDP Receive<br />

API_RECV - TCP Receive<br />

Page 112 / 400

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

Saved successfully!

Ooh no, something went wrong!