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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This function always returns immediately. If no message is currently available, DX is non-zero and AX = -<br />

28.<br />

On success, a message from the highest priority non-empty FIFO mailbox is copied into the 12 byte store<br />

at [ES:DI] and then this delivered message is removed from the mailbox.<br />

Related Topics<br />

Top of list<br />

Index page<br />

<strong>RTOS</strong> Message Exchange Manager<br />

Interrupt 0xAD service 0x54: RTX_WAIT_MSG, Wait for a message<br />

Parameters<br />

AH<br />

ES:DI<br />

Wait up to a specified number of milliseconds for a message from a Message Exchange.<br />

0x54<br />

Pointer to user RTX_Wait_Msg type structure<br />

Return Value<br />

Comments<br />

DX = 0 success AX: 0<br />

DX != 0 failure AX: contains error code<br />

The user must fill in the RTX_Wait_Msg structure prior to calling here.<br />

On success, the highest priority message available on the exchange is copied into your message<br />

container at location specified by the msg member of the RTX_Wait_Msg structure. Then the message<br />

is removed from the Message Exchange.<br />

Each caller to this API can specify their priority for access to messages. To wait in FIFO order, all callers<br />

have to wait with the same priority.<br />

Related Topics<br />

Top of list<br />

Index page<br />

RTX_Wait_Msg type definition<br />

<strong>RTOS</strong> Message Exchange Manager<br />

Page 216 / 400

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

Saved successfully!

Ooh no, something went wrong!