Colibri iMX7D 1GB – Ethernet Link LED Not Blinking / No Physical Link in U-Boot

Hello Toradex Community,

I am troubleshooting an Ethernet/LAN issue on a Colibri iMX7D 1GB V1.1B
module.

The Ethernet link/activity LEDs do not blink or turn ON when a LAN cable
is connected. I am currently testing the module directly from U-Boot,
before installing Torizon OS, to determine whether this is an
OS/software issue or a hardware/PHY issue.

Hardware / U-Boot Information

Module: Toradex Colibri iMX7D 1GB V1.1B U-Boot:
2022.07-6.8.9+git.e092e3250270 CPU: Freescale i.MX7D rev1.3 DRAM: 1 GiB
Ethernet interface detected by U-Boot: eth0: ethernet@30be0000 Reset
cause: POR

Relevant U-Boot output:

U-Boot 2022.07-6.8.9+git.e092e3250270 (Jan 01 1970 - 00:00:00 +0000)

CPU: Freescale i.MX7D rev1.3 1000 MHz (running at 792 MHz) CPU: Extended
Commercial temperature grade (-20C to 105C) at 35C Reset cause: POR
DRAM: 1 GiB Core: 52 devices, 17 uclasses, devicetree: separate PMIC:
RN5T567 LSIVER=0x01 OTPVER=0x0d MMC: FSL_SDHC: 1, FSL_SDHC: 0 Loading
Environment from MMC… OK In: serial Out: serial Err: serial Model:
Toradex 0039 Colibri iMX7D 1GB V1.1B Serial#: 08945925 SEC0: RNG
instantiated Net: eth0: ethernet@30be0000 Hit any key to stop autoboot:
0 switch to partitions #0, OK mmc0(part 0) is current device ** No
partition table - mmc 0 ** Couldn’t find partition mmc 0:1 Colibri iMX7

The “No partition table” message is expected at the moment because the
module does not currently have an OS installed. My main concern is the
Ethernet physical link.

Problem

When I connect a known-working Ethernet cable, the LAN link/activity
LEDs remain completely OFF.

The same carrier board, Ethernet cable, Ethernet connection/network, and
power supply work correctly when I replace this Colibri iMX7D module
with another working Colibri iMX7 module.

Therefore, the problem appears to follow this particular module rather
than the carrier board or LAN cable.

U-Boot still detects the Ethernet controller:

Net: eth0: ethernet@30be0000

but there is no visible physical Ethernet link.

Questions

  1. How can I verify from U-Boot whether the Ethernet PHY is detected
    correctly?

  2. Which U-Boot commands should I use to check the PHY ID, PHY
    registers, link status, auto-negotiation, speed and duplex?

  3. Is there a way to reset or reinitialize the Ethernet PHY completely
    from U-Boot?

  4. Can the Ethernet PHY/link be tested independently of Torizon OS?

  5. Since another Colibri iMX7 works correctly on the exact same carrier
    board and Ethernet connection, could this indicate a hardware/PHY
    issue with this particular module?

  6. Are there any U-Boot environment variables, device-tree settings, or
    configuration settings that could prevent the Ethernet PHY/link LEDs
    from becoming active?

  7. Is there any recommended diagnostic procedure from Toradex for
    determining whether the PHY hardware on the Colibri module is
    damaged?

I would like to verify the Ethernet hardware thoroughly from U-Boot
before installing/reinstalling Torizon OS.

Please let me know which U-Boot commands/output would be useful, and I
can provide the results.

Thank you.

Hi, I’m the Toradex AI Assistant.

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


Ethernet PHY Diagnostics from U-Boot on Colibri iMX7D

Your troubleshooting approach is sound—testing from U-Boot helps isolate whether this is a hardware or software issue. Since the problem follows the module rather than the carrier board, and another Colibri iMX7 works correctly in the same setup, this does point toward a module-specific issue.

U-Boot PHY Diagnostics

1. Verify PHY Detection and Read PHY Registers

U-Boot provides the mii command to interact directly with the PHY through the MDIO bus. You can use it to:

Check if the PHY responds at its expected address:

Colibri iMX7 # mii device

This lists available MII devices.

Read the PHY ID registers:

Colibri iMX7 # mii info

This should display the PHY identifier. For the Colibri iMX7D, you should see a valid PHY ID (not 0x00000000 or 0xffffffff).

Read specific PHY registers:

Colibri iMX7 # mii read <address> <register>

For example, to read register 2 (PHYIDR1) at address 0:

Colibri iMX7 # mii read 0 2

A response of all zeros (0x0000) or all ones (0xffff) across all addresses indicates a communication problem(1).

2. Check Link Status and Auto-Negotiation

Read the Basic Status Register (register 1):

Colibri iMX7 # mii read 0 1

Bit 2 indicates link status. If it’s 0, there’s no physical link established.

Dump all PHY registers:

Colibri iMX7 # mii dump 0

This provides a complete view of the PHY’s register state.

