<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic S32DS watchdog timer not trigering reset in S32 SDK</title>
    <link>https://community.nxp.com/t5/S32-SDK/S32DS-watchdog-timer-not-trigering-reset/m-p/904993#M995</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am currently working with the s32k148 eval board ,using the S32 Design studio for ARM Version : 2.1 Build Id 170810&lt;/P&gt;&lt;P&gt;and am trying to configure a watch dog timer , which should trigger a reset every 256 ms if not serviced .&lt;/P&gt;&lt;P&gt;for this I have configured the LPO clock (128KHz) as&amp;nbsp; the input clock and set the value of 16384 to the TOVAL register and to just make sure that the watch dog basic functionality is fine, i am not refreshing the watchdog.&lt;/P&gt;&lt;P&gt;but unexpectedly the watchdog is not trigering any reset and after few seconds I can see the counter value in the Pemicro console dispalyed with the incrementing value as can be seen in the below snapshot.&lt;/P&gt;&lt;P&gt;I would like to understand that why if the program allowed to still run and what does this values in the console means.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;main()&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CLOCK_SYS_Init(g_clockManConfigsArr, CLOCK_MANAGER_CONFIG_CNT,g_clockManCallbacksArr, CLOCK_MANAGER_CALLBACK_CNT);&lt;BR /&gt; CLOCK_SYS_UpdateConfiguration(0U, CLOCK_MANAGER_POLICY_AGREEMENT);&lt;BR /&gt; PINS_DRV_Init(NUM_OF_CONFIGURED_PINS, g_pin_mux_InitConfigArr);&lt;BR /&gt; WDOG_DRV_Init(INST_WATCHDOG1, &amp;amp;Window_watchdog);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;the below is the watch dog configuration structure.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/*! watchdog1 configuration structures */&lt;/P&gt;&lt;P&gt;const wdog_user_config_t Window_watchdog = {&lt;BR /&gt; .clkSource = WDOG_LPO_CLOCK,&lt;BR /&gt; .opMode = {&lt;BR /&gt; false, /* Wait Mode*/&lt;BR /&gt; false, /* Stop Mode*/&lt;BR /&gt; true /* Debug Mode*/&lt;BR /&gt; },&lt;BR /&gt; .updateEnable = true,&lt;BR /&gt; .intEnable = true,&lt;BR /&gt; .winEnable = false,&lt;BR /&gt; .windowValue = 16384,&lt;BR /&gt; .timeoutValue = 16384,&lt;BR /&gt; .prescalerEnable = false&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/83595i066F59BF7FC7E3E7/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 May 2019 16:08:31 GMT</pubDate>
    <dc:creator>satish_k_singh</dc:creator>
    <dc:date>2019-05-22T16:08:31Z</dc:date>
    <item>
      <title>S32DS watchdog timer not trigering reset</title>
      <link>https://community.nxp.com/t5/S32-SDK/S32DS-watchdog-timer-not-trigering-reset/m-p/904993#M995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am currently working with the s32k148 eval board ,using the S32 Design studio for ARM Version : 2.1 Build Id 170810&lt;/P&gt;&lt;P&gt;and am trying to configure a watch dog timer , which should trigger a reset every 256 ms if not serviced .&lt;/P&gt;&lt;P&gt;for this I have configured the LPO clock (128KHz) as&amp;nbsp; the input clock and set the value of 16384 to the TOVAL register and to just make sure that the watch dog basic functionality is fine, i am not refreshing the watchdog.&lt;/P&gt;&lt;P&gt;but unexpectedly the watchdog is not trigering any reset and after few seconds I can see the counter value in the Pemicro console dispalyed with the incrementing value as can be seen in the below snapshot.&lt;/P&gt;&lt;P&gt;I would like to understand that why if the program allowed to still run and what does this values in the console means.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;main()&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CLOCK_SYS_Init(g_clockManConfigsArr, CLOCK_MANAGER_CONFIG_CNT,g_clockManCallbacksArr, CLOCK_MANAGER_CALLBACK_CNT);&lt;BR /&gt; CLOCK_SYS_UpdateConfiguration(0U, CLOCK_MANAGER_POLICY_AGREEMENT);&lt;BR /&gt; PINS_DRV_Init(NUM_OF_CONFIGURED_PINS, g_pin_mux_InitConfigArr);&lt;BR /&gt; WDOG_DRV_Init(INST_WATCHDOG1, &amp;amp;Window_watchdog);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;the below is the watch dog configuration structure.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/*! watchdog1 configuration structures */&lt;/P&gt;&lt;P&gt;const wdog_user_config_t Window_watchdog = {&lt;BR /&gt; .clkSource = WDOG_LPO_CLOCK,&lt;BR /&gt; .opMode = {&lt;BR /&gt; false, /* Wait Mode*/&lt;BR /&gt; false, /* Stop Mode*/&lt;BR /&gt; true /* Debug Mode*/&lt;BR /&gt; },&lt;BR /&gt; .updateEnable = true,&lt;BR /&gt; .intEnable = true,&lt;BR /&gt; .winEnable = false,&lt;BR /&gt; .windowValue = 16384,&lt;BR /&gt; .timeoutValue = 16384,&lt;BR /&gt; .prescalerEnable = false&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/83595i066F59BF7FC7E3E7/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 May 2019 16:08:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/S32DS-watchdog-timer-not-trigering-reset/m-p/904993#M995</guid>
      <dc:creator>satish_k_singh</dc:creator>
      <dc:date>2019-05-22T16:08:31Z</dc:date>
    </item>
  </channel>
</rss>

