<?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: Unstable Gigabit Ethernet on i.MX 8M Mini in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/2006093#M231490</link>
    <description>&lt;P&gt;I used to think it was caused by energy-saving mode, but in DTS, it was declared to disable all EEE modes, but the problem still exists. The phy I am using is RTL8211E-VB-CG&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Only__0-1733230186134.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/313782iB5103045A3DE7321/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Only__0-1733230186134.png" alt="Only__0-1733230186134.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 03 Dec 2024 12:49:55 GMT</pubDate>
    <dc:creator>Only_聆听</dc:creator>
    <dc:date>2024-12-03T12:49:55Z</dc:date>
    <item>
      <title>Unstable Gigabit Ethernet on i.MX 8M Mini</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/1986998#M230437</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We have a custom designed board based on i.MX 8M Mini running Android 9.0 and we're experiencing an issue with gigabit ethernet. The connection will randomly drop out and self recover again randomly later. We tried to ping the router or other devices on the same LAN and got the same issue. Ping would fail randomly for several seconds or sometimes several minutes.&lt;/P&gt;&lt;P&gt;We checked the kernel log and found many 'Link is Down' message followed by many 'Link is Up' message when the connection is lost. We suspect it might an issue with our kernel dts config or the FEC driver but we couldn't spot any obvious errors.&lt;/P&gt;&lt;P&gt;The ethernet phy chip used is&amp;nbsp;RTL8211E-VB-CG and it is used on some of our other rockchip boards as well and those do not have such problem.&lt;/P&gt;&lt;P&gt;One thing we did notice is that in the rockchip kernel dts, there are two properties 'tx_delay' and 'rx_delay' that can be modified to adjust the timings. We did not find similar values to change on the i.MX platform. The RTL8211E chip has two hardware pins that set the RX/TX delay as specified in the datasheet.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="delay.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/308383iF9630ECF16E2967F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="delay.png" alt="delay.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;We tested both configurations. 'no delay' doesn't work at all and '2ns delay' produces the issue described here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help or information will be appreciated.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yuping&lt;/P&gt;</description>
      <pubDate>Mon, 04 Nov 2024 11:20:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/1986998#M230437</guid>
      <dc:creator>yuping1</dc:creator>
      <dc:date>2024-11-04T11:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: Unstable Gigabit Ethernet on i.MX 8M Mini</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/1987001#M230438</link>
      <description>&lt;P&gt;Here are the dts for i.MX board:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;amp;fec1 {
	pinctrl-names = "default";
	pinctrl-0 = &amp;lt;&amp;amp;pinctrl_fec1&amp;gt;;
	phy-mode = "rgmii-id";
	phy-handle = &amp;lt;&amp;amp;ethphy0&amp;gt;;
	fsl,magic-packet;
	status = "okay";

	mdio {
		#address-cells = &amp;lt;1&amp;gt;;
		#size-cells = &amp;lt;0&amp;gt;;

		ethphy0: ethernet-phy@0 {
			compatible = "ethernet-phy-ieee802.3-c22";
			reg = &amp;lt;0&amp;gt;;
			at803x,led-act-blind-workaround;
			at803x,eee-okay;
			at803x,vddio-1p8v;
		};
	};
};&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below is the dts for rockchip board:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;amp;gmac1 {
	phy-mode = "rgmii";
	clock_in_out = "output";

	snps,reset-gpio = &amp;lt;&amp;amp;gpio4 RK_PC2 GPIO_ACTIVE_LOW&amp;gt;;
	snps,reset-active-low;
	snps,reset-delays-us = &amp;lt;0 50000 50000&amp;gt;;

	assigned-clocks = &amp;lt;&amp;amp;cru SCLK_GMAC1_RX_TX&amp;gt;, &amp;lt;&amp;amp;cru SCLK_GMAC1&amp;gt;;
	assigned-clock-parents = &amp;lt;&amp;amp;cru SCLK_GMAC1_RGMII_SPEED&amp;gt;, &amp;lt;&amp;amp;cru CLK_MAC1_2TOP&amp;gt;;
	assigned-clock-rates = &amp;lt;0&amp;gt;, &amp;lt;125000000&amp;gt;;

	pinctrl-names = "default";
	pinctrl-0 = &amp;lt;&amp;amp;gmac1m1_miim
		     &amp;amp;gmac1m1_tx_bus2
		     &amp;amp;gmac1m1_rx_bus2
		     &amp;amp;gmac1m1_rgmii_clk
		     &amp;amp;gmac1m1_rgmii_bus&amp;gt;;

	tx_delay = &amp;lt;0x24&amp;gt;;
	rx_delay = &amp;lt;0x08&amp;gt;;

	phy-handle = &amp;lt;&amp;amp;rgmii_phy1&amp;gt;;
	status = "okay";
};
&amp;amp;mdio1 {
	rgmii_phy1: phy@7 {
		compatible = "ethernet-phy-ieee802.3-c22";
		reg = &amp;lt;0x7&amp;gt;;
	};
};&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Nov 2024 11:26:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/1987001#M230438</guid>
      <dc:creator>yuping1</dc:creator>
      <dc:date>2024-11-04T11:26:59Z</dc:date>
    </item>
    <item>
      <title>Re: Unstable Gigabit Ethernet on i.MX 8M Mini</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/1987095#M230448</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You dtb looks ok, I guess your issue if due to RTL8211E, So please check your HW setting Vs PHY datasheet (PHY address, clock delay, SELRGV, etc..) and schematics.&lt;/P&gt;
