<?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>MPC5xxx中的主题 Re: MPC5604E Clock Architecture Issues</title>
    <link>https://community.nxp.com/t5/MPC5xxx/MPC5604E-Clock-Architecture-Issues/m-p/657912#M7130</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have confirmed the same behavior on my board. Yes, the input for clk_out is before the divider. Thanks for pointing this out, I will report it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, it is possible that the clk out can be set to higher frequencies but we do not guarantee the functionality of the device in this case. It's out of our specification.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lukas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Nov 2016 14:06:08 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2016-11-15T14:06:08Z</dc:date>
    <item>
      <title>MPC5604E Clock Architecture Issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC5604E-Clock-Architecture-Issues/m-p/657911#M7129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm working on MPC5604E, and wanted to get clock out of "clk_out" pin [PCR36, Pin No. 62], according to Clock Architecture Block diagram [Refer "Img1"], Input to the "clk_out" pad is from FMPLL_0 after FMPLL_CLK_DIV, But according to over experimentation its not the case, according to what I have validated the input to "clk_out" is from FMPLL_0 before FMPLL_CLK_DIV. It also says maximum frequency supported on "clk_out" pad is 32MHz [Refer Img2]&lt;/P&gt;&lt;P&gt;but we have tested it upto 120MHz. Do clarify the issues.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/122501iCF51E1752F0A315A/image-size/large?v=v2&amp;amp;px=999" title="169441_169441.png" alt="169441_169441.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/8755iC3A576A45A93876A/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/122502iA0E13FBB19AE8161/image-size/large?v=v2&amp;amp;px=999" title="169445_169445.png" alt="169445_169445.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/8878i1018F5867937C014/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&amp;nbsp;&lt;/P&gt;&lt;P&gt;SUHAS S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Nov 2016 15:10:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC5604E-Clock-Architecture-Issues/m-p/657911#M7129</guid>
      <dc:creator>suhass</dc:creator>
      <dc:date>2016-11-14T15:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: MPC5604E Clock Architecture Issues</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC5604E-Clock-Architecture-Issues/m-p/657912#M7130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have confirmed the same behavior on my board. Yes, the input for clk_out is before the divider. Thanks for pointing this out, I will report it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, it is possible that the clk out can be set to higher frequencies but we do not guarantee the functionality of the device in this case. It's out of our specification.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lukas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2016 14:06:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC5604E-Clock-Architecture-Issues/m-p/657912#M7130</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2016-11-15T14:06:08Z</dc:date>
    </item>
  </channel>
</rss>

