Thank you for providing those details! Since you’re using TorizonCore 6.6.1 on a Verdin iMX8M Mini DualLite 1GB with the Verdin Development Board V1.1F, and other modules work fine with the same setup, this points to a module-specific configuration issue.
Troubleshooting Steps
1. Check NetworkManager and Ethernet Interface Status
First, let’s verify the NetworkManager service and interface status:
systemctl status NetworkManager
Then check the Ethernet interface state:
nmcli device status
ip link show eth0
2. Check for DHCP Activity
Monitor DHCP requests in real-time:
journalctl -u NetworkManager -f
Then try to restart the Ethernet interface:
nmcli device disconnect eth0
nmcli device connect eth0
Watch the journal output for any DHCP-related errors or timeout messages.
3. Verify Ethernet Driver and PHY
Check if the Ethernet driver loaded correctly:
dmesg | grep -i eth
dmesg | grep -i fec
The Verdin iMX8M Mini uses the Microchip KSZ9131 Ethernet PHY(1). Look for any PHY initialization errors or link negotiation issues in the output.
4. Manual IP Configuration Test
To isolate whether this is a DHCP-specific issue, try assigning a static IP temporarily:
nmcli connection modify "Wired connection 1" ipv4.method manual ipv4.addresses 192.168.1.100/24 ipv4.gateway 192.168.1.1
nmcli connection down "Wired connection 1"
nmcli connection up "Wired connection 1"
If a static IP works but DHCP doesn’t, the issue is likely with DHCP client communication.
5. Check Device Tree and Hardware Configuration
Verify the device tree is correctly loaded:
cat /proc/device-tree/model
Check if there are any hardware-related errors:
dmesg | grep -i error
dmesg | grep -i fail
Potential Root Causes
Given that:
- The link is established (physical layer works)
- Other modules work fine with identical setup
- NetworkManager is running
- Reflashing didn’t resolve it
This could indicate:
- MAC Address Issue: The module might have a duplicate or invalid MAC address
- DHCP Client Problem: The DHCP discover packets might not be sent or received properly
- Kernel/Driver Issue: A module-specific driver initialization problem
Check MAC Address
Verify the MAC address is valid and unique:
ip link show eth0
cat /sys/class/net/eth0/address
The MAC address should start with 00:14:2D (Toradex OUI)(1).
Next Steps
Please run the commands above and share:
- The output of
dmesg | grep -i eth
- The output of
journalctl -u NetworkManager (last 50 lines)
- The MAC address from
ip link show eth0
- Whether static IP assignment works
This will help identify whether the issue is at the DHCP layer, driver layer, or hardware configuration level.
Best regards,
Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
