• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 309 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.

TMS320F28377S: Knowing where was the Code (PC) when Watchdog reset occurs

A GIR
Genius 3615 points

Part Number: TMS320F28377S
Other Parts Discussed in Thread: C2000WARE

Hello,

According a scenario, I get a Watchdog reset.

In others word, there is something too ling into my code which lead to trig the Reset by the Watchdog.

So the Watchdog do a good job!

Now, I'm looking for what part of my code is too long.
Is it possible to know the Counter Program (PC) value when the WDG reset Occurs?

I tried to catch the WDG reset by configure it on "Interrupt" mode, but the PIEIFR1.INTx8 is never Set. (I configure LPMCR.WDINTE to 1, SCSR.WDENINT to 1...

If I set manualy the PIEIFR1.INTx8, The cpu jump to the ISR routine...

But I'm sure to generate a watchdog event, but never the Int1.8 is set..

-1) How know the PC address at the moment where the WTG reset occurs

2) Alternative solution: What I missed to jump to an interrput on WDG event? (By this way, with the debugger, I can see the Stack and knwow the function executing when Event occurs...)

  • 0
    TI__Guru* 95315 points
    A GIR said:
    Is it possible to know the Counter Program (PC) value when the WDG reset Occurs?

    Not when the WD generates a reset.

    A GIR said:
    -1) How know the PC address at the moment where the WTG reset occurs

    Not sure if identifying the function where WD reset was generated would help, since that function by itself may not be taking too much time but the preceding functions do.

    A GIR said:
    What I missed to jump to an interrput on WDG event?

    Please try the tested example in C:\ti\c2000\C2000Ware_4_01_00_00\driverlib\f2837xs\examples\cpu1\watchdog.