This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RTX OS goes into idle state after running for awhile

Hi all,

I am using the MCBSTR9 board and I am running the RTX OS with two concurrent tasks. All is well but after it runs for awhile, it stops. When I break in, it sits in the OS idle loop. Have anyone experience this before? It does not crash but it somehow stopped running the two tasks that was initially running. The stop time is intermediate. It can run up to 30 minutes or as short as 5 minutes.

Any ideas?

Thanks,
Tom

Parents

0 ImPer Westermark over 16 years ago in reply to Tom Tran

So they are sharing a mutex, but you get a lockup even if neither of the threads takes this mutex?

Is your timer tick still running?

Are you able to use a JTAG interface to check the current state of the two tasks?
Cancel
Vote up 0 Vote down

Cancel

Reply

0 ImPer Westermark over 16 years ago in reply to Tom Tran

So they are sharing a mutex, but you get a lockup even if neither of the threads takes this mutex?

Is your timer tick still running?

Are you able to use a JTAG interface to check the current state of the two tasks?
Cancel
Vote up 0 Vote down

Cancel

Children

0 Tom Tran over 16 years ago in reply to ImPer Westermark

Actually, after further testing, I found out that the I2C and UART interrupts are conflicting. Which I think is another topic dealing with nested interrupts.
Cancel
Vote up 0 Vote down

Cancel