Ethernet 2 port on Aquila iMX95 Development Board

Technical Support
1

Hi,

I have compiled an image using yocto for the iMX95 Aquila Development Board, building upon this example with a realtime kernel and building the reference-minimal-image provided by Toradex. The device trees used seem to include also the ethernet ports, but ethernet port 2 (end1) is missing when I type ip link.

I found these kernel logs that show that the MDIO dev cannot be created:
[ 0.243263] fsl_enetc_mdio 0003:01:00.0: Cannot get IERB init status: -517

[ 0.301075] ptp_netc 0002:00:18.0: enabling device (0000 -> 0002)

[ 0.407762] fsl_enetc_mdio 0003:01:00.0: enabling device (0000 -> 0002)

[ 1.633806] imx6q-pcie 4c300000.pcie: Phy link never came up

[ 2.635045] imx6q-pcie 4c300000.pcie: Phy link never came up

[ 7.047921] optee: probing for conduit method.

[ 7.246866] fsl_enetc4 0002:00:00.0: Adding to iommu group 5

[ 7.351703] fsl_enetc4 0002:00:00.0: enabling device (0000 -> 0002)

[ 7.518289] fsl_enetc4 0002:00:10.0: Adding to iommu group 6

[ 7.628434] fsl_enetc4 0002:00:10.0: enabling device (0000 -> 0002)

[ 7.650376] fsl_enetc4 0002:00:00.0 end0: renamed from eth0

[ 8.139643] mdio_bus 0002:00:10.0-imdio:10: Polling timeout, line: 395

[ 8.149691] fsl_enetc4 0002:00:10.0: cannot create xpcs mdiodev (-19)

[ 8.150058] fsl_enetc4 0002:00:10.0: Failed to create MDIO bus

I have tried several things, including changing the device tree but none of these seem to work. What could be something else to try? I am expecting the supplied device trees for this development board to work out of the box, so that is why I’m hestitant to put a lot of time in figuring this out before asking here. Thanks in advance!

2

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 Ethernet port 2 (end1) issue on your Aquila iMX95 Development Board! To provide you with the most accurate guidance, could you please clarify a few details about your setup?

  1. Which exact OS version and BSP are you running? (e.g., Yocto 7.2.0, BSP 7.x.y, Torizon OS 7.x.x)
  2. Which specific Aquila iMX95 module variant are you using? (e.g., Aquila iMX95 Hexa 8GB WB IT, Aquila iMX95 Hexa 4GB IT, etc.)

You can get this information by running the tdx-info command on your device. More details about this tool are available at https://developer.toradex.com/software/development-resources/tdx-info/.

The kernel logs you’ve shared suggest an MDIO initialization issue and a PCIe link problem, which could be related to device tree configuration or hardware initialization timing. However, the exact solution may depend on your specific BSP version and hardware configuration.

Once you provide these details, I’ll be able to guide you more effectively on whether this is a known issue, a device tree overlay requirement, or something else that needs adjustment in your Yocto build.

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.

3

Hi @daan0308!

Unfortunately, this is a known issue, and we are already working to fix this.

Best regards.

4

Hi @lucas_az.tx ,

Thanks for the response. If there is anything I can do to help you in this let me know. But probably you’re way more experienced. For the versions, I’m using the latest versions:
BSP: 7.6.1
Kernel: Downstream Toradex v6.6.138 based on NXP BSP L6.6.52_2.2.2
Yocto: 5.0 (Scarthgap)
U-Boot: Downstream Toradex 2024.04 based on NXP lf_v2024.04
TF-A firmware: NXP lf-6.6.52-2.2.1
Release: 05/2026
as stated in the tutorial with the defaults.xml

Best regards,

Daan

5

Hi @daan0308!

Thanks for sharing the details of your setup.

Over the next few days, we will add this issue to the Aquila iMX95 Known Issues list until it is resolved.

Best regards.