• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 443 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.

SK-AM64B: Queries on RTI / Watchdog module

Amey P
Intellectual 320 points

Part Number: SK-AM64B

Hello

As per the TRM of AM64x, the RTI module is used to support the watchdog functionality. As understood from the TRM, it supports two DWWD (Digital Windowed Watchdog) and

DWD (Digital Watch dog) per RTI instance. 

a. Why are there two separate modules (DWWD & DWD)? Any specific use case where both can be used at a time?

b. Is DWD similar to a simple Watchdog where the application has to feed the watchdog before timeout else it will cause system to reset or generate an NMI?

c. Is there any key difference between these modules (apart from the concept of window mechanism for DWWD)

Thanks

Amey

  • 0
    TI__Guru**** 234225 points

    Hello Amey,

    Thank you for the query.

    Help me understand the use case.
    Are you performing any tests and observing any issue.
    Help me understand the development environment that you are using?

    Regards,

    Sreenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    Intellectual 320 points

    Hello Sreenivasa

    I am currently evaluating the AM64x EVK and I was trying to understand the RTI module. 

    The use case would be to use the watchdog in the end application (non rtos on R5 core). For now I would use the Code Composer Studio as IDE

    Thanks

    Amey

  • +1 in reply to Amey P
    TI__Guru 55678 points

    Hello Amey ,

    Sorry for delayed response .

    Actually, I can say that DWD and DWWD modules are the same and there is no difference and the only difference is the window size configuration.

    For example, if you configure Window size 100%, then DWWD can be run as normal Timer and after the timer is expired watchdog to generate either a Reset or a non-maskable interrupt to the SOC.

    And if you configure a window size other than 100%, then any attempt give watchdog's key outside of the watchdog time window, or a failure to service the watchdog in this time window, will cause the watchdog to generate either a reset or a non-maskable interrupt to the SOC.

    I hope above answers will clear your queries .

    Regards,

    S.Anil.