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? 
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.