How to configure eth0 on fslc-image-network-full-cmdline


Leo
 

Hello,

I'm using a wandboard (rev d1) and building the fslc-image-network-full-cmdline image (honister branch). I've got ethernet wired to a switch on my home network, but I cannot figure out how to setup this build to bring up eth0 via DHCP. Any help would be appreciated. Is this image supposed to bring up eth0 right out of the box?

Build Configuration:
BB_VERSION           = "1.52.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-20.04"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "wandboard"
DISTRO               = "poky"
DISTRO_VERSION       = "3.4"
TUNE_FEATURES        = "arm vfp cortexa9 neon thumb callconvention-hard"
TARGET_FPU           = "hard"
meta                 
meta-poky            = "HEAD:da5d1b540e052c862232f8bd464d30bb387fe86e"
meta-oe              
meta-multimedia      
meta-python          
meta-networking      = "HEAD:ad52a41de8b4b7d619d1376d0a0090ebcfff56da"
meta-freescale       = "HEAD:ed3435620a2404c241fef3c4ef90d1f31d3b7a8a"
meta-freescale-3rdparty = "HEAD:fd3c4aa47c93b77942dfcf1ab8ded0c54cb589d5"
meta-freescale-distro = "HEAD:d2e27cc4778663450495a67bfb036cba600cb27a"


