Hi I am building a custom Yocto image for the i.MX 95 Verdin Evaluation Kit. What device tree should I use ? Currently I am using imx95-19x19-verdin.dts but the ethernet is not working.
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
Device Tree Selection for i.MX 95 Verdin Evaluation Kit
For the i.MX 95 Verdin Evaluation Kit, you’ll need to select the appropriate base device tree that matches your hardware configuration (1).
Finding the Correct Device Tree
The device tree files for 64-bit modules like the i.MX 95 are located in specific directories (1):
- NXP modules:
/arch/arm64/boot/dts/freescale/ - TI modules:
/arch/arm64/boot/dts/ti
Choosing the Base Device Tree
When selecting your base device tree, you should (1):
- Choose the base device tree that matches the hardware platform - Toradex provides a set of base device trees for its hardware platforms
- Find a device tree layout of the module you are using and the respective carrier board level device tree to base your customization on
Creating Your Custom Device Tree
Once you identify the correct base device tree, you can create your custom version (1):
$ cp ./arch/arm64/boot/dts/freescale/imx8mm-verdin-wifi-dev.dts ./arch/arm64/boot/dts/freescale/imx8mm-verdin-wifi-dev-custom.dts
Troubleshooting Ethernet Issues
If ethernet is not working with your current device tree selection, this suggests you may need to:
- Verify you’re using the correct base device tree for the i.MX 95 Verdin Evaluation Kit
- Check the device tree binding documentation specific to your hardware platform for proper ethernet configuration (1)
- Review the carrier board-specific device tree to ensure ethernet interfaces are properly defined
Additional Resources
For comprehensive device tree customization guidance, refer to the Toradex documentation on Device Tree Technical Overview (2) and First Steps with Device Trees (1).
The sources don’t specify the exact device tree filename for the i.MX 95 Verdin Evaluation Kit, so you may need to check the actual device tree files in your kernel source to find the correct base device tree that includes proper ethernet support for your specific hardware configuration.
Best regards, Toradex AI Assistant.
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
Greetings @SeroshD,
You marked your thread with “torizon”. Does this mean you are building a Torizon OS based image for the i.MX95 Verdin EVK?
In any case, with my Torizon OS based image for the i.MX95 Verdin EVK, it’s using the imx95-19x19-verdin-adv7535-ap1302.dtb device tree by default. With this device tree ETH1 seems to be working fine.
Best Regards,
Jeremias
Hello @jeremias.tx
No I built an image with Yocto without Torizon OS.
Thank you for your answer. I solved my issue by enabling MSI, I had the kernel boot parameter psi=nomsi so I removed it.
Best Regards,
Serosh
I solved my issue by enabling MSI, I had the kernel boot parameter
psi=nomsiso I removed it.
So your issue here is resolved now yes?
Best Regards,
Jeremias
Yes the issue is resolved.
Thank you again