<?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 Ethernet clock issue in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2281727#M35970</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have a custom board with &lt;STRONG&gt;imxrt1176&lt;/STRONG&gt; controller that is interfaced to 1G &lt;STRONG&gt;ethernet phy(DP83869)&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Changed the &lt;STRONG&gt;configuration registers&lt;/STRONG&gt; then it is working good and checked for &lt;STRONG&gt;10mbps it is working&lt;/STRONG&gt; fine but when we change the ethernet to&lt;STRONG&gt; 100mbps&lt;/STRONG&gt; connection then it is &lt;STRONG&gt;not able to ping. &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Then probed on all signals and identified that imxrt1176 is &lt;STRONG&gt;not generating 25mhz&lt;/STRONG&gt; clock on &lt;STRONG&gt;Eth_tx_clk&lt;/STRONG&gt; and it is &lt;STRONG&gt;continuous 2.5MHZ&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;After searching a relevant document is found in that mentioned that we need to change clock to 125Mhz as shown in below figure:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bhardwaj_0-1767678805467.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371795i29CB22A7A48B5DAF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Bhardwaj_0-1767678805467.png" alt="Bhardwaj_0-1767678805467.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;As per the above screenshot modified clock in clock tool as shown in below figure:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bhardwaj_1-1767678861249.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371796i1BB3D5002050256E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Bhardwaj_1-1767678861249.png" alt="Bhardwaj_1-1767678861249.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Jan 2026 06:03:26 GMT</pubDate>
    <dc:creator>Bhardwaj</dc:creator>
    <dc:date>2026-01-06T06:03:26Z</dc:date>
    <item>
      <title>Ethernet clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2281727#M35970</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have a custom board with &lt;STRONG&gt;imxrt1176&lt;/STRONG&gt; controller that is interfaced to 1G &lt;STRONG&gt;ethernet phy(DP83869)&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Changed the &lt;STRONG&gt;configuration registers&lt;/STRONG&gt; then it is working good and checked for &lt;STRONG&gt;10mbps it is working&lt;/STRONG&gt; fine but when we change the ethernet to&lt;STRONG&gt; 100mbps&lt;/STRONG&gt; connection then it is &lt;STRONG&gt;not able to ping. &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Then probed on all signals and identified that imxrt1176 is &lt;STRONG&gt;not generating 25mhz&lt;/STRONG&gt; clock on &lt;STRONG&gt;Eth_tx_clk&lt;/STRONG&gt; and it is &lt;STRONG&gt;continuous 2.5MHZ&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;After searching a relevant document is found in that mentioned that we need to change clock to 125Mhz as shown in below figure:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bhardwaj_0-1767678805467.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371795i29CB22A7A48B5DAF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Bhardwaj_0-1767678805467.png" alt="Bhardwaj_0-1767678805467.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;As per the above screenshot modified clock in clock tool as shown in below figure:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bhardwaj_1-1767678861249.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/371796i1BB3D5002050256E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Bhardwaj_1-1767678861249.png" alt="Bhardwaj_1-1767678861249.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 06:03:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2281727#M35970</guid>
      <dc:creator>Bhardwaj</dc:creator>
      <dc:date>2026-01-06T06:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2281912#M35971</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/254971"&gt;@Bhardwaj&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks for your interest in NXP MIMXRT series!&lt;/P&gt;
&lt;P&gt;Have you successfully resolved this clock issue by following the instructions in AN14215?&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Gavin&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 07:49:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2281912#M35971</guid>
      <dc:creator>Gavin_Jia</dc:creator>
      <dc:date>2026-01-06T07:49:35Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2283725#M35972</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/203261"&gt;@Gavin_Jia&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;No, the issue is not solved. Another observation also found that when we change the speed to 1Gbps then the clock is changing to 25Mhz.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 08:21:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2283725#M35972</guid>
      <dc:creator>Bhardwaj</dc:creator>
      <dc:date>2026-01-06T08:21:35Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2289784#M35986</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/254971"&gt;@Bhardwaj&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks for the information.&lt;/P&gt;
