Banner_AURIX_Security-Solution Banner_AURIX_Security-Solution Banner_AURIX_Security-Solution


infineon4engineers Facebook

infineon@google+ Google+

infineon@linkedin linkedin

infineon4engi@twitter twitter

infineon@youtube youtube

+ Reply to Thread
Results 1 to 7 of 7

Thread: WDT Counter behavior (not count down) on Application Kit TC27x / TC29x

  1. #1
    Beginner Beginner shimizus3106 is on a distinguished road
    Join Date
    Jul 2019
    Posts
    5
    Points
    70

    WDT Counter behavior (not count down) on Application Kit TC27x / TC29x

    WDT Counter behavior (not count down) on Application Kit TC27x / TC29x

    Dear Forum members,

    I have question about using Watch doc timer of Application Kit TC27x / TC29x.

    To use configure the function, I'm refering AP32019 below,
    https://www.infineon.com/dgdl/ap3201...12b41c3ba42d89


    Here is my code to call function to check like below.

    ...

    WDT_Passwd();

    WDT_Modify(0x0000 0000, 0x0000 0000); // ENDINIT clear
    [or WDT_Modify(0x00FF 0000, 0xFFFF 0000);] // ENDINIT clear, RELAOD value

    /* some operation to check counter, or trap occur */
    /* So the func is to execute long duration here */

    WDT_Modify(0x0000 000F, 0x0000 000F); // ENDINIT set

    I check status reg - WDTTIM (or other flag) during the operation to check counter or trap occur.
    there is no change - no coutner dcrement or no interrupt happen...

    I dont know why such behavior is.. WDT doesnt start ??


    Could you let me know if I mistake something ? and let me know how to configure ? (example code is beter to me)


    Best Regards,
    Shige

  2. #2
    Advanced Advanced cwunder is on a distinguished road
    Join Date
    Feb 2015
    Location
    USA
    Posts
    101
    Points
    1897.5
    Some comments:
    1) The Watchdog timers only count up (they do not count down)
    2) The Watchdog timers are enabled by default after reset, however if you are connected to a debugger they are by default disabled. Depending on the debugger there is a command to enable them while debugging or you can directly do this with your code.
    3) It is not clear to me what you what to achieve with the watchdog? Which watchdog?

  3. #3
    Beginner Beginner shimizus3106 is on a distinguished road
    Join Date
    Jul 2019
    Posts
    5
    Points
    70
    Hello.

    thank you for your message.

    Regarding to 1),2), here is my current situation

    Those related registers status are below:


    WDT Control register 0 is :
    (reset) 0xfffc000f -> 0xfffc000e / Reload: 0xfffc , endinit: 0
    WDT Control register 1 is :
    -> 0x000000 / enable Watchdog timer
    WDT Status register is : -> 0xfffc0010 / time-out mode, reflect the current contents of WDT ;0xfffc

    about 3),
    I want to check the function behavior normal WDT, not safty.

    From register status, it seems that WDT enable and start, but no trap, interrupt and no change counter number even if without changing endinit :1.

    something wrong with my sequence and understanding ?

    Best regards,
    Shige

  4. #4
    Beginner Beginner shimizus3106 is on a distinguished road
    Join Date
    Jul 2019
    Posts
    5
    Points
    70
    Hi.

    After that, I tried and checked WDT functionality with IFX software framework, iLLD_1_0_1_10_0__TC2x and iLLD_1_0_1_10_0__TC2x Demos. (Compiler,debugger: TASKING)

    Consequently, API - IfxScuWdt_enableWatchdogWithDebugger() was required to run well.

    What the API is doing ?

    Best regards,
    Shige

  5. #5
    Advanced Advanced cwunder is on a distinguished road
    Join Date
    Feb 2015
    Location
    USA
    Posts
    101
    Points
    1897.5
    For ease of use the AURIX has the capability to suspend the watchdogs when connected to a debugger (default setting). This is to avoid nuisance watchdog timeouts that will reset your system while you are developing your code.

    This API is writing to a debug specific register that allows the watchdogs to run when the debugger (connected) is running and pause it when you halt or break your program execution. With this setting the watchdog timeout behavior will act as it would when you don't have a debugger connected. This will allow you to determine if your watchdog servicing is proper (the right timeout value).

  6. #6
    New Member New Member s-shige is on a distinguished road
    Join Date
    Jun 2019
    Posts
    1
    Points
    40
    Thank you for the information.

    >>This API is writing to a debug specific register that allows the watchdogs to run when the debugger (connected) is running

    Where can we get the information about the register ?

    As I checked some spec but I couldn't find.
    I only know that we need some treatment when using debugger.

    Best regards,
    Shige

  7. #7
    Advanced Advanced cwunder is on a distinguished road
    Join Date
    Feb 2015
    Location
    USA
    Posts
    101
    Points
    1897.5
    As I checked some spec but I couldn't find.
    I only know that we need some treatment when using debugger.
    Is there something else you need as you have the API or a tooling command to accomplish the task at hand.

    The user's manual states the distribution of the OCDS documentation is restricted.

+ Reply to Thread

Tags for this Thread

Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.