3. Reset and Reinitialize Ethernet

Reinitialize the network interface:

Colibri iMX7 # dhcp

or

Colibri iMX7 # ping <ip_address>

These commands force U-Boot to bring up the Ethernet interface and attempt PHY negotiation.

Software reset the PHY:

Colibri iMX7 # mii write 0 0 0x8000

This sets the reset bit in the control register.

Diagnostic Interpretation

Based on the troubleshooting guidance(1), if you see:

  • All addresses return 0xffff: The MDIO line is stuck high—possible unpowered PHY, PHY held in reset, missing PHY clock, or hardware fault
  • All addresses return 0x0000: The MDIO line is stuck low—possible incorrect pin multiplexing, signal held low, or broken MDIO signal path(1)
  • Valid PHY ID but no link: Check cable, verify RGMII configuration, or potential PHY hardware issue

Hardware vs. Software Issue

Since:

  1. U-Boot detects eth0: ethernet@30be0000 (MAC controller is present)
  2. Another Colibri iMX7 works on the same carrier board
  3. LEDs remain completely off (no PHY activity)

The most likely causes are:

  • PHY not responding on MDIO bus (hardware fault on the module)
  • PHY not receiving power or clock (module-level issue)
  • Damaged PHY chip on this specific module

Recommended Next Steps

  1. Run mii info and mii dump 0 to check PHY communication
  2. Try addresses 0-7 if the PHY doesn’t respond at address 0
  3. Check if all MDIO reads return the same value (indicates bus-level fault)
  4. If the PHY doesn’t respond at all, this strongly suggests hardware damage to the module

Device Tree and Environment Variables

While device tree settings can affect PHY configuration in Linux, U-Boot typically uses its own compiled-in device tree. Environment variables like fdtfile affect which device tree Linux loads, not U-Boot’s PHY initialization(1). Since U-Boot detects the MAC controller, the basic hardware description is present.

Production Testing

Unfortunately, the provided documentation doesn’t include specific Toradex factory diagnostic procedures for PHY hardware validation. However, the MDIO register scan approach described above is the standard method for determining PHY hardware health(1).

If the mii commands show no PHY response or all-zeros/all-ones values across all addresses, this would confirm a hardware-level fault with the Ethernet PHY on this particular module.

Please share the output of mii info and mii dump 0 commands, and I can help interpret the results.

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.

Thank you for the suggestions. I followed the suggested steps one by one. Below is the output of the commands:

Colibri iMX7 # mii device
MII devices: ‘FEC0’
Current device: ‘FEC0’

Colibri iMX7 # mii info
PHY 0x00: OUI = 0x0885, Model = 0x11, Rev = 0x03, 10baseT, HDX
PHY 0x01: OUI = 0x0885, Model = 0x11, Rev = 0x03, 10baseT, HDX

Colibri iMX7 # mii read 0 2
0022

Colibri iMX7 # mii read 0 1
7849

Colibri iMX7 # dhcp
ethernet@30be0000 Waiting for PHY auto negotiation to complete… TIMEOUT !
Could not initialize PHY ethernet@30be0000
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

Abort

Colibri iMX7 # mii write 0 0 0x8000

Colibri iMX7 # mii dump 0
0. (3100) – PHY control register –
(8000:0000) 0.15 = 0 reset
(4000:0000) 0.14 = 0 loopback
(2040:2000) 0. 6,13 = b01 speed selection = 100 Mbps
(1000:1000) 0.12 = 1 A/N enable
(0800:0000) 0.11 = 0 power-down
(0400:0000) 0.10 = 0 isolate
(0200:0000) 0. 9 = 0 restart A/N
(0100:0100) 0. 8 = 1 duplex = full
(0080:0000) 0. 7 = 0 collision test enable
(003f:0000) 0. 5- 0 = 0 (reserved)

@ToradexAI, even after performing all the above checks, the Ethernet connection is still not working.

The LAN link/activity LEDs do not turn on or blink when the Ethernet cable is connected. The DHCP command also reports that PHY auto-negotiation is timing out:

“Waiting for PHY auto negotiation to complete… TIMEOUT !”
“Could not initialize PHY ethernet@30be0000”

As mentioned earlier, the same carrier board, LAN cable, network connection, and power supply work correctly when I use another Colibri iMX7 module.

Could you please check the above PHY output and advise what I should test next?

Does this output indicate that the PHY is responding over MDIO but is unable to establish a physical Ethernet link?

Could this be a hardware-related issue with the Ethernet PHY or Ethernet interface on this particular Colibri iMX7 module?
@ToradexAI
Thank you.

Analysis of PHY Diagnostics Output

Thank you for providing the detailed command outputs. Let me analyze what they reveal about your Ethernet PHY issue.

PHY Communication Status

The good news is that the PHY is responding on the MDIO bus:

