imx8mp eqos not working in uboot

[JasonShu]

Hi All NXP Technical Team

1. The device information can be displayed, but cannot ping the network.

2. Using a direct connection method, the PC shows that the network is not recognized.

3. How should I investigate next?

Spoiler

u-boot=> mii dump 1
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)

u-boot=> ping 192.168.1.3
phy_connect
get_phy_id
phy_device_create
phy_id is 536894608
phy_config
genphy_config_aneg
result is 1
phy_startup
dp83848_startup
ethernet@30bf0000 Waiting for PHY auto negotiation to complete..... done
Using ethernet@30bf0000 device

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

Best Regards

Jason

[JosephAtNXP]

Hi,

Thank you for your interest in NXP Semiconductor products,

Are you using EVK? I can't replicate, please try the following:

u-boot=> pri ethact
ethact=ethernet@30bf0000
u-boot=> setenv ipaddr <Our IP>
u-boot=> setenv serverip <Host IP>
u-boot=> ping $serverip
ethernet@30bf0000 Waiting for PHY auto negotiation to complete....... done
Using ethernet@30bf0000 device
host <Host IP> is alive

When the IP does not exist it says:

u-boot=> ping <NOT Host IP>
Using ethernet@30bf0000 device

ARP Retry count exceeded; starting again
ping failed; host <NOT Host IP> is not alive

So, make sure your Host IP does exist, is within the same network (works under 255.255.255.0) and there are not firewall issues with your router.

For further debug try with:

u-boot=> mii device
MII devices: 'FEC0' 'ethernet@30bf0000'
Current device: 'FEC0'
u-boot=> mii device ethernet@30bf0000
u-boot=> mii dump 1
1.     (79ad)                 -- PHY status register --
  (8000:0000) 1.15    =     0     100BASE-T4 able
  (4000:4000) 1.14    =     1     100BASE-X  full duplex able
  (2000:2000) 1.13    =     1     100BASE-X  half duplex able
  (1000:1000) 1.12    =     1     10 Mbps    full duplex able
  (0800:0800) 1.11    =     1     10 Mbps    half duplex able
  (0400:0000) 1.10    =     0     100BASE-T2 full duplex able
  (0200:0000) 1. 9    =     0     100BASE-T2 half duplex able
  (0100:0100) 1. 8    =     1     extended status
  (0080:0080) 1. 7    =     1     (reserved)
  (0040:0000) 1. 6    =     0     MF preamble suppression
  (0020:0020) 1. 5    =     1     A/N complete
  (0010:0000) 1. 4    =     0     remote fault
  (0008:0008) 1. 3    =     1     A/N able
  (0004:0004) 1. 2    =     1     link status
  (0002:0000) 1. 1    =     0     jabber detect
  (0001:0001) 1. 0    =     1     extended capabilities

Which seems like there is a link status on your side.

Regards

[JasonShu]

Hi, 
I am using EVK.I have set up the IP and server IP , but I still cannot ping them. The “pri ” as following:

Spoiler

u-boot=> pri
baudrate=115200
board_name=EVK
board_rev=iMX8MP
boot_fit=no
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else if run loadimage; then run mmcboot; else run netboot; fi; fi; fi;
bootcmd_mfg=run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; fi;
bootdelay=2
bootscript=echo Running bootscript from mmc ...; source
console=ttymxc1,115200
disable_giga=1
emmc_dev=2
eth1addr=00:0a:35:01:fe:c0
ethact=ethernet@30bf0000
ethaddr=64:00:F1:11:22:33
ethprime=eth1
fastboot_dev=mmc2
fdt_addr=0x43000000
fdt_file=imx8mp-evk.dtb
fdt_high=0xffffffffffffffff
fdtcontroladdr=bcbf75f8
gatewayip=192.168.0.1
image=Image
initrd_addr=0x43800000
initrd_high=0xffffffffffffffff
ipaddr=192.168.0.2
jh_clk=
jh_mmcboot=setenv fdt_file imx8mp-evk-root.dtb;setenv jh_clk clk_ignore_unused; if run loadimage; then run mmcboot; else run jh_netboot; fi;
jh_netboot=setenv fdt_file imx8mp-evk-root.dtb; setenv jh_clk clk_ignore_unused; run netboot;
kboot=booti
loadaddr=0x40480000
loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}
mfgtool_args=setenv bootargs console=${console},${baudrate} rdinit=/linuxrc clk_ignore_unused
mmcargs=setenv bootargs ${jh_clk} console=${console} root=${mmcroot}
mmcautodetect=yes
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${boot_fit} = yes || test ${boot_fit} = try; then bootm ${loadaddr}; else if run loadfdt; then booti ${loadaddr} - ${fdt_addr}; else echo WARN: Cannot load the DT; fi; fi;
mmcdev=2
mmcpart=1
mmcroot=/dev/mmcblk2p2 rootwait rw
nandfit_part=yes
netargs=setenv bootargs ${jh_clk} console=${console} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${loadaddr} ${image}; if test ${boot_fit} = yes || test ${boot_fit} = try; then bootm ${loadaddr}; else if ${get_cmd} ${fdt_addr} ${fdt_file}; then booti ${loadaddr} - ${fdt_addr}; else echo WARN: Cannot load the DT; fi; fi;
netmask=255.255.255.0
script=boot.scr
sd_dev=1
serial#=1f1ca800a8030e3a
serverip=192.168.0.3
soc_type=imx8mp
splashimage=0x50000000

Environment size: 2458/4092 bytes

ping 192.168.0.3：

Spoiler

u-boot=> ping 192.168.0.3
phy_connect
get_phy_id
phy_device_create
phy_id is 536894608
phy_config
genphy_config_aneg
result is 1
phy_startup
dp83848_startup
ethernet@30bf0000 Waiting for PHY auto negotiation to complete.... done
Using ethernet@30bf0000 device

ARP Retry count exceeded; starting again
ping failed; host 192.168.0.3 is not alive
u-boot=>

I used packet capture software and found that host ip cannot detect the gateway

Spoiler

417 612.352265 WistronI_87:91:e1 Broadcast ARP 42 Who has 192.168.0.1? Tell 192.168.0.3

Regards

[JosephAtNXP]

Hi,

Seems like a network configuration, what happens when you directly ping a Own Host through static IP?

Have you tried to acquire a DHCP with => dhcp?

Regards,