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.

ES:DI<br />

0x46 (= RTX_FIND_EVENTGROUP)<br />

Pointer to 4 character name tag. This string need not be zero terminated but most be four bytes length.<br />

Return Value<br />

Comments<br />

DX = 0 success AX: contains the event group ID<br />

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

This function allows event groups to be accessed by another program which knows the agreed upon<br />

name for the group, thereby providing a communication and control mechanism between programs.<br />

Related Topics<br />

Top of list<br />

Index page<br />

<strong>RTOS</strong> Event Manager<br />

Interrupt 0xAD service 0x50: RTX_CREATE_MSG, Create a Message Exchange<br />

Parameters<br />

AH<br />

ES:DI<br />

Creates a new Message Exchange.<br />

0x50 (= RTX_CREATE_MSG)<br />

Pointer to user RTX_Msg type structure<br />

Return Value<br />

Comments<br />

DX = 0 success AX: 0, RTX_Msg structure contains the new msgID<br />

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

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

The Message Exchange Manager returns a 16-Bit unique ID to the caller.<br />

You can provide a unique 4 character tag to identify the Message Exchange, thereby allowing other<br />

programs access to it by name.<br />

The maximum number of Message Exchanges supported by the system is ten.<br />

Related Topics<br />

Page 213 / 400

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

Saved successfully!

Ooh no, something went wrong!