We have used uart A0 ,A1,B1. interuupt handelers are also there for all. but still it eneters in isr trap routine. shows some time oscilator interrupt flag / power on interrupt flag set?
how to get out of this issue?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
We have used uart A0 ,A1,B1. interuupt handelers are also there for all. but still it eneters in isr trap routine. shows some time oscilator interrupt flag / power on interrupt flag set?
how to get out of this issue?
We are using uart A1 ,uart A0 ,I2C & timer A0,A1 interrupts . Issue is, at some point, due to some unknown interrupt ,code gets trapped in Isr trap code . We have now added interrupt routines for NMI ,Timer B0,B1 , WDT, port2 interrupts to find out which interrupt is causing the code to jump in ISR trap routine. Still not able to get out it .
Hi,
please have a look in this e2e thread. It talks about ISR trap routine and ways how to handle it.
One reason why you might be caught in the ISR trap routine are interrupt flags which are not self clearing. You need to clear them manually.
Usually you shouldn't use the ISR trap routine, but have specific ISR for each type of interrupt you expect (timer, port, ADC, etc...).
Best regards,
Andre
Hi Kalpana,
Is the application you are running a TI example application or a TI application that was modified? Is it customized code?
If you are using CCS or IAR, you should be able to step through your code using breakpoints to see where the program is failing. Then at the point of failure, drill down into the APIs to find the exact point of failure. It is probably some variable not initialized properly or its being set to a value that is not correct.
You can also verify that the UART interrupts are firing by placing breakpoints within the handlers.
Regards,
Arthi
**Attention** This is a public forum