<?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: imx8mp single ethernet using eqos in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1917865#M226628</link>
    <description>&lt;P&gt;&lt;SPAN&gt;s_arendt-san,&lt;BR /&gt;Thank you tell me about reason from no uses case.&lt;BR /&gt;I think, that error also come from fec disabled.&lt;BR /&gt;So we must need fec set status = "okay"; even if we don't use fec.&lt;BR /&gt;But I need care of&amp;nbsp; pinctrl because our custom board these fec port are non connection.&lt;BR /&gt;If these port active to fec port, it may occur some trouble by input pins.&lt;BR /&gt;So I decide to set bellow simple settings without pinctrl-0.&lt;BR /&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;// Dummy settings for activate eqos
&amp;amp;fec {
	pinctrl-names = "default";
	phy-mode = "rgmii-id";
	status = "okay";
};&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;this case, u-boot ping said that bellow. (Could not get PHY for FEC1: addr 1)&lt;BR /&gt;&lt;BR /&gt;u-boot=&amp;gt; ping 192.168.xx.xx&lt;BR /&gt;Could not get PHY for FEC1: addr 1&lt;BR /&gt;ethernet@30bf0000 Waiting for PHY auto negotiation to complete....... done&lt;BR /&gt;Using ethernet@30bf0000 device&lt;BR /&gt;host 192.168.xx.xx is alive&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jul 2024 06:55:18 GMT</pubDate>
    <dc:creator>satokimiyasu</dc:creator>
    <dc:date>2024-07-26T06:55:18Z</dc:date>
    <item>
      <title>imx8mp single ethernet using eqos</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1917665#M226616</link>
      <description>&lt;P&gt;We cannot use eqos ethernet at singe ethernet.&lt;BR /&gt;Our board is custom board base on imx8mp-evk.&lt;BR /&gt;Custom board&amp;nbsp; different from&amp;nbsp;imx8mp-evk on eqos single ethernet.&lt;BR /&gt;My understanding is if we don't need to use fec, we just set status = "disabled"; in&amp;nbsp;&amp;nbsp;imx8mp-evk.dts.&lt;BR /&gt;&lt;BR /&gt;The problem is if when I set fec disabled only use eqos port, Igot error "EQOS_DMA_MODE_SWR stuckFAILED: -110".&lt;BR /&gt;But fec status = "okay"; case was fine even if our board don't have fec phy chip.&lt;BR /&gt;&lt;BR /&gt;please let me know about that reason.&lt;BR /&gt;I'm something wrong?&lt;/P&gt;&lt;LI-CODE lang="c"&gt;&amp;amp;fec {
        pinctrl-names = "default";
        pinctrl-0 = &amp;lt;&amp;amp;pinctrl_fec&amp;gt;;
        phy-mode = "rgmii-id";
        phy-handle = &amp;lt;&amp;amp;ethphy1&amp;gt;;
        fsl,magic-packet;
//      status = "okay";
        status = "disabled";    //Not use

        mdio {
                #address-cells = &amp;lt;1&amp;gt;;
                #size-cells = &amp;lt;0&amp;gt;;

                ethphy1: ethernet-phy@1 {
                        compatible = "ethernet-phy-ieee802.3-c22";
                        reg = &amp;lt;1&amp;gt;;
                        eee-broken-1000t;
                };
        };
};&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;uboot log&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;U-Boot 2022.04-dirty (Jul 26 2024 - 10:20:19 +0900)&lt;/P&gt;&lt;P&gt;CPU: i.MX8MP[6] rev1.1 1800 MHz (running at 1200 MHz)&lt;BR /&gt;CPU: Commercial temperature grade (0C to 95C) at 45C&lt;BR /&gt;Reset cause: POR&lt;BR /&gt;Model: NXP i.MX 8M Plus Based Custom Board&lt;BR /&gt;DRAM: 4 GiB&lt;BR /&gt;Core: 81 devices, 24 uclasses, devicetree: separate&lt;BR /&gt;MMC: FSL_SDHC: 0&lt;BR /&gt;Loading Environment from nowhere... OK&lt;BR /&gt;[*]-Video Link 0fail to find output device&lt;BR /&gt;probe video device failed, ret -19&lt;/P&gt;&lt;P&gt;[0] lcd-controller@32e80000, video&lt;BR /&gt;fail to find output device&lt;BR /&gt;probe video device failed, ret -19&lt;BR /&gt;In: serial&lt;BR /&gt;Out: serial&lt;BR /&gt;Err: serial&lt;BR /&gt;SEC0: RNG instantiated&lt;/P&gt;&lt;P&gt;BuildInfo:&lt;BR /&gt;- ATF 8dbe286&lt;/P&gt;&lt;P&gt;MMC Device 1 not found&lt;BR /&gt;no mmc device at slot 1&lt;BR /&gt;Detect USB boot. Will enter fastboot mode!&lt;BR /&gt;Net:&lt;BR /&gt;Warning: ethernet@30bf0000 (eth1) using random MAC address - 0a:ad:b2:b1:75:bd&lt;BR /&gt;eth1: ethernet@30bf0000 [PRIME]&lt;BR /&gt;Fastboot: Normal&lt;BR /&gt;Boot from USB for mfgtools&lt;BR /&gt;*** Warning - Use default environment for mfgtools&lt;BR /&gt;, using default environment&lt;/P&gt;&lt;P&gt;Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; fi;&lt;BR /&gt;Hit any key to stop autoboot: 0&lt;/P&gt;&lt;P&gt;## Checking Image at 43800000 ...&lt;BR /&gt;Unknown image format!&lt;BR /&gt;Run fastboot ...&lt;BR /&gt;u-boot=&amp;gt; env set ipaddr 192.168.xx.xx&lt;BR /&gt;u-boot=&amp;gt; env set netmask 255.255.0.0&lt;BR /&gt;u-boot=&amp;gt; ping 192.168.xx.xx&lt;BR /&gt;EQOS_DMA_MODE_SWR stuckFAILED: -110&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 01:50:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1917665#M226616</guid>
      <dc:creator>satokimiyasu</dc:creator>
      <dc:date>2024-07-26T01:50:52Z</dc:date>
    </item>
    <item>
      <title>Re: imx8mp single ethernet using eqos</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1917798#M226624</link>
      <description>&lt;P&gt;There are several issues with Uboot and EQOS in older versions. I guess it was simply no uses case for devs to make it working as single ethernet. Best is you checkout a newer Uboot version. Things get better there. You can also address uboot mailing list.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 05:30:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1917798#M226624</guid>
      <dc:creator>s_arendt</dc:creator>
      <dc:date>2024-07-26T05:30:03Z</dc:date>
    </item>
    <item>
      <title>Re: imx8mp single ethernet using eqos</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1917865#M226628</link>
      <description>&lt;P&gt;&lt;SPAN&gt;s_arendt-san,&lt;BR /&gt;Thank you tell me about reason from no uses case.&lt;BR /&gt;I think, that error also come from fec disabled.&lt;BR /&gt;So we must need fec set status = "okay"; even if we don't use fec.&lt;BR /&gt;But I need care of&amp;nbsp; pinctrl because our custom board these fec port are non connection.&lt;BR /&gt;If these port active to fec port, it may occur some trouble by input pins.&lt;BR /&gt;So I decide to set bellow simple settings without pinctrl-0.&lt;BR /&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;// Dummy settings for activate eqos
