infineon4engineers Facebook

infineon@google+ Google+

infineon@linkedin linkedin

infineon4engi@twitter twitter

infineon@youtube youtube

+ Reply to Thread
Results 1 to 5 of 5

Thread: Hitex XMC1300 Class B Watchdog POST Timing

  1. #1
    Scott is on a distinguished road
    Join Date
    Aug 2015
    Posts
    4
    Points
    62.5

    Hitex XMC1300 Class B Watchdog POST Timing

    I have a project that uses the XMC1300 Class B library provided by Hitex. The watchdog timer power-on self-test (POST) can be configured with #defines located in ClassB_config.h that set the watchdog timer lower bound (ClassB_TEST_POST_WDOG_WLB) and the watchdog timeout (ClassB_TEST_POST_WDOG_TIME).

    The comment for ClassB_TEST_POST_WDOG_WLB states:
    Code:
    // <o>Timeout WLB value for the WDT <4000-60000>
    // <i> Define the Timeout lower boundary for the WDT.
    // <i> Default: 4000
    #define ClassB_TEST_POST_WDOG_WLB       4000
    Using the minimum value of 4000 results in the system not meeting a maximum start-up delay time requirement. If I reduce the values of ClassB_TEST_POST_WDOG_WLB and ClassB_TEST_POST_WDOG_TIME to less than 4000, I am able to meet the start-up time requirement. It is unclear to me why 4000 is noted as the minimum value in the comments. The watchdog timer can be configured with lower values, and the test appears to be functioning correctly with a lower value.

    Is it ok to use values lower than 4000 for ClassB_TEST_POST_WDOG_WLB? If not, what is the limitation?

    I currently have it configured with these values, which seem to work fine:
    Code:
    #define ClassB_TEST_POST_WDOG_TIME      200
    #define ClassB_TEST_POST_WDOG_WLB       100
    Thanks!

  2. #2
    Travis will become famous soon enough
    Join Date
    Feb 2013
    Location
    Singapore
    Posts
    749
    Points
    4580
    Hi Scott,

    you can make use of the DAVE4 apps to re check on your WDT. Attached is a WDT project using XMC1200 for your reference.

    Best Regards
    Travis
    ?????

  3. #3
    Scott is on a distinguished road
    Join Date
    Aug 2015
    Posts
    4
    Points
    62.5
    Hi Travis,

    Thanks for the reply. I have the watchdog timer working, both for the POST test done by the Class B library on startup as well as during the normal operation of my code after the POST tests are complete.

    My question is specifically about the Hitex Class B safety library WDT POST test. The comment in the library code (ClassB_config.h) indicates a minimum value of 4000 to be used as the minimum timeout value. I don't see anything in the documentation for the Class B safety library, or for the XMC1300, to indicate that 4000 is indeed a minimum limit for the timeout.

    I have the watchdog POST test passing with a value <4000 as the watchdog timeout, but I'm looking for verification from someone that is familiar with the Class B safety library that my timeout value is ok for the test.

    Do you know why the range of values for the watchdog timeout is specified as 4000-60000 in ClassB_config.h?

  4. #4
    Travis will become famous soon enough
    Join Date
    Feb 2013
    Location
    Singapore
    Posts
    749
    Points
    4580
    Hi Scott,

    Maybe you can discuss this with Hitex as they are the developer of the safety library.

    Best Regards
    Travis

  5. #5
    Scott is on a distinguished road
    Join Date
    Aug 2015
    Posts
    4
    Points
    62.5
    I heard back from Hitex that the settings I've used are ok.

    The real limit is: ClassB_TEST_POST_WDOG_TIME > ClassB_TEST_POST_WDOG_WLB > 0

+ 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.