• State
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 83 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TMS320F280039C: Reasons for entering Interrupt_defaultHandler()

Zhen He
Prodigy 230 points
Part Number: TMS320F280039C
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hello, Ti experts.

When I was testing the program, I found that the program entered Intrrupt_defaultHandler(), which should be the reason why I did not assign the interrupt service function. But how can I tell from the pieVect and vectID values what is generating the interrupt event?

  • 0
    TI__Expert 7240 points

    Hi Zhen,

    Are you running one of the examples in C2000ware? If so, can you point me to the path of the example so I can take a look?

    Since the value read into pieVect is 0, vector fetching has not even been enabled since the ENPIE bit is not set (bit 0 of the PIECTRL register, see below):

    Is Interrupt_initModule() called during the initialization code?

    Best Regards,

    Delaney

  • 0 in reply to Delaney Woodward
    Prodigy 230 points

    Hi Delaney,

    This is the program I'm using and not a Ti routine. The Interrupt_initModule() function is called during initialization. So is there any other way to find out why? thank you.

  • 0 in reply to Zhen He
    TI__Expert 7240 points

    Hi Zhen,

    Can you step through your code and verify that when you step over the last line of  Interrupt_initModule(), the ENPIE bit gets set in the Register View? Make sure to enable continuous refresh.

    You can also verify that you are calling the initialization functions in the right order (you should match the order of the C2000ware example).

    Best Regards,

    Delaney