<?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 i.MX8MP ENET_RXC/A25 Pinmux Clarification for MII Interface in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8MP-ENET-RXC-A25-Pinmux-Clarification-for-MII-Interface/m-p/2416236#M246854</link>
    <description>&lt;P&gt;We are developing a custom board using the PHYTEC phyCORE-i.MX8M Plus SOM and are reviewing the Ethernet pinmux for migration from the existing RGMII interface to MII. The PHYTEC SOM pin A25 is associated with the i.MX8M Plus ENET_RXC signal. In the i.MX8MP pinmux, ENET_RXC supports ALT0 = CCM_ENET_QOS_CLOCK_GENERATE_RX_CLK and ALT1 = ENET_QOS_RX_ER. We need clarification regarding the correct pin assignment and interface requirements for the intended MII configuration. Specifically, is ENET_RXC required for the MII receive interface, or can the required RX_ER function be assigned to another suitable i.MX8M Plus pad/GPIO? If a different pad can be used, please provide the recommended pin mapping. We also need confirmation of whether the i.MX8M Plus ENET_QOS controller supports the intended MII interface and whether any IOMUX, MAC, device-tree, GPR, or PHY configuration changes are required. Please advise on the recommended Ethernet pin mapping and configuration for the i.MX8M Plus with the PHYTEC phyCORE SOM.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Sep 2026 07:38:03 GMT</pubDate>
    <dc:creator>TS-Rameshkumar-PHYTEC</dc:creator>
    <dc:date>2026-09-25T07:38:03Z</dc:date>
    <item>
      <title>i.MX8MP ENET_RXC/A25 Pinmux Clarification for MII Interface</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8MP-ENET-RXC-A25-Pinmux-Clarification-for-MII-Interface/m-p/2416236#M246854</link>
      <description>&lt;P&gt;We are developing a custom board using the PHYTEC phyCORE-i.MX8M Plus SOM and are reviewing the Ethernet pinmux for migration from the existing RGMII interface to MII. The PHYTEC SOM pin A25 is associated with the i.MX8M Plus ENET_RXC signal. In the i.MX8MP pinmux, ENET_RXC supports ALT0 = CCM_ENET_QOS_CLOCK_GENERATE_RX_CLK and ALT1 = ENET_QOS_RX_ER. We need clarification regarding the correct pin assignment and interface requirements for the intended MII configuration. Specifically, is ENET_RXC required for the MII receive interface, or can the required RX_ER function be assigned to another suitable i.MX8M Plus pad/GPIO? If a different pad can be used, please provide the recommended pin mapping. We also need confirmation of whether the i.MX8M Plus ENET_QOS controller supports the intended MII interface and whether any IOMUX, MAC, device-tree, GPR, or PHY configuration changes are required. Please advise on the recommended Ethernet pin mapping and configuration for the i.MX8M Plus with the PHYTEC phyCORE SOM.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2026 07:38:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8MP-ENET-RXC-A25-Pinmux-Clarification-for-MII-Interface/m-p/2416236#M246854</guid>
      <dc:creator>TS-Rameshkumar-PHYTEC</dc:creator>
      <dc:date>2026-09-25T07:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8MP ENET_RXC/A25 Pinmux Clarification for MII Interface</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8MP-ENET-RXC-A25-Pinmux-Clarification-for-MII-Interface/m-p/2416370#M246861</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thank you for your interest in NXP Semiconductor products,&lt;/P&gt;
&lt;P&gt;i.MX 8M Plus does not support MII, please refer to the following extract from RM:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;Seamless interface to commercial ethernet PHY devices via one of the following:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;a 2-bit Reduced MII (RMII) operating at 50 MHz.&lt;/LI&gt;
&lt;LI&gt;a (double data rate) 4-bit Reduced GMII (RGMII) operating at 125 MHz.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;For signal mapping, you can refer to i.MX 8M Plus DS.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="JosephAtNXP_0-1790353940796.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/396872iB1DA6353A348B5A9/image-size/large?v=v2&amp;amp;px=999" role="button" title="JosephAtNXP_0-1790353940796.png" alt="JosephAtNXP_0-1790353940796.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2026 16:32:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8MP-ENET-RXC-A25-Pinmux-Clarification-for-MII-Interface/m-p/2416370#M246861</guid>
      <dc:creator>JosephAtNXP</dc:creator>
      <dc:date>2026-09-25T16:32:31Z</dc:date>
    </item>
  </channel>
</rss>

