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
-
How can I verify from U-Boot whether the Ethernet PHY is detected
correctly? -
Which U-Boot commands should I use to check the PHY ID, PHY
registers, link status, auto-negotiation, speed and duplex? -
Is there a way to reset or reinitialize the Ethernet PHY completely
from U-Boot? -
Can the Ethernet PHY/link be tested independently of Torizon OS?
-
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? -
Are there any U-Boot environment variables, device-tree settings, or
configuration settings that could prevent the Ethernet PHY/link LEDs
from becoming active? -
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.