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

DL
CX
ES:BX
BIT7: 0=normal ISR, 1=RTX ISR (RTX ISR allow RTX Calls, e.g. wake a task), please notice the
comment below!
HAL interrupt number from following list:
0 = INT0 (external)
1 = Network controller (internal) (*)
2 = INT2 (external)
3 = INT3 (external)
4 = INT4 (external)
5 = INT5 (external) / DMA Interrupt Channel 0 (if DMA is used)
6 = INT6 (external) / DMA Interrupt Channel 1 (if DMA is used)
7 = reserved
8 = Timer0 (internal)
9 = Timer1 (internal)
10 = Timer 1ms (internal) (*)
11 = Serial port 0 (internal)(*)
12 = Serial port 1 (internal)(*)
13 = reserved
14 = reserved
15 = NMI (internal/external)
(* = internal used by @CHIP-RTOS, not available for user interrupt service functions)
Number of interrupts generated before new user interrupt service routine is called.
CX = 0 disables the user ISR (same as a NULL in ES:BX).
far pointer to user interrupt service routine
if pointer is NULL user ISR is disabled
Return Value
Comments
Far pointer to old handler in ES:BX
The user-defined ISR is called from a system ISR with the interrupt identifier number in the BX CPU
register, thus allowing for a single user ISR to handle multiple interrupt sources. The user ISR can be
declared in either of the following forms:
void huge My_ISR(void) ; // More efficient form
void interrupt My_ISR(void) ; // Tolerated form
The more efficient huge procedures are recommended. For assembly language ISR implementations, a
far RET is recommended and a IRET on exit is tolerated. The user ISR function must preserve only the
DS and BP registers, so there is no requirement for the full register save/restore provided by the
interrupt declarations.
Any required EOI signal is issued by the system ISR which calls your user ISR function. This EOI is
issued after your function returns.
If you install a RTX ISR you can use the following RTX calls in your ISR:
RTX_RESTART_TASK
RTX_WAKEUP_TASK
RTX_SIGNAL_SEM
Page 296 / 400