root@wandboard:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::21f:7bff:fe0a:90b8  prefixlen 64  scopeid 0x20<link>
        ether 00:1f:7b:0a:90:b8  txqueuelen 1000  (Ethernet)
        RX packets 14  bytes 1200 (1.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 32  bytes 6786 (6.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@wandboard:~# cat /etc/network/interfaces
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# Wireless interfaces
iface wlan0 inet dhcp
        wireless_mode managed
        wireless_essid any
        wpa-driver wext
        wpa-conf /etc/wpa_supplicant.conf

iface atml0 inet dhcp

# Wired or wireless interfaces
auto eth0
iface eth0 inet dhcp
iface eth1 inet dhcp

# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
iface usb0 inet static
        address 192.168.7.2
        netmask 255.255.255.0
        network 192.168.7.0
        gateway 192.168.7.1

# Bluetooth networking
iface bnep0 inet dhcp


Michał Kotyla
 

Hi,

On Wed, Nov 17, 2021 at 11:40 PM, Leo wrote:
Hello,

I'm using a wandboard (rev d1) and building the fslc-image-network-full-cmdline image (honister branch). I've got ethernet wired to a switch on my home network, but I cannot figure out how to setup this build to bring up eth0 via DHCP. Any help would be appreciated. Is this image supposed to bring up eth0 right out of the box?

Build Configuration:
BB_VERSION           = "1.52.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-20.04"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "wandboard"
DISTRO               = "poky"
DISTRO_VERSION       = "3.4"
TUNE_FEATURES        = "arm vfp cortexa9 neon thumb callconvention-hard"
TARGET_FPU           = "hard"
meta                 
meta-poky            = "HEAD:da5d1b540e052c862232f8bd464d30bb387fe86e"
meta-oe              
meta-multimedia      
meta-python          
meta-networking      = "HEAD:ad52a41de8b4b7d619d1376d0a0090ebcfff56da"
meta-freescale       = "HEAD:ed3435620a2404c241fef3c4ef90d1f31d3b7a8a"
meta-freescale-3rdparty = "HEAD:fd3c4aa47c93b77942dfcf1ab8ded0c54cb589d5"
meta-freescale-distro = "HEAD:d2e27cc4778663450495a67bfb036cba600cb27a"


root@wandboard:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::21f:7bff:fe0a:90b8  prefixlen 64  scopeid 0x20<link>
        ether 00:1f:7b:0a:90:b8  txqueuelen 1000  (Ethernet)
        RX packets 14  bytes 1200 (1.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 32  bytes 6786 (6.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@wandboard:~# cat /etc/network/interfaces
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# Wireless interfaces
iface wlan0 inet dhcp
        wireless_mode managed
        wireless_essid any
        wpa-driver wext
        wpa-conf /etc/wpa_supplicant.conf

iface atml0 inet dhcp

# Wired or wireless interfaces
auto eth0
iface eth0 inet dhcp
iface eth1 inet dhcp

# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
iface usb0 inet static
        address 192.168.7.2
        netmask 255.255.255.0
        network 192.168.7.0
        gateway 192.168.7.1

# Bluetooth networking
iface bnep0 inet dhcp

I have this issue after updating meta layers to honister and kernel to version 5.10. My problem was fixed by changing fec node in device tree - phy-mode value should be rgmii-id and phy-reset-duration should be increased:

phy-mode = "rgmii-id";
phy-reset-duration = <10>;

You can see at commit logs in imx devicetrees on kernel repository for more information.

Best regards,

-- 
Michał Kotyla
Embedded Linux Developer
GPG: 14FC54DC259CF70A
https://3mdeb.com | @3mdeb_com


Fabio Estevam
 

Hi Leo,

On Wed, Nov 17, 2021 at 7:40 PM Leo <Leo.E.Meza@gmail.com> wrote:

Hello,

I'm using a wandboard (rev d1) and building the fslc-image-network-full-cmdline image (honister branch). I've got ethernet wired to a switch on my home network, but I cannot figure out how to setup this build to bring up eth0 via DHCP. Any help would be appreciated. Is this image supposed to bring up eth0 right out of the box?
There is a recent fix in 5.15.13 for Ethernet on wandboard
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm/boot/dts/imx6qdl-wandboard.dtsi?h=v5.15.13&id=ef73e3b650b7b1ad4080b8e7aeba5e36e19f0932

After applying this fix, I can confirm Ethernet is functional.

To get an IP address via DHCP:
udhcpc -i eth0


Gary Huband
 

If your image uses systemd-networkd, then the interface configuration files are in /etc/systemd/network.  For eth0 using DNS you should have a file eth0.network:

[Match]
Name=eth0

[Network]
DHCP=ipv4


Gary


From: meta-freescale@... <meta-freescale@...> on behalf of Fabio Estevam via lists.yoctoproject.org <festevam=gmail.com@...>
Sent: Wednesday, January 5, 2022 8:18 AM
To: Leo <Leo.E.Meza@...>
Cc: meta-freescale@... <meta-freescale@...>
Subject: Re: [meta-freescale] How to configure eth0 on fslc-image-network-full-cmdline
 
Hi Leo,

On Wed, Nov 17, 2021 at 7:40 PM Leo <Leo.E.Meza@...> wrote:
>
> Hello,
>
> I'm using a wandboard (rev d1) and building the fslc-image-network-full-cmdline image (honister branch). I've got ethernet wired to a switch on my home network, but I cannot figure out how to setup this build to bring up eth0 via DHCP. Any help would be appreciated. Is this image supposed to bring up eth0 right out of the box?

There is a recent fix in 5.15.13 for Ethernet on wandboard
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fstable%2Flinux.git%2Fcommit%2Farch%2Farm%2Fboot%2Fdts%2Fimx6qdl-wandboard.dtsi%3Fh%3Dv5.15.13%26id%3Def73e3b650b7b1ad4080b8e7aeba5e36e19f0932&amp;data=04%7C01%7Cgary%40missionsecure.com%7C1397663187e94db62ab508d9d04deb6b%7Cf0ca9611f13f4dc98e1b119172b8ec5d%7C0%7C1%7C637769855347295604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=VNgLH7NoC8HmHQw3B0zk4Afv%2F3u2UAyLVpjskmbS8iQ%3D&amp;reserved=0

After applying this fix, I can confirm Ethernet is functional.

To get an IP address via DHCP:
udhcpc -i eth0

Gary Huband
Sr. Software and Systems Engineer

Office: 434.284.8071 x720
Direct: 434.260.4995
Gary@...

Follow Us!
LinkedIn  |  Blog  |  Website

: : : : : : : : : : : : : : : : : : : : : : : : : : :

MSi

This email and any files transmitted with it are confidential and proprietary and intended solely for the use of the individual or entity to whom they are addressed. Any dissemination, distribution or copying of this communication is strictly prohibited without our prior permission. If you received this in error, please contact the sender and delete the material from any computer.


Andrey Zhizhikin
 

Hello Leo and Fabio,

On Wed, Jan 5, 2022 at 2:18 PM Fabio Estevam <festevam@gmail.com> wrote:

Hi Leo,

On Wed, Nov 17, 2021 at 7:40 PM Leo <Leo.E.Meza@gmail.com> wrote:

Hello,

I'm using a wandboard (rev d1) and building the fslc-image-network-full-cmdline image (honister branch). I've got ethernet wired to a switch on my home network, but I cannot figure out how to setup this build to bring up eth0 via DHCP. Any help would be appreciated. Is this image supposed to bring up eth0 right out of the box?
There is a recent fix in 5.15.13 for Ethernet on wandboard
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm/boot/dts/imx6qdl-wandboard.dtsi?h=v5.15.13&id=ef73e3b650b7b1ad4080b8e7aeba5e36e19f0932
There is a PR in meta-freescale layer against [master] branch, which
upgrades the Kernel to 5.15.13:
https://github.com/Freescale/meta-freescale/pull/936

Once merged, you can build the image of [master] to verify if your
problem persists.


After applying this fix, I can confirm Ethernet is functional.

To get an IP address via DHCP:
udhcpc -i eth0



--
Regards,
Andrey.


Otavio Salvador
 



Em sex., 7 de jan. de 2022 às 06:54, Andrey Zhizhikin <andrey.z@...> escreveu:
On Wed, Jan 5, 2022 at 2:18 PM Fabio Estevam <festevam@...> wrote:
> On Wed, Nov 17, 2021 at 7:40 PM Leo <Leo.E.Meza@...> wrote:

> There is a recent fix in 5.15.13 for Ethernet on wandboard
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/arch/arm/boot/dts/imx6qdl-wandboard.dtsi?h=v5.15.13&id=ef73e3b650b7b1ad4080b8e7aeba5e36e19f0932

There is a PR in meta-freescale layer against [master] branch, which
upgrades the Kernel to 5.15.13:
https://github.com/Freescale/meta-freescale/pull/936

Once merged, you can build the image of [master] to verify if your
problem persists.

This has been merged :-)

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750