<?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のトピックParameter constraints for i.MX6 spread-spectrum clocking?</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743651#M115707</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear i.MX-Community&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We're using i.MX6-SoCs (Solo, DualLite, Dual, Quad, and QuadPlus) on several different custom board designs. We're using the spread-spectrum feature of the 528 MHz "system PLL" and didn't have any issues with these, so far. For a new board-design we needed somewhat "more aggressive" spreac-spectrum settings, so we started testing with several different parameters, during which we noticed strange behavior: a different parameter-set from our default settings, which should result in the same frequency-settings, results in a very unstable system (segmentation faults, exceptions, corrupted data reads from memory, etc. under Yocto-Linux with 4.1.15 kernel).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To be more specific (on an i.MX6D):&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;PLL_SYS_SS[STOP] = 250, PLL_SYS_SS[STEP] = 1, PLL_SYS_DENOM[B] = 400 works fine without any problems on all devices.&lt;/LI&gt;&lt;LI&gt;PLL_SYS_SS[STOP] = 500, PLL_SYS_SS[STEP] = 2, PLL_SYS_DENOM[B] = 800 on &lt;SPAN style="text-decoration: underline;"&gt;some devices&lt;/SPAN&gt; results in the Linux kernel crashing sooner or later (sometimes already during the boot-process, sometimes after a couple of minutes) on almost every boot.&amp;nbsp;Some few&amp;nbsp;identically equipped devices don't seem to have problems with these settings, though.&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;(PLL_SYS_NUM[A] is set to the default value of 0 in either case)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Either setting should result in the same&amp;nbsp;spread spectrum range of 15 MHz and modulation frequency of 48 KHz and verification with an oscilloscope by configuring the CLKO2-output to "mmdc_ch0_clk_root/7" shows that the clock seems to be behaving as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any constraints on valid combinations of parameters, that should be followed for the spread-spectrum settings? I can't seem to find any constraints being mentioned in the reference manual, datasheet or application notes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Jan 2018 13:00:52 GMT</pubDate>
    <dc:creator>MOW</dc:creator>
    <dc:date>2018-01-22T13:00:52Z</dc:date>
    <item>
      <title>Parameter constraints for i.MX6 spread-spectrum clocking?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743651#M115707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear i.MX-Community&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We're using i.MX6-SoCs (Solo, DualLite, Dual, Quad, and QuadPlus) on several different custom board designs. We're using the spread-spectrum feature of the 528 MHz "system PLL" and didn't have any issues with these, so far. For a new board-design we needed somewhat "more aggressive" spreac-spectrum settings, so we started testing with several different parameters, during which we noticed strange behavior: a different parameter-set from our default settings, which should result in the same frequency-settings, results in a very unstable system (segmentation faults, exceptions, corrupted data reads from memory, etc. under Yocto-Linux with 4.1.15 kernel).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To be more specific (on an i.MX6D):&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;PLL_SYS_SS[STOP] = 250, PLL_SYS_SS[STEP] = 1, PLL_SYS_DENOM[B] = 400 works fine without any problems on all devices.&lt;/LI&gt;&lt;LI&gt;PLL_SYS_SS[STOP] = 500, PLL_SYS_SS[STEP] = 2, PLL_SYS_DENOM[B] = 800 on &lt;SPAN style="text-decoration: underline;"&gt;some devices&lt;/SPAN&gt; results in the Linux kernel crashing sooner or later (sometimes already during the boot-process, sometimes after a couple of minutes) on almost every boot.&amp;nbsp;Some few&amp;nbsp;identically equipped devices don't seem to have problems with these settings, though.&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;(PLL_SYS_NUM[A] is set to the default value of 0 in either case)&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Either setting should result in the same&amp;nbsp;spread spectrum range of 15 MHz and modulation frequency of 48 KHz and verification with an oscilloscope by configuring the CLKO2-output to "mmdc_ch0_clk_root/7" shows that the clock seems to be behaving as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any constraints on valid combinations of parameters, that should be followed for the spread-spectrum settings? I can't seem to find any constraints being mentioned in the reference manual, datasheet or application notes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 13:00:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743651#M115707</guid>
      <dc:creator>MOW</dc:creator>
      <dc:date>2018-01-22T13:00:52Z</dc:date>
    </item>
    <item>
      <title>Re: Parameter constraints for i.MX6 spread-spectrum clocking?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743652#M115708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;recommended ddr dithering range is about 1%, for i.MX6 there are no special&lt;/P&gt;&lt;P&gt;restrictions for combinations of parameters. If some modules use that clock,&lt;/P&gt;&lt;P&gt;it is necessary to consider how dithering clock may affect them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 23:18:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743652#M115708</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-01-22T23:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: Parameter constraints for i.MX6 spread-spectrum clocking?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743653#M115709</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there are no restrictions for combinations of parameters, how come that one set of parameters works fine, while the other - resulting in the same final modulation effects - does not work stable at all on the same board?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to the formulas given in the reference manual (and oscilloscope measurements), &lt;STRONG&gt;both parameter sets&lt;/STRONG&gt; result in&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;a spread spectrum range of 15 MHz&lt;/LI&gt;&lt;LI&gt;a modulation frequency of 48 KHz&lt;/LI&gt;&lt;LI&gt;and a frequency change step of 60 KHz&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;But we have boards on which one parameter set works fine, while the other set doesn't work at all. So what can be the difference?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jan 2018 07:31:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743653#M115709</guid>
      <dc:creator>MOW</dc:creator>
      <dc:date>2018-01-23T07:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: Parameter constraints for i.MX6 spread-spectrum clocking?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743654#M115710</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please try to analyze issue observing mmdc signal on clko pin using CCM_CCOSR register.&lt;/P&gt;&lt;P&gt;Please also try with baremetal tests, to exclude opearting system side effects:&lt;/P&gt;&lt;P&gt;Github SDK&lt;BR /&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fgithub.com%2Fbackenklee%2Fswp-report%2Ftree%2Fmaster%2FiMX6_Platform_SDK" rel="nofollow" target="_blank"&gt;https://github.com/backenklee/swp-report/tree/master/iMX6_Platform_SDK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jan 2018 07:48:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Parameter-constraints-for-i-MX6-spread-spectrum-clocking/m-p/743654#M115710</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-01-23T07:48:03Z</dc:date>
    </item>
  </channel>
</rss>

