<?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 Re: the PLL error of the s32k312 in ppm in S32K</title>
    <link>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1711390#M26463</link>
    <description>Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/201913"&gt;@VaneB&lt;/a&gt;&lt;BR /&gt;&lt;BR /&gt;Is that right?</description>
    <pubDate>Fri, 25 Aug 2023 09:18:00 GMT</pubDate>
    <dc:creator>dongyong1</dc:creator>
    <dc:date>2023-08-25T09:18:00Z</dc:date>
    <item>
      <title>the PLL error of the s32k312 in ppm</title>
      <link>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1710027#M26402</link>
      <description>&lt;P&gt;Dear NXP Engineers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to know what is the PLL error of the s32k312 in ppm&lt;/P&gt;</description>
      <pubDate>Wed, 23 Aug 2023 15:17:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1710027#M26402</guid>
      <dc:creator>dongyong1</dc:creator>
      <dc:date>2023-08-23T15:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: the PLL error of the s32k312 in ppm</title>
      <link>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1710129#M26404</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/200612"&gt;@dongyong1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sorry for the inconvenience this may cause.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;All information related to the PLL jitter is provided in Table 41 of the&amp;nbsp;S32K3xx Data Sheet, Rev. 8.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;B.R.&lt;/P&gt;
&lt;P&gt;VaneB&lt;/P&gt;</description>
      <pubDate>Wed, 23 Aug 2023 21:07:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1710129#M26404</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2023-08-23T21:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: the PLL error of the s32k312 in ppm</title>
      <link>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1710200#M26411</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;VaneB&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;take the last line of Table41 as an example(1680ps 120Mhz). Is it possible to calculate like this: 1/120MHZ=8.3ns, 1680ps/8.3ns=0.2. (0.2/120M)*1000000=0.002ppm&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dongyong1_0-1692841739259.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/237731iBC40700EEF983E3E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dongyong1_0-1692841739259.png" alt="dongyong1_0-1692841739259.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 01:49:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1710200#M26411</guid>
      <dc:creator>dongyong1</dc:creator>
      <dc:date>2023-08-24T01:49:42Z</dc:date>
    </item>
    <item>
      <title>Re: the PLL error of the s32k312 in ppm</title>
      <link>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1711390#M26463</link>
      <description>Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/201913"&gt;@VaneB&lt;/a&gt;&lt;BR /&gt;&lt;BR /&gt;Is that right?</description>
      <pubDate>Fri, 25 Aug 2023 09:18:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1711390#M26463</guid>
      <dc:creator>dongyong1</dc:creator>
      <dc:date>2023-08-25T09:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: the PLL error of the s32k312 in ppm</title>
      <link>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1712580#M26523</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/200612"&gt;@dongyong1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These two specs are about entirely different things. So, I think converting the ps to ppm is not possible.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Frequency is the number of cycles executed per second. Otherwise, the jitter is about the variance of the clock period. So, if your clock period varies randomly by 10ns RMS (for example), but the period is still 1µs on average, then you can have a very accurate (but jittery) 1MHz clock.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 18:42:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/the-PLL-error-of-the-s32k312-in-ppm/m-p/1712580#M26523</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2023-08-28T18:42:28Z</dc:date>
    </item>
  </channel>
</rss>