&lt;P&gt;If you received 0 bytes, looks like your receive path is broken. Please check the pin definition/muxing in DT, receive clock settings in the PHY and the RCC, as well as connection/timings configurations at PHY level.&lt;/P&gt;
&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Mon, 04 Nov 2024 14:14:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/1987095#M230448</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2024-11-04T14:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: Unstable Gigabit Ethernet on i.MX 8M Mini</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/2006087#M231489</link>
      <description>&lt;P&gt;Hello, I have encountered the same problem as him. The log shows that the network has been switching between 10M, 100M, and 1000M.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[19:40:02.502]收←◆[ 227.550570] fec 30be0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx&lt;/P&gt;&lt;P&gt;[19:40:18.885]收←◆[ 243.934572] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx&lt;/P&gt;&lt;P&gt;[19:40:20.021]收←◆[ 245.070298] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a&lt;/P&gt;&lt;P&gt;[19:40:20.118]收←◆[ 245.167955] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a&lt;/P&gt;&lt;P&gt;[19:40:32.196]收←◆[ 257.246587] fec 30be0000.ethernet eth0: Link is Up - 10Mbps/Half - flow control off&lt;/P&gt;&lt;P&gt;[19:40:43.460]收←◆[ 268.511081] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx&lt;/P&gt;&lt;P&gt;[19:41:20.017]收←◆[ 305.070247] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a&lt;/P&gt;&lt;P&gt;[19:41:20.115]收←◆[ 305.167936] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a&lt;/P&gt;&lt;P&gt;[19:42:11.517]收←◆[ 356.574683] fec 30be0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx&lt;/P&gt;&lt;P&gt;[19:42:20.013]收←◆[ 365.070404] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a&lt;/P&gt;&lt;P&gt;[19:42:20.110]收←◆[ 365.167999] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a&lt;/P&gt;&lt;P&gt;[19:42:43.260]收←◆[ 388.319071] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx&lt;/P&gt;&lt;P&gt;[19:43:01.691]收←◆[ 406.751070] fec 30be0000.ethernet eth0: Link is Up - 10Mbps/Half - flow control off&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 12:43:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/2006087#M231489</guid>
      <dc:creator>Only_聆听</dc:creator>
      <dc:date>2024-12-03T12:43:27Z</dc:date>
    </item>
    <item>
      <title>Re: Unstable Gigabit Ethernet on i.MX 8M Mini</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/2006093#M231490</link>
      <description>&lt;P&gt;I used to think it was caused by energy-saving mode, but in DTS, it was declared to disable all EEE modes, but the problem still exists. The phy I am using is RTL8211E-VB-CG&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Only__0-1733230186134.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/313782iB5103045A3DE7321/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Only__0-1733230186134.png" alt="Only__0-1733230186134.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 12:49:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unstable-Gigabit-Ethernet-on-i-MX-8M-Mini/m-p/2006093#M231490</guid>
      <dc:creator>Only_聆听</dc:creator>
      <dc:date>2024-12-03T12:49:55Z</dc:date>
    </item>
  </channel>
</rss>

