<?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: i.MX RT1050 RMII Reference Clock in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888566#M2629</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Well, here I know it is really confused. Please be note that both ENET_REF_CLK and ENET_TX_CLK are inputs to the pins you route them to by default. This had been clearly indicated in the Reference manual.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/75771i4A7B30352474131D/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/75857i259343FD279A1E0D/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While, it is yes that for IMXRT1050-EVKB, ENET_TX_CLK&amp;nbsp; is used to clock the PHY. This had been done by software.&lt;/P&gt;&lt;P&gt;By configure ENET PLL(Set ENET1_CLK_SEL to 0 to have the ENET1 TX clock driven by the internal ref_enetpll) and set ENET1_TX_CLK_DIR&amp;nbsp; to 1 to enable ENET1_TX_CLK output driver that will redirect the generated clock to the PHY.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Jan 2019 10:35:17 GMT</pubDate>
    <dc:creator>miduo</dc:creator>
    <dc:date>2019-01-23T10:35:17Z</dc:date>
    <item>
      <title>i.MX RT1050 RMII Reference Clock</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888565#M2628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;According&amp;nbsp; to the i.MX RT1050 Processor Reference Manual, Rev. 2, the signal ENET_REF_CLK (on pad GPIO_B1_10) is an input in RMII mode. See Table 40-2. ENET External Signals.&lt;/P&gt;&lt;P&gt;Looking at the IMXRT1050-EVKB schematics, however, this signal seems to be an output from the processor, signal name ENET_TX_CLK, which is used to clock the PHY.&lt;/P&gt;&lt;P&gt;Can anybody please explain this apparent difference in documented signal direction.&lt;/P&gt;&lt;P&gt;Thanks for your help,&lt;/P&gt;&lt;P&gt;Pete Baston.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2019 13:27:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888565#M2628</guid>
      <dc:creator>pb1</dc:creator>
      <dc:date>2019-01-21T13:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX RT1050 RMII Reference Clock</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888566#M2629</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Well, here I know it is really confused. Please be note that both ENET_REF_CLK and ENET_TX_CLK are inputs to the pins you route them to by default. This had been clearly indicated in the Reference manual.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/75771i4A7B30352474131D/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/75857i259343FD279A1E0D/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While, it is yes that for IMXRT1050-EVKB, ENET_TX_CLK&amp;nbsp; is used to clock the PHY. This had been done by software.&lt;/P&gt;&lt;P&gt;By configure ENET PLL(Set ENET1_CLK_SEL to 0 to have the ENET1 TX clock driven by the internal ref_enetpll) and set ENET1_TX_CLK_DIR&amp;nbsp; to 1 to enable ENET1_TX_CLK output driver that will redirect the generated clock to the PHY.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2019 10:35:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888566#M2629</guid>
      <dc:creator>miduo</dc:creator>
      <dc:date>2019-01-23T10:35:17Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX RT1050 RMII Reference Clock</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888567#M2630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Fang,&lt;/P&gt;&lt;P&gt;Thanks for your reply. So, by configuring&amp;nbsp; these bits in software we have the choice of two modes, with the 50MHz reference clock being either an input or an output ?&lt;/P&gt;&lt;P&gt;Why was the 50MHz clock output mode chosen for the EVKB design ? Is this simply to avoid having a crystal on the PHY ?&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Pete.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2019 11:04:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888567#M2630</guid>
      <dc:creator>pb1</dc:creator>
      <dc:date>2019-01-23T11:04:28Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX RT1050 RMII Reference Clock</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888568#M2631</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, your understanding is correct.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2019 06:58:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/i-MX-RT1050-RMII-Reference-Clock/m-p/888568#M2631</guid>
      <dc:creator>miduo</dc:creator>
      <dc:date>2019-01-24T06:58:51Z</dc:date>
    </item>
  </channel>
</rss>

