• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 84 subscribers
  • Views 417 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28386S: Unassigned interrupt

John Hite
Expert 1355 points
Part Number: TMS320F28386S


The serial flash tool and my project are communicating a bit, autobaud even works. However, I am crashing in Interrupt_defaultHandler(). It tells me

"To help you debug the issue, local
    // variable vectID contains the vector ID of the interrupt that occurred."

However, breakpoints do not work in the ISR and it is not showing up in the variable watch. Is there some way to find it out without copying to a global and doing something like a long jump.

I have not worked with interrupts on this device yet but hope to find an example repo to get up to speed. Is there an Academy chapter or similar on interrupts.

Thanks,

John

  • 0
    Expert 1355 points

    longjmp does not work either. I changed Interrupt_defaultHandler() so that it should return instead of stopping on an infinite loop but my changes are ignored though project has been cleaned.

  • 0 in reply to John Hite
    TI__Mastermind 19795 points

    Hi John,

    Thanks for your question. Can you try adding vectID to the "Watch Expressions" window in CCS and view its value while the code is at the ESTOP in "Interrupt_defaultHandler()"? Please provide this value.

    Breakpoints like ESTOP should work without issue if you are in debugger mode in CCS (by running using "Debug" instead of direct loading the code and disocnnecting).

    Regards,

    Vince

  • 0 in reply to Vince
    Expert 1355 points

    Should have mentioned I tried adding a watch. The value is "identifier not found: vectID "      

  • 0 in reply to John Hite
    TI__Mastermind 19795 points

    Hi John,

    Thanks for the follow-up, can you provide a screenshot of the call stack when the error is paused at the breakpoint? I'm wondering if the trace is actually lower in the call stack (in a sub-function) instead of in the actual Interrupt_defaultHandler() function. If you could provide the full CCS window with the call stack visible, that would be great.

    Thanks!

    Regards,

    Vince