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? 
Device Tree Configuration for Verdin AM62 on Ivy Carrier Board
The issue you’re experiencing with ETH2 not being available is likely related to the device tree configuration. The mismatch between the U-Boot detection (“Verdin Development Board”) and your actual hardware (Ivy Carrier Board) indicates that the system is loading the wrong device tree.
Understanding the Issue
The Verdin AM62 supports multiple carrier boards, and each requires specific device tree configurations to enable all interfaces properly (1). When the wrong device tree is loaded, certain peripherals like the second Ethernet interface may not be initialized correctly.
Checking Currently Used Device Tree
To check which device tree is currently being used, you can examine the applied overlays (2):
# ls /proc/device-tree/chosen/overlays/
(2)
For each overlay that was applied successfully, you’ll see files with .dtbo extensions, and their values should be 0 if applied correctly (2):
# cat /proc/device-tree/chosen/overlays/<overlay_name>.dtbo
(2)
Networking Interface Configuration
Torizon OS uses NetworkManager for network configuration, and Ethernet interfaces are named ethernet0, ethernet1, etc. (3). You can check the status of your network devices with:
# nmcli device
(3)
To show available connections and devices:
# nmcli connection show
(3)
Device Tree Customization Options
Since you need the correct device tree for the Ivy Carrier Board, you have two main approaches (1):
-
Using Device Tree Overlays: This is the recommended approach for simple modifications and when readily-available overlays exist for your hardware configuration (1).
-
Custom Device Tree: For more complex modifications or when specific overlays aren’t available (1).
Enabling the Second Ethernet Interface
The Verdin AM62 features dual Gigabit Ethernet - one with an integrated PHY and another with RGMII interface (4). The second Ethernet interface may require specific device tree configuration or overlays to be properly enabled on the Ivy Carrier Board.
Recommended Next Steps
-
Verify Hardware Configuration: Ensure your Ivy Carrier Board has the second Ethernet interface properly connected and configured.
-
Check Available Overlays: Look for Ivy-specific device tree overlays in the /boot/ostree/tori.../dtb/ directory.
-
Apply Correct Device Tree: You may need to use TorizonCore Builder to create a custom image with the appropriate device tree configuration for the Ivy Carrier Board.
-
Network Interface Configuration: Once the correct device tree is loaded, configure both Ethernet interfaces using NetworkManager commands (3).
The key is ensuring that the system loads the device tree configuration specific to your Ivy Carrier Board rather than the default Verdin Development Board configuration.
Best regards,
Toradex AI Assistant.
