Verdin IMX95: 2nd Ethernet port not working

The 2nd Ethernet port on my new Verdin IMX95 with Ivy Plus Carrier Board doesn’t work. Both the prebuilt Toradex torizonOS and yocto images downloaded from the Toradex developer website gives the same error:

$ sudo ifconfig ethernet1 up
net ethernet1: could not attach to PHY
SIOCSIFFLAGS: No such device

Is this a hardware issue? Anyone have the same hardware to cross check?
Thanks

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


I’d be glad to help troubleshoot the second Ethernet port issue! To provide the most accurate guidance, could you let me know:

  1. Which OS and version are you running? (e.g., Torizon OS 7.2.0, specific Yocto BSP version)
  2. Which carrier board are you using? (e.g., Verdin Development Board, custom carrier board)

The Verdin iMX95 features 2x Gigabit Ethernet (1x PHY with TSN and AVB + 1x RGMII) according to the specifications (1). However, the second Ethernet port configuration can vary depending on your carrier board design and device tree configuration.

For reference, you can use the tdx-info command to get detailed information about your system configuration. More details are available at: Getting Device Information with Tdx-Info | Toradex Developer Center

The second Ethernet port typically requires proper device tree configuration and may need to be manually enabled depending on your carrier board design (2). Once I know your specific setup, I can provide targeted troubleshooting steps for your configuration.

Common platforms to consider:

  • Hardware: Verdin iMX95, carrier boards (Development Board, custom designs)
  • OS: Torizon OS versions, Yocto BSP versions
  • Integration: Device tree configuration, Ethernet drivers

Best regards, Toradex AI Assistant.


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

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

I’m running on the Verdin Ivy Plus carrier board with Yocto BSP 7.

Based on the error you’re seeing, this appears to be a device tree configuration issue rather than a hardware problem. The Verdin iMX95 does support dual Ethernet, but the second Ethernet port needs to be properly configured in the device tree (1).

Troubleshooting Steps

1. Check Current Device Tree Configuration

First, verify which device tree binary is currently loaded:

# fw_printenv fdtfile

(1)

2. Enable the Correct Device Tree for Ivy Plus

The Ivy Plus carrier board should have its specific device tree that includes the second Ethernet configuration. You’ll need to set the appropriate device tree binary using U-Boot fw-utils:

# sudo fw_setenv fdtfile <ivy-plus-device-tree>.dtb

(1)

Then reboot to apply the changes:

# reboot

(1)

3. Verify Second Ethernet Configuration

For SoMs with dual Ethernet, the second Ethernet controller is typically available as RGMII and requires proper device tree configuration (1). The second Ethernet port needs:

  • Proper PHY configuration in the device tree
  • Correct pin muxing for RGMII signals
  • Power control configuration if applicable

4. Check Available Device Trees

List the available device tree binaries for your BSP 7 installation:

# ls /boot/*.dtb

Look for a device tree specifically for the Ivy Plus carrier board with Verdin iMX95.

5. Manual MAC Address Configuration

If the device tree is correct but you’re still having issues, you can manually set the second Ethernet MAC address in U-Boot:

U-Boot # setenv eth1addr 01:23:45:67:89:ac
U-Boot # saveenv

(1)

Additional Considerations

The error “could not attach to PHY” typically indicates that the Ethernet controller cannot communicate with the PHY chip, which is usually due to:

  • Missing or incorrect device tree configuration
  • PHY not being detected on the MDIO bus
  • Incorrect PHY address configuration
  • Missing power control for the PHY

Since you’re using BSP 7 with Verdin iMX95, make sure you have the correct device tree overlay or device tree binary that specifically supports the Ivy Plus carrier board’s second Ethernet implementation.

Best regards, Toradex AI Assistant.


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

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

The device tree file seems to be correct:

Verdin iMX95 # print fdtfile
fdtfile=imx95-verdin-wifi-dev.dtb

I don’t see a different ivy-plus dtb. Just one dtb for ivy.

Hey @dtran11

You can check the proper device tree for you board in our dedicated article, and it is also available in the quickstart for you particular configuration.

the correct one would be imx95-verdin-wifi-ivy.dtb
while imx95-verdin-wifi-dev.dtb corresponds to the Verdin development board.

Please give a try and let us know if the issue still remains.

That fixed it. Thank you!

What’s the best way to set the preferred dtb file for my yocto build? Is it to make a bbappend to u-boot-toradex for the “fdt_board=ivy” in board/toradex/verdin-imx95/verdin-imx95.env?