Failed to Start Network Configuration on iMX8MP

[amosercq]

Hello,

I am having issues connecting my iMX8MP-EVK to the network when using a Yocto build. In particular, when booting the board the console output prints several FAILED operations (most of them are repeated and I only included one for each below):

Starting Network Name Resolution...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
 Starting Network Configuration...
[FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
See 'systemctl status avahi-daemon.service' for details.
[ OK ] Started Telephony service.
[FAILED] Failed to start Network Configuration.
See 'systemctl status systemd-networkd.service' for details.
[DEPEND] Dependency failed for Wait for Network to be Configured.

I originally blamed it on the fact that I was using an older nanbield environment, so decided to update to scarthgap, but unfortunately that didn't resolve the issue.

So far I have tried both the 6.6.23 and 6.6.36 releases, with the same result (I even tried the imx-image-multimedia and imx-image-full recipes). Interestingly, if I use the pre-built image downloadable from the website (L6.6.36_2.1.0_MX8MP) there doesn't seem to be any issues.

Checking the status of the systemd services shows the following:

systemd-networkd

root@imx8mp-lpddr4-evk:~# systemctl status systemd-networkd.service
x systemd-networkd.service - Network Configuration
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2024-02-27 17:26:11 UTC; 23s ago
TriggeredBy: x systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
man:org.freedesktop.network1(5)
Process: 785 ExecStart=/usr/lib/systemd/systemd-networkd (code=exited, status=203/EXEC)
Main PID: 785 (code=exited, status=203/EXEC)
FD Store: 0 (limit: 512)
CPU: 74ms
Feb 27 17:26:11 imx8mp-lpddr4-evk systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Feb 27 17:26:11 imx8mp-lpddr4-evk systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Feb 27 17:26:11 imx8mp-lpddr4-evk systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 27 17:26:11 imx8mp-lpddr4-evk systemd[1]: Failed to start Network Configuration.

systemd-resolved

root@imx8mp-lpddr4-evk:~# systemctl status systemd-resolved.service
x systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2024-02-27 17:26:09 UTC; 20min ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Process: 688 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=203/EXEC)
Main PID: 688 (code=exited, status=203/EXEC)
CPU: 114ms

Feb 27 17:26:09 imx8mp-lpddr4-evk systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5.
Feb 27 17:26:09 imx8mp-lpddr4-evk systemd[1]: systemd-resolved.service: Start request repeated too quickly.
Feb 27 17:26:09 imx8mp-lpddr4-evk systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Feb 27 17:26:09 imx8mp-lpddr4-evk systemd[1]: Failed to start Network Name Resolution.

systemd-timesyncd

root@imx8mp-lpddr4-evk:~# systemctl status systemd-timesyncd.service
x systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2024-02-27 17:26:08 UTC; 20min ago
Docs: man:systemd-timesyncd.service(8)
Process: 484 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=203/EXEC)
Main PID: 484 (code=exited, status=203/EXEC)
CPU: 117ms

Feb 27 17:26:08 imx8mp-lpddr4-evk systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Feb 27 17:26:08 imx8mp-lpddr4-evk systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Feb 27 17:26:08 imx8mp-lpddr4-evk systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 27 17:26:08 imx8mp-lpddr4-evk systemd[1]: Failed to start Network Time Synchronization.
Feb 27 17:26:08 imx8mp-lpddr4-evk systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Feb 27 17:26:08 imx8mp-lpddr4-evk systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 27 17:26:08 imx8mp-lpddr4-evk systemd[1]: Failed to start Network Time Synchronization.
Feb 27 17:26:09 imx8mp-lpddr4-evk systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Feb 27 17:26:09 imx8mp-lpddr4-evk systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Feb 27 17:26:09 imx8mp-lpddr4-evk systemd[1]: Failed to start Network Time Synchronization.

Finally, if I check the logs for networkd:

root@imx8mp-lpddr4-evk:~# journalctl -u systemd-networkd
Feb 27 17:26:10 imx8mp-lpddr4-evk systemd[1]: Starting Network Configuration...
Feb 27 17:26:10 imx8mp-lpddr4-evk (networkd)[737]: systemd-networkd.service: Failed to execute /usr/lib/systemd/systemd-networkd: Permission denied
Feb 27 17:26:10 imx8mp-lpddr4-evk systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=203/EXEC
Feb 27 17:26:10 imx8mp-lpddr4-evk systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 27 17:26:10 imx8mp-lpddr4-evk systemd[1]: Failed to start Network Configuration.
Feb 27 17:26:10 imx8mp-lpddr4-evk systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1.

 Any idea why this might happen? I have followed the instructions from the imx-manifest repo (nxp-imx/imx-manifest: i.MX Release Manifest (github.com)) (with MACHINE=imx8mp-lpddr4-evk).

Any help would be greatly appreciated, many thanks!

Alex

[amosercq]

Hi @clay_miller,

have you had a chance to replicate this?

[clay_miller]

Hi Alex,
I ran into several build issues when using the machine target imx8mp-lpddr4-evk. I'm thinking this target may not have gotten all then package updates yet for the newer releases, and might not be pointing to the relevant dts files to configure the Ethernet interfaces.
Try building for the machine target "imx8mpevk" to see if your Ethernet interfaces and phy setup correctly. You can build for core-image-minimal to quickly test the interfaces, but I don't think it comes with a presetup network service.
Regards,
Clay

[clay_miller]

Hi Alex,

I'll try to reproduce this behavior and get back to you.

In the mean time I have a few questions:

Did you make any edits to your Yocto build?

Do any of the network interfaces show up? 

Regards,

Clay

[amosercq]

Hi Clay,

thanks for the quick reply.

I didn't modify the build, the only edit I made is adding the following to local.conf:

PARALLEL_MAKE = "-j 2"
BB_NUMBER_THREADS = "2"

Interestingly, none of the network interfaces seem to be showing up when running ifconfig (other than the loopback).

[clay_miller]

Hi Alex,
Just following up in case that alternate/generic target didn't work. After resolving my own build issues, the target machine imx8mp-lpddr4-evk with the core-image-minimal recipe can successfully start up a network service with both eth0 and eth1 links up. I suggest performing a clean build to trigger Yocto to rebuild all packages.

I didn't get a chance to confirm with the imx-image-multimedia and imx-image-full recipes as those take much longer to build. Let me know if the issue persists.

Regards,
Clay

[amosercq]

Hi Clay,

Thanks for the follow up. Unfortunately neither using the generic target nor setting up a clean environment worked. Could I be missing something in the process? Or perhaps there is something wrong with the board I have?

I now completely deleted the directory with my Yocto environment and set a fresh one up, using the latest scarthgap manifest (repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml) and target imx8mp-lpddr4-evk (MACHINE=imx8mp-lpddr4-evk DISTRO=fsl-imx-xwayland source ./imx-setup-release.sh -b bld-xwayland).

The build succeeds (bitbake imx-image-core), but when I run the device it once again doesn't show any network interface.

root@imx8mp-lpddr4-evk:~# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

 I attached a log file with all the boot messages, in case that can be helpful.

Thank you for the support,
Alex