<?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>S32KのトピックRe: Why CMU should run on a different clock than WDOG?</title>
    <link>https://community.nxp.com/t5/S32K/Why-CMU-should-run-on-a-different-clock-than-WDOG/m-p/1960215#M41266</link>
    <description>&lt;P&gt;Got it. Thank you.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Sep 2024 01:39:37 GMT</pubDate>
    <dc:creator>longyi1234</dc:creator>
    <dc:date>2024-09-24T01:39:37Z</dc:date>
    <item>
      <title>Why CMU should run on a different clock than WDOG?</title>
      <link>https://community.nxp.com/t5/S32K/Why-CMU-should-run-on-a-different-clock-than-WDOG/m-p/1949507#M40664</link>
      <description>&lt;P&gt;Why CMU should run on a different clock than WDOG?&lt;/P&gt;&lt;P&gt;The chip I use is S32K1xx. This is what the Reference Manual says:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="longyi1234_0-1725787753305.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/297731iA23CAA5400019A3E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="longyi1234_0-1725787753305.png" alt="longyi1234_0-1725787753305.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 08 Sep 2024 09:30:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Why-CMU-should-run-on-a-different-clock-than-WDOG/m-p/1949507#M40664</guid>
      <dc:creator>longyi1234</dc:creator>
      <dc:date>2024-09-08T09:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: Why CMU should run on a different clock than WDOG?</title>
      <link>https://community.nxp.com/t5/S32K/Why-CMU-should-run-on-a-different-clock-than-WDOG/m-p/1950068#M40716</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;the reason is simple: if clock of CMU fails, the watchdog resets application (because is running on another clock) - assuming that CMU's reset is the safe state. Next actions depend on supervisor system.&lt;/P&gt;
&lt;P&gt;If CMU and watchdog share the same clock, the application got stuck during clock malfunction.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Mon, 09 Sep 2024 12:11:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Why-CMU-should-run-on-a-different-clock-than-WDOG/m-p/1950068#M40716</guid>
      <dc:creator>PavelL</dc:creator>
      <dc:date>2024-09-09T12:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: Why CMU should run on a different clock than WDOG?</title>
      <link>https://community.nxp.com/t5/S32K/Why-CMU-should-run-on-a-different-clock-than-WDOG/m-p/1960215#M41266</link>
      <description>&lt;P&gt;Got it. Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Sep 2024 01:39:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Why-CMU-should-run-on-a-different-clock-than-WDOG/m-p/1960215#M41266</guid>
      <dc:creator>longyi1234</dc:creator>
      <dc:date>2024-09-24T01:39:37Z</dc:date>
    </item>
  </channel>
</rss>

