i.MX ProcessorsのトピックRe: Could not initialize PHY ethernet@30be0000

Could not initialize PHY ethernet@30be0000

inigovicentewal — Fri, 07 Feb 2020 12:28:42 GMT

Hi,

I am using u-boot in iMX8M Mini EVK and i have this problem.

How can i solve this problem? Any idea?

On mx8mm-evk side the debug console shows:

U-Boot SPL 2018.03-imx_v2018.03_4.14.98_2.0.0_ga+g87a19df (Apr 11 2019 - 11:14:18 +0000)
power_bd71837_init
DDRINFO: start lpddr4 ddr init
DRAM PHY training for 3000MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 400MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 100MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 3000MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC2

U-Boot 2018.03-imx_v2018.03_4.14.98_2.0.0_ga+g87a19df (Apr 11 2019 - 11:14:18 +0000)
CPU: Freescale i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 33C
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM: 2 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52]
Power supply on USB2
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment
Failed (-5)
No panel detected: default to MIPI2HDMI
adv7535_init: Can't find device id=0x3d, on bus 1
Display: MIPI2HDMI (1920x1080)
Video: 1920x1080x24
In: serial
Out: serial
Err: serial
BuildInfo:
- ATF 1cb68fa
- U-Boot 2018.03-imx_v2018.03_4.14.98_2.0.0_ga+g87a19df
switch to partitions #0, OK
mmc1(part 0) is current device
flash target is MMC:1
Net:
Warning: ethernet@30be0000 using MAC address from ROM
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
** Unable to read file boot.scr **
** Unable to read file Image **
Booting from net ...
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
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17

Re: Could not initialize PHY ethernet@30be0000

igorpadykov — Sat, 08 Feb 2020 13:54:03 GMT

Hi Iñigo

one can check with oscilloscope enet clock in uboot function setup_fec()

imx8mm_evk.c\imx8mm_evk\freescale\board - uboot-imx - i.MX U-Boot

Description can be found in sect.8.2.4.2 General Purpose Register 1 (IOMUXC_GPR_GPR1)

i.MX8M Mini Reference Manual.

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: Could not initialize PHY ethernet@30be0000

inigovicentewal — Tue, 11 Feb 2020 08:45:51 GMT

Hi igorpadykov‌

I already solved my problem, thanks

Another question, Do you know if the OP-TEE project is integrated in L4.14.98_2.0.0_ga_images_MX8MMEVK?

It's right?

TFA is also activated? If not, how can I do it?

Re: Could not initialize PHY ethernet@30be0000

jrtigerlee — Tue, 18 Aug 2020 21:55:56 GMT

Hi Iñigo,

How did you fix the PH initialize issue?
Can you share your experience?

Re: Could not initialize PHY ethernet@30be0000

inigovicentewal — Mon, 24 Aug 2020 11:15:18 GMT

Hi,

It is because the image is badly flashed

I used version L4.19.35_1.1.0_images_MX8MMEVK and I did not get that problem