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

Top of list
Index page
send queue.
This function reports the number of bytes currently in the UART transmit hardware. By adding this
function's return value to the software transmit buffer byte count reported by the GetDriverInfo API, you
can determine the total number of transmit data bytes still pending output.
The maximum count returned here will be 2 bytes, accounting for the UART's transmit shift register (1
byte) and transmit holding register (1 byte).
Interrupt 0x14 service 0xA1: Install a Fossil User Callback Function
Parameters
AH
DX
ES:DI
The user callback function will be called when a Fossil serial port event occurs.
0xA1
Comments
Port number: 0 for EXT, 1 for COM
Pointer to the User Callback function
This call installs an user callback function for the specified serial port. The callback function must be
very short! Long Fossil callback functions can lead to character loss.
To use the Fossil callback functions, you have to switch the serial port into the IRQ Mode (see
CHIP.INI). In DMA mode the callback functions will not work!
The callback function must conform to this prototype:
fossil_event_t far *(huge my_fossil_callback)(
fossil_event_t far *e ) ;
The fossil_event_t structure e passed in contains the event which has occurred. Following events
are possible:
#define FE_DATA_AVAIL 0x01 // New Data Received
#define FE_READY_FOR_SEND 0x02 // (currently not supported)
#define FE_ERROR_DETECTED 0x10 // (currently not supported)
Newly received data_length bytes can be found at location referenced by data pointer in structure e.
The callback function can also return a fossil_event_t structure. The returned structure contains an
action event which the Fossil serial port driver will respond to as follows:
#define FE_IGNORE_DATA 0x01 // Do not copy the received data
// into the receive queue.
#define FE_DATA_TO_SEND 0x02 // (currently not supported)
If the callback does not return any event, the return value must be a null pointer (=0L).
Page 341 / 400