Current torizoncore-builder build not running properly IVY Plus

Technical Support
, , , ,
1

I am using the quarterly build:
torizon-docker-verdin-imx8mp-Tezi_7.2.0+build.13.tar
and originally was just trying to add the second Ehternet port. I got some suggestions from tech support which didn’t seem to work and I finally just went with:
custom: linux/arch/arm64/boot/dts/freescale/imx8mp-verdin-wifi-ivy.dts
in my tcbuild.yaml file, which worked.
I moved to 24.04 and did the tcb install and clone of the directories and used the same yaml file, but I get problems at boot up. I get all these errors saying it fails to start:
Starting kernel …

[ 1.005675] imx-drm display-subsystem: no available port
[ 1.128111] mdio_bus 30be0000.ethernet-1: MDIO device at address 7 is missing.
Starting systemd-udevd version 255.17^
sysroot.readonly configuration value: 0 (fs writable: 1)
Using legacy ostree bind mount for /
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Time Synchronization.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Time Synchronization.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Time Synchronization.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Time Synchronization.
[ 6.726157] imx-bus-devfreq 32700000.interconnect: failed to fetch clk: -2
[FAILED] Failed to start Modem Manager.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Time Synchronization.
[FAILED] Failed to start Bluetooth service.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Time Synchronization.
[FAILED] Failed to start Hostname Service.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start User Login Management.
[ 9.224707] tpm tpm0: A TPM error (256) occurred attempting the self test
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.

Torizon OS 7.2.0+build.13 verdin-imx8mp-15139619 ttymxc2

verdin-imx8mp-15139619 login:

I have tried clearing all the overlays to see if something has changed, but I still get the same thing. The reasons I was doing this was

  1. 20.04 has gone obsolete,
  2. We decided not to use the USB NCM connection, as it didn’t work with the tablet we are using.

The only difference in this build case was I am not using the “isolate” changes we have in the build file, as I was going to make all the changes starting with just the 2 Ethernet ports working.

Any suggestions as to how to proceed here would be helpful.
I can log in, although it took a while to come back with the prompt.

So, I tried just taking the tar file and unpacking it, then deploying that. Shouldn’t that be the same as the original, without any changes? I get the same errors with that.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello! Thank you for your detailed description. Let’s break down your situation and outline how to proceed step by step.

Key Points Noted:

  • You’re running Torizon OS 7.2.0 on Verdin iMX8MP and customizing for a second Ethernet port.
  • You previously used custom device trees that worked with older Torizon versions.
  • Now, after cloning your config to 24.04 and using the same tcbuild.yaml, you’re seeing many [FAILED] service errors.
  • Unpacking and deploying the base Torizon OS image without changes still presents issues.

Suggestions to Troubleshoot and Proceed

1. Kernel and Device Tree Version Match

Custom device trees must match the kernel version of your TorizonCore image. Device trees that worked in earlier TorizonCore versions may not be compatible with 7.2.0. If you are moving from a previous major version, always re-base your device tree on the version provided in the Linux source tree for 7.2.0.

Resource:

2. Test Plain Base Image

When you unpack and deploy the unmodified base tarball image (via TorizonCore Builder’s images unpack and images deploy), your board should boot without the system service failures.

  • If the failures still occur with no customizations, something may be wrong with the deployment method, media, or image integrity.
  • If you used Toradex Easy Installer, try re-deploying the original image to rule out corruption.

Resource:

3. Device Tree Customization

If the plain base image works, but your custom device tree triggers errors:

  • Re-clone the device tree from the 7.2.0 kernel sources, not from your older setup.
  • Carefully apply customizations (like enabling the second Ethernet port) on top of the fresh 7.2.0 device tree, rather than porting in your old .dts.

Resource:

4. Investigate Boot Errors

Typical reasons for the [FAILED] systemd services:

  • Network: Misconfigured device tree or missing interface drivers impacts network and timesync services.
  • User Login: If device nodes aren’t created properly due to device tree misconfiguration, login management can fail.
  • Modem/Bluetooth: Device tree nodes for hardware that isn’t present/working may trigger service failures.

If the hardware is unchanged and the base image fails, these might be software/compatibility problems. If only after custom changes, they’re likely device tree or kernel configuration related.

5. Next Steps

  • Verify with Base Image: Ensure the unmodified Torizon 7.2.0 image boots without service errors.
  • Start with Fresh Device Tree: Use the latest device tree from Torizon 7.2.0, re-applying only the essential Ethernet changes.
  • Incrementally Apply Customizations: Make and test one change at a time, rebooting and checking for errors after each.

If you specify which Device Tree changes you made (especially for the second Ethernet), I can help identify if adjustments are needed for 7.2.0.

If you need guidance on identifying the correct device tree source for Torizon 7.x and how to apply your custom changes, let me know!

Best regards,
Toradex AI Assistant.

Ensure device tree compatibility
Image deployment workflow

3

Hey @EvetsMostel1,

This is a little difficult to follow. It sounds like you have copy and pasted TCB project files from one host computer to another, going from 20.04 to 24.04 OS versions. And the project worked on 20.04, but does not on 24.04?

-Eric

4

No. The only thing I really copied was the build.yaml file. The install of builder and the clone of the Linux and device-trees directory, was done in the usual way. I downloaded the tar files the same way and put them in an ./images directory. When I start torizoncore-builder, i source the tcb-env-setup.sh.
I got it to work when I downloaded 7.3.0+build9.tar and went away from 7.2.0+build13.tar. As you know, 7.3.0 is a “smoke test” build, where 7.2.0 is a quarterly release.

Steve

5

Hey @EvetsMostel1,

Were you able to compile the torizoncore-buillder image successfully?

-Eric