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

[email protected] Wed, 05 Jan 2022 04:58:37 -0800
Newsgroups org.yoctoproject.lists.meta-freescale
Message-ID <[email protected]>
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