PHY 0x00: OUI = 0x0885, Model = 0x11, Rev = 0x03, 10baseT, HDX
  • PHY ID register 2 returns 0x0022 — This is a valid response, not 0x0000 or 0xffff
  • OUI = 0x0885 indicates a Micrel/Microchip PHY (likely KSZ8041 or similar)
  • The PHY is detected at address 0 and is communicating properly via MDIO

This rules out the most severe hardware faults (dead PHY chip, broken MDIO bus, or complete power failure)(1).

The Critical Problem: Auto-Negotiation Timeout

However, your dhcp output reveals the actual issue:

ethernet@30be0000 Waiting for PHY auto negotiation to complete… TIMEOUT !
Could not initialize PHY ethernet@30be0000

This means:

  • The MAC can talk to the PHY via MDIO ✓
  • The PHY responds to register reads/writes ✓
  • BUT the PHY cannot establish a physical link with the network peer ✗

PHY Register Analysis

Your register dump shows:

0.     (3100)                 – PHY control register –
(1000:1000) 0.12    =     1     A/N enable
(2040:2000) 0. 6,13 =   b01    speed selection = 100 Mbps
(0100:0100) 0. 8    =     1     duplex = full

The PHY is configured for:

  • Auto-negotiation: Enabled
  • Speed: 100 Mbps
  • Duplex: Full

However, when you read register 1 (Basic Status Register), you got 0x7849:

Colibri iMX7 # mii read 0 1
7849

Breaking down 0x7849 in binary:

  • Bit 2 (Link Status) = 0 — No link established
  • Bit 5 (Auto-negotiation complete) = 0 — Auto-negotiation has not completed

This confirms that while the PHY chip itself is functional and responding, it cannot establish a physical Ethernet link.

Likely Root Causes

Since another Colibri iMX7 module works perfectly on the same carrier board with the same cable, and this module’s PHY responds on MDIO but cannot establish link, the most probable causes are:

1. Damaged PHY Transceiver Circuitry

The MDIO interface (digital control) works, but the analog transceiver section (which handles the actual Ethernet signals on the RJ45) may be damaged. This can happen from:

  • ESD (Electrostatic Discharge) events
  • Overvoltage on Ethernet pins
  • Physical damage to the module

2. RGMII/MII Interface Issues Between MAC and PHY

The data path between the i.MX7’s Ethernet MAC and the PHY chip may have issues(1). However, since this is an on-module connection (not on the carrier board), and the working module uses the same design, this points to module-level hardware damage.

3. PHY Crystal/Clock Issues

If the PHY’s reference clock or crystal oscillator is not functioning, the PHY may respond to MDIO commands but cannot generate proper Ethernet signals for link negotiation.

Additional Diagnostic Steps

To further isolate the issue, try these additional checks:

Check PHY Extended Registers

Read the PHY status register to see link partner detection:

Colibri iMX7 # mii read 0 0x1f

Read register 0x1e (if supported by your PHY model):

Colibri iMX7 # mii read 0 0x1e

Force Link Mode (Bypass Auto-Negotiation)

Try forcing the PHY to 10 Mbps half-duplex to see if it can establish any link:

Colibri iMX7 # mii write 0 0 0x0000
Colibri iMX7 # dhcp

Then try 100 Mbps full-duplex forced mode:

Colibri iMX7 # mii write 0 0 0x2100
Colibri iMX7 # dhcp

If the link still doesn’t come up in forced mode, this strongly indicates hardware-level PHY transceiver damage.

Check for Multiple PHY Addresses

Your mii info showed:

PHY 0x00: OUI = 0x0885, Model = 0x11, Rev = 0x03, 10baseT, HDX
PHY 0x01: OUI = 0x0885, Model = 0x11, Rev = 0x03, 10baseT, HDX

Two PHYs appear at addresses 0 and 1 with identical IDs. This is unusual. Try targeting address 1:

Colibri iMX7 # mii device FEC0
Colibri iMX7 # mii read 1 1
Colibri iMX7 # mii dump 1

Conclusion and Recommendation

Based on your diagnostic output:

  1. ✓ PHY chip is alive and responding to MDIO commands
  2. ✓ MDIO bus communication works (not a bus-level fault(1))
  3. ✗ PHY cannot establish physical Ethernet link (auto-negotiation timeout)
  4. ✗ Link LEDs remain off (no PHY activity on the wire)
  5. ✓ Another module works on same carrier board (rules out carrier board issue)

This pattern strongly suggests hardware damage to the Ethernet PHY’s analog transceiver section on this specific Colibri iMX7D module.

The PHY’s digital control interface (MDIO) works, but the analog circuitry that drives the actual Ethernet signals appears non-functional. This type of failure is consistent with ESD damage or overvoltage events on the Ethernet port.

Next Steps

  1. Try the forced link mode tests above to confirm
  2. If those also fail, the module likely has permanent hardware damage to the Ethernet PHY
  3. Contact Toradex support directly for RMA evaluation if the module is under warranty

Unfortunately, this type of hardware fault cannot be resolved through software, U-Boot commands, or OS reinstallation.

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.