compulab uboot eth0 on eval board doesn't work

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

compulab uboot eth0 on eval board doesn't work

829 Views
thepnimit
Contributor III

Hi,

I use compulab evalboard cl-som-imx8x, On uboot by default set eth1 prime when I load dtb and kernel from tftp it no problem.

But when I change prime to eth0 it can not use

setenv ethprime eth0
setenv ethact ethernet@5b040000

saveenv

U-Boot 2018.03-imx_v2018.03_4.14.98_2.0.0_ga+g87a19df (Nov 20 2019 - 12:16:16 +0000)

CPU: Freescale i.MX8QXP revB A35 at 1200 MHz
Model: CompuLab CL-SOM-iMX8X
Board: CompuLab CL-SOM-IMX8X
Boot: FLEXSPI
DRAM: 2 GiB
MAC from EEPROM: 01:00:FF:FF:FF:FF
No MAC address found for primary NIC
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from SPI Flash... SF: Detected w25q16cl with page size 256 Bytes, erase size 4 KiB, total 2 MiB
OK
[pcie_ctrlb_sata_phy_init_rc] LNK DOWN 8600000
In: serial
Out: serial
Err: serial

BuildInfo:
- SCFW cb6f758b, SECO-FW 92ef1143, IMX-MKIMAGE dd023400, ATF 1cb68fa
- U-Boot 2018.03-imx_v2018.03_4.14.98_2.0.0_ga+g87a19df

flash target is MMC:0
Net:
Warning: ethernet@5b040000 (eth0) using random MAC address - 16:89:6e:97:26:5d
eth0: ethernet@5b040000 [PRIME]
Warning: ethernet@5b050000 (eth1) using random MAC address - 8a:d7:52:74:2a:e2
, eth1: ethernet@5b050000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
=> setenv serverip 192.168.60.90; setenv ipaddr 192.168.60.252
=> ping 192.168.60.90
ethernet@5b040000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@5b040000
Using ethernet@5b040000 device

ARP Retry count exceeded; starting again
ping failed; host 192.168.60.90 is not alive

For the LED on RJ45 port green and orange working both and when boot to linux it can use eth0 and eth1 no problem.

May it have problem with code or config in uboot?

0 Kudos
1 Reply

709 Views
diegoadrian
NXP Employee
NXP Employee

Hello,

Unfortunately, we cannot give you support from this product since you are using a device that is still in pre-production and you are using a third party board. What I suggest to you, is to go with the third party that sold you the board.

I apologize for the inconvenience this may give you.

Best regards,

Diego.

0 Kudos