&lt;P&gt;I noticed you submitted the same ticket in SFDC. As we discussed, I suspect the clock you're monitoring originates from the PHY rather than the MAC. Please try the relevant GPR5 configuration and testing. Thanks in advance!&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Gavin&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jan 2026 02:25:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2289784#M35986</guid>
      <dc:creator>Gavin_Jia</dc:creator>
      <dc:date>2026-01-08T02:25:45Z</dc:date>
    </item>
    <item>
      <title>Re: Ethernet clock issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2297840#M36060</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/203261"&gt;@Gavin_Jia&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I had checked that but there are two GPR5 in clock_config.c&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;At line 875&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;/* Set ENET_1G &lt;/SPAN&gt;&lt;SPAN&gt;Tx&lt;/SPAN&gt;&lt;SPAN&gt; clock source. */&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;IOMUXC_GPR-&amp;gt;&lt;/SPAN&gt;&lt;SPAN&gt;GPR5&lt;/SPAN&gt;&lt;SPAN&gt; = ((IOMUXC_GPR-&amp;gt;&lt;/SPAN&gt;&lt;SPAN&gt;GPR5&lt;/SPAN&gt;&lt;SPAN&gt; &amp;amp; ~IOMUXC_GPR_GPR5_ENET1G_TX_CLK_SEL_MASK) | IOMUXC_GPR_GPR5_ENET1G_RGMII_EN_MASK);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;/* Set ENET_1G &lt;/SPAN&gt;&lt;SPAN&gt;Ref&lt;/SPAN&gt;&lt;SPAN&gt; clock source. */&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;IOMUXC_GPR-&amp;gt;&lt;/SPAN&gt;&lt;SPAN&gt;GPR5&lt;/SPAN&gt;&lt;SPAN&gt; |= IOMUXC_GPR_GPR5_ENET1G_REF_CLK_DIR_MASK;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At line 1697&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;/* Set ENET_1G &lt;/SPAN&gt;&lt;SPAN&gt;Tx&lt;/SPAN&gt;&lt;SPAN&gt; clock source. */&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;IOMUXC_GPR-&amp;gt;&lt;/SPAN&gt;&lt;SPAN&gt;GPR5&lt;/SPAN&gt;&lt;SPAN&gt; = ((IOMUXC_GPR-&amp;gt;&lt;/SPAN&gt;&lt;SPAN&gt;GPR5&lt;/SPAN&gt;&lt;SPAN&gt; &amp;amp; ~&lt;/SPAN&gt;&lt;SPAN&gt;IOMUXC_GPR_GPR5_ENET1G_TX_CLK_SEL_MASK&lt;/SPAN&gt;&lt;SPAN&gt;) | IOMUXC_GPR_GPR5_ENET1G_RGMII_EN_MASK);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;/* Set ENET_1G &lt;/SPAN&gt;&lt;SPAN&gt;Ref&lt;/SPAN&gt;&lt;SPAN&gt; clock source. */&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;IOMUXC_GPR-&amp;gt;&lt;/SPAN&gt;&lt;SPAN&gt;GPR5&lt;/SPAN&gt;&lt;SPAN&gt; &amp;amp;= ~IOMUXC_GPR_GPR5_ENET1G_REF_CLK_DIR_MASK;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Tried by removing line 1697-1700 still no change.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Modified the phy related functions. Attaching modified fsl_phyrtl8211f.c file please check.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;why am unable to get 25Mhz on Tx_clk pin when rx_clk is 25mhz in 100mbps but when changed to 1gbps then tx_clk is getting 25mhz? ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 22 Jan 2026 05:18:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Ethernet-clock-issue/m-p/2297840#M36060</guid>
      <dc:creator>Bhardwaj</dc:creator>
      <dc:date>2026-01-22T05:18:48Z</dc:date>
    </item>
  </channel>
</rss>

