Torizon libphy: PHY fixed-0:00 not found

Hello

Now and then when booting my image based on torizon-core-docker.bb and the latest toradex_4.20.y branch i get an error that the on-module phy could not be found.

I also experience this behavior on the latest torizon-core from tezi.toradex.com:

U-Boot 2016.11-1.0b1+g07edca0bb8 (Jan 01 1970 - 00:00:00 +0000)

CPU:   Freescale i.MX7D rev1.3 996 MHz (running at 792 MHz)
CPU:   Extended Commercial temperature grade (-20C to 105C) at 38C
Reset cause: POR
DRAM:  1 GiB
PMIC:  RN5T567 LSIVER=0x01 OTPVER=0x0d
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Video: 640x480x18
In:    serial
Out:   serial
Err:   serial
Model: Toradex Colibri iMX7 Dual 1GB (eMMC) V1.1A, Serial# 06476991
Net:   FEC0
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
reading /boot.scr
2173 bytes read in 14 ms (151.4 KiB/s)
## Executing script at 87000000
445 bytes read in 123 ms (2.9 KiB/s)
48090 bytes read in 119 ms (394.5 KiB/s)
7528960 bytes read in 290 ms (24.8 MiB/s)
2804984 bytes read in 177 ms (15.1 MiB/s)
Kernel image @ 0x81000000 [ 0x000000 - 0x72e200 ]
## Flattened Device Tree blob at 82000000
   Booting using the fdt blob at 0x82000000
   Loading Device Tree to 8fff1000, end 8ffffbd9 ... OK

Starting kernel ...

[    0.841722] caam 30900000.caam: failed to acquire DECO 0
[    0.847070] caam 30900000.caam: failed to instantiate RNG
Starting version 241-9-gc1f8ff8+
Resolved OSTree target to: /rootfs/ostree/deploy/torizon/deploy/d0a8ffe53ac06f7b593886474584ebf95cfe9805a196be75397efc254d263073.0
[    3.437133] sd 0:0:0:0: [sda] No Caching mode page found
[    3.442500] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    8.853484] libphy: PHY fixed-0:00 not found
[    8.857766] fec 30be0000.ethernet eth0: could not attach to PHY

TorizonCore 1.0b1 colibri-imx7-06476991 ttymxc0

colibri-imx7-06476991 login:

I really didn’t pay attention when this happens but i do now - most of the time i am pressing the reset button on the eval board.

Can this be related to 50890_U-boot: “Could not initialize PHY FEC” Issue After Software Reboot when uboot doesen’t get to do its things?

Hi @m.tellian,

Is this issue experienced when you you power off completely then power back on? Or is it just when the reset button is used? How about when the reboot command is used on the command line?

Best Regards,
Jeremias