<?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>i.MX ProcessorsのトピックRe: IMX-93 Wdog interrupt clock source</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2158304#M240322</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/252662"&gt;@leoX&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;you can use a software timer for pre-watchdog monitoring.&lt;/P&gt;
&lt;P&gt;Instead of relying solely on the watchdog interrupt.&lt;/P&gt;
&lt;P&gt;1 setup a periodic software timer (GPT or PIT) to monitor system health.&lt;/P&gt;
&lt;P&gt;2 if a fault is detected, attempt recovery before the watchdog expires.&lt;/P&gt;
&lt;P&gt;3 only let the watchdog expire if recovery fails. This gives you full control over timing and avoid the tight 128-cycle constraint.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Aug 2025 12:03:07 GMT</pubDate>
    <dc:creator>danielchen</dc:creator>
    <dc:date>2025-08-26T12:03:07Z</dc:date>
    <item>
      <title>IMX-93 Wdog interrupt clock source</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2154267#M240188</link>
      <description>&lt;P&gt;&lt;SPAN&gt;What is the clock source for the wdog interrupt timing in IMX93? According to the RM, enabling the wdog interrupt provides 128 bus clock cycles for processing before a reset occurs. I understand that the bus clock frequency should be the selected 133MHz, which means there is less than 1 microsecond available. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="leoX_1-1755594071675.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/352973i7E6097B01E14D753/image-size/medium?v=v2&amp;amp;px=400" role="button" title="leoX_1-1755594071675.png" alt="leoX_1-1755594071675.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;However, when I toggle an IO pin in the interrupt and measure it with an oscilloscope, the actual interrupt duration is around 57 microseconds. So, which clock root is this timing derived from? By the way, I use the wdog1 for CM33.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="a9c31161-a8ee-4428-8294-77925609586c.jpg" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/352977i9C0DD80DC0093C27/image-size/large?v=v2&amp;amp;px=999" role="button" title="a9c31161-a8ee-4428-8294-77925609586c.jpg" alt="a9c31161-a8ee-4428-8294-77925609586c.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Aug 2025 09:06:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2154267#M240188</guid>
      <dc:creator>leoX</dc:creator>
      <dc:date>2025-08-19T09:06:14Z</dc:date>
    </item>
    <item>
      <title>Re: IMX-93 Wdog interrupt clock source</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2155168#M240221</link>
      <description>&lt;P&gt;Hi Leo:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The clock source for WDOG1&amp;nbsp; in i.MX93 is&amp;nbsp; 24Mhz oscillator (osc_24m), not the 133 MHz bus clock.&lt;/P&gt;
&lt;P&gt;The 128 cycles mentioned in the reference manual are not based on the 133MHz bus clock.&lt;/P&gt;
&lt;P&gt;You can check the actual clock rate using&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;!--ScriptorStartFragment--&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV class="scriptor-paragraph"&gt;&lt;SPAN&gt;cat&lt;/SPAN&gt; &lt;SPAN&gt;/&lt;/SPAN&gt;&lt;SPAN&gt;sys&lt;/SPAN&gt;&lt;SPAN&gt;/&lt;/SPAN&gt;&lt;SPAN&gt;kernel&lt;/SPAN&gt;&lt;SPAN&gt;/&lt;/SPAN&gt;&lt;SPAN&gt;debug&lt;/SPAN&gt;&lt;SPAN&gt;/&lt;/SPAN&gt;&lt;SPAN&gt;clk&lt;/SPAN&gt;&lt;SPAN&gt;/&lt;/SPAN&gt;&lt;SPAN&gt;clk_summary&lt;/SPAN&gt; &lt;SPAN&gt;|&lt;/SPAN&gt; &lt;SPAN&gt;grep&lt;/SPAN&gt; &lt;SPAN&gt;wdog1&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="scriptor-paragraph"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="scriptor-paragraph"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielchen_0-1755683176092.png" style="width: 754px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/353276i5CC43243B733FFF8/image-dimensions/754x51?v=v2" width="754" height="51" role="button" title="danielchen_0-1755683176092.png" alt="danielchen_0-1755683176092.png" /&gt;&lt;/span&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;SPAN&gt;&lt;!--ScriptorEndFragment--&gt;&lt;/SPAN&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2025 09:46:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2155168#M240221</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2025-08-20T09:46:52Z</dc:date>
    </item>
    <item>
      <title>Re: IMX-93 Wdog interrupt clock source</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2155730#M240235</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Daniel，&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you for your answering!&amp;nbsp;I followed your method and confirmed that it is indeed a 24MHz clock. Based on the calculations, it should be around 5us, but the actual test result shows 58us. Therefore, I would like to know if this time can be adjusted to allow my interrupt execution time to be longer so that I can perform more recording tasks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Best Regards.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 05:31:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2155730#M240235</guid>
      <dc:creator>leoX</dc:creator>
      <dc:date>2025-08-21T05:31:13Z</dc:date>
    </item>
    <item>
      <title>Re: IMX-93 Wdog interrupt clock source</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2155773#M240238</link>
      <description>&lt;P&gt;Hi Leo:&lt;/P&gt;
&lt;P&gt;The watchdog interrupt grace period on the imx93 is derived from a 24Mhz clock, and the reference manual&amp;nbsp; specifies a 128-cycle window before reset.&amp;nbsp; However, the actual&amp;nbsp; interrupt duration you measured (~57us) includes software overhead, such as interrupt latency, context switching and GPIO toggling.&lt;/P&gt;
&lt;P&gt;If you need more time before reset, you can implement a software timer that monitors system health and gives more time for recovery.&lt;/P&gt;
&lt;P&gt;Or you can try whether you can use a slower clock source (external 32khz if available.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 06:43:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2155773#M240238</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2025-08-21T06:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: IMX-93 Wdog interrupt clock source</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2155849#M240241</link>
      <description>&lt;P&gt;Hi Daniel，&lt;/P&gt;&lt;P&gt;I am toggling the IO port within the interrupt handler function and waiting for 5us each time, so this time (~57us) only accounts for the function execution time. Additionally, could you please explain in more detail the method to obtain more interrupt handling time before reset? Thank you a lot!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 08:04:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2155849#M240241</guid>
      <dc:creator>leoX</dc:creator>
      <dc:date>2025-08-21T08:04:49Z</dc:date>
    </item>
    <item>
      <title>Re: IMX-93 Wdog interrupt clock source</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2158304#M240322</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/252662"&gt;@leoX&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;you can use a software timer for pre-watchdog monitoring.&lt;/P&gt;
&lt;P&gt;Instead of relying solely on the watchdog interrupt.&lt;/P&gt;
&lt;P&gt;1 setup a periodic software timer (GPT or PIT) to monitor system health.&lt;/P&gt;
&lt;P&gt;2 if a fault is detected, attempt recovery before the watchdog expires.&lt;/P&gt;
&lt;P&gt;3 only let the watchdog expire if recovery fails. This gives you full control over timing and avoid the tight 128-cycle constraint.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Aug 2025 12:03:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX-93-Wdog-interrupt-clock-source/m-p/2158304#M240322</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2025-08-26T12:03:07Z</dc:date>
    </item>
  </channel>
</rss>

