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.

TMS320F28P559SJ-Q1: System from getting stuck, when wrongly entered Interrupt_defaultHandler

Part Number: TMS320F28P559SJ-Q1

Tool/software:

Hi 
In my customer's application, the MCU receives data using the FIFO mode of the Serial Communications Interface (SCI).

We observe that when the transmission sends data at a too high frequency, The program will jump in to the Interrupt_defaultHandler and cannot go out from this handler, causing the system to crash.

Although the Watchdog Timer (WDT) feature is enabled, it does not appear to be functional in this case and can only be recovered through a system restart.

We would like to know. Is there a mechanism for the program to automatically pop out or recover to prevent the system from getting stuck?

  • Hello,

    The application going into the default handler usually would not be caused by the SCI module. If data is received on the SCI too quickly, the module will set the overrun flag in the SCIRXST register. 

    The default handler will be branched to when the PIE doesn't find a corresponding ISR address for the interrupt in the vector table. Can you verify that the customer is correctly calling the Interrupt_register() function with their ISR function name?

    Best Regards,

    Delaney