Hi,
When I wrote driver for COM1 or COM2 with InterruptAttach() function and
ISR Handler separately, they both work fine independently. When I put
two ISRs for both COM1 and COM2 together in each thread, the program
will have Memory Fault
(Core Dump). For COM1, InterruptAttach() and InterruptWait() are in
thread1; while for COM2, InterruptAttach() and InterruptWait() are in
thread2. It seems that kernel mess the event from InterruptWait().
Another thing I did is that in Handler of COM2 the return NULL is always
given, however, the problem is still there. Hence my question is that
whether QNXRTP supports multiple ISR in different threads independently
or in same thread. The answer for me should be positive!
Regards!
YUNCHUN YANG
PLEASE do not cross post.
“Yang, Yunchun” <yyang@ee.ucr.edu> wrote in message
news:3A78B15A.6FCCFE4B@ee.ucr.edu…
Hi,
When I wrote driver for COM1 or COM2 with InterruptAttach() function and
ISR Handler separately, they both work fine independently. When I put
two ISRs for both COM1 and COM2 together in each thread, the program
will have Memory Fault
(Core Dump). For COM1, InterruptAttach() and InterruptWait() are in
thread1; while for COM2, InterruptAttach() and InterruptWait() are in
thread2. It seems that kernel mess the event from InterruptWait().
Another thing I did is that in Handler of COM2 the return NULL is always
given, however, the problem is still there. Hence my question is that
whether QNXRTP supports multiple ISR in different threads independently
or in same thread. The answer for me should be positive!
Regards!
YUNCHUN YANG