&amp;amp;fec {
	pinctrl-names = "default";
	phy-mode = "rgmii-id";
	status = "okay";
};&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;this case, u-boot ping said that bellow. (Could not get PHY for FEC1: addr 1)&lt;BR /&gt;&lt;BR /&gt;u-boot=&amp;gt; ping 192.168.xx.xx&lt;BR /&gt;Could not get PHY for FEC1: addr 1&lt;BR /&gt;ethernet@30bf0000 Waiting for PHY auto negotiation to complete....... done&lt;BR /&gt;Using ethernet@30bf0000 device&lt;BR /&gt;host 192.168.xx.xx is alive&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 06:55:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1917865#M226628</guid>
      <dc:creator>satokimiyasu</dc:creator>
      <dc:date>2024-07-26T06:55:18Z</dc:date>
    </item>
    <item>
      <title>Re: imx8mp single ethernet using eqos</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1918124#M226643</link>
      <description>&lt;P&gt;Pretty sure there is no need to enable that FEC interface. But for that you need to change the board files - at least in this old 2204 version. You can read that init of this is coupled there, for no real reason. Which uboot version (mainline, nxp, version) are you using? Better go for a newer one, there are a lot of changes for the qos driver... But if this trick solves your problem, that is ok too.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 12:28:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1918124#M226643</guid>
      <dc:creator>s_arendt</dc:creator>
      <dc:date>2024-07-26T12:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: imx8mp single ethernet using eqos</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1918866#M226677</link>
      <description>&lt;P&gt;I used u-boot branch&amp;nbsp;lf_v2022.04(default).&lt;BR /&gt;I will try to use&amp;nbsp;lf_v2024.04.&lt;BR /&gt;lf_v2024.04 dts file is so different from&amp;nbsp;lf_v2022.04 dts file.&lt;BR /&gt;I will report later when I try to set fec "status = disabled" later.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 00:48:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1918866#M226677</guid>
      <dc:creator>satokimiyasu</dc:creator>
      <dc:date>2024-07-29T00:48:47Z</dc:date>
    </item>
    <item>
      <title>Re: imx8mp single ethernet using eqos</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1919960#M226728</link>
      <description>&lt;P&gt;&lt;SPAN&gt;lf_v2024.04 u-boot case, it is not so different from&amp;nbsp;&amp;nbsp;lf_v2022.04 results about fec status setting.&lt;BR /&gt;It still need set fes status="okay".&lt;BR /&gt;Thank you for your advice.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2024 04:17:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1919960#M226728</guid>
      <dc:creator>satokimiyasu</dc:creator>
      <dc:date>2024-07-30T04:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: imx8mp single ethernet using eqos</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1920106#M226735</link>
      <description>Yes, dts handling is changed. With lf_ seems you are using NXP uboot. I am in mainline. Anyway my config doesn't have set CONFIG_FEC_MXC=y and it is not enabled in dts. But well, you find a solution, that's ok! Best regards and good luck further.</description>
      <pubDate>Tue, 30 Jul 2024 06:46:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8mp-single-ethernet-using-eqos/m-p/1920106#M226735</guid>
      <dc:creator>s_arendt</dc:creator>
      <dc:date>2024-07-30T06:46:03Z</dc:date>
    </item>
  </channel>
</rss>

