• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 31 subscribers
  • Views 316 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM2634: MCAL driver WDG

Panda Bear
Intellectual 375 points
Part Number: AM2634

Hello 

I try to test the WDG Example Code from MCAL_AM263x_00.09.00_03. I got the outputs below:

Is the output correct? The test never reaches to pass line in the code. Do I have to set something?

The code is runned on the eval board. 

Thank you 

  • 0
    TI__Genius 15435 points

    Hi 

    The WDG app is running correctly, the WDG application will basically overflow the watchdog and once the overflow occurs a reset is issued, this is the reason you're seeing the gibberish numbers and the character "C" being printed continously every few seconds. The application is working fine.

    Thanks

  • 0 in reply to Kowshik Gudimetla
    Intellectual 375 points

    thank you for your reply. 

    Just to understand better the driver, I have several question?

    1. How can I check, that the Watchdog reset is executed?

    2. In the driver there is a code part, which is shown below:

     

    when will the software reach this part when the code is executed?

    Thanks

  • 0 in reply to Panda Bear
    TI__Genius 15435 points

    Hi,

    Panda Bear said:
    1. How can I check, that the Watchdog reset is executed?

    You can directly monitor this register 0x5320000C through the memory browser, it shows the reset cause. If it's through WDT0 the reset cause is 0x43 and so on as per the below register description.

    I have tried with MCU SDK example by running the WDT2 instance and I got the rest cause as 0x49 which is correct according to the above table.

    Panda Bear said:
    In the driver there is a code part, which is shown below:

    This part is never reached during a correct execution of the program and it is expected to not execute this line too. 

  • 0 in reply to Kowshik Gudimetla
    Intellectual 375 points

    Hi,

    The Watchdog is triggered when the QSPI Boot is on; but when the Boot mode is on No Boot or Uart then the Wdg is not triggered. 

    Could you explain this behavior?

    Thanks

  • 0 in reply to Panda Bear
    TI__Genius 15435 points

    Hi,

    Let me try this out at my end and come with an explanation. Ideally there shouldn't major difference, and also please note that do no try to load any program in UART boot mode with CCS, it is only used to get the images and flash them at the moment.

  • 0 in reply to Panda Bear
    TI__Genius 15435 points

    Hi

    I have verified the behaviour at my end, I don't see this kind of difference, the WDG POR reset is triggerred in any mode and the SoC is reset properly. We're re-designing the WDG app example to properly find the reset cause and the example exits the code automatically.

    It will be available in the upcoming release.

    Thanks,
    G kowshik