net: smsc95xx: ARP Retry count exceeded problem

Lars Michael lh_post at yahoo.com
Wed Jan 12 09:47:27 CET 2022


Using the smsc95xx ethernet interface for ping/tftp fails with:
"ARP Retry count exceeded; starting again".
U-Boot version: 2021.10+fslc+ge6310a598d
The driver works on the same hardware running U-Boot 2015.07+fslc+g3f0c535.
The board is a custom i.MX6 with two ethernet ports. The primary is usingthe imx fec, the secondary is provided by the LAN9512.
defconfig:CONFIG_USB_HOST=yCONFIG_USB_EHCI_HCD=yCONFIG_USB_EHCI_MX6=yCONFIG_USB_ETHER_SMSC95XX=yCONFIG_USB_HOST_ETHER=y
With DEBUG enabled I get this output, ending in the ARP timeout.The driver appears to load ok, and the correct MAC is used.
<START>
starting USB...Bus usb at 2184000: USB EHCI 1.00Bus usb at 2184200: USB EHCI 1.00scanning bus usb at 2184000 for devices... 3 USB Device(s) foundscanning bus usb at 2184200 for devices... 1 USB Device(s) found       scanning usb for storage devices... 0 Storage Device(s) found       scanning usb for ethernet devices... 
USB Ethernet device detectedEndpoints In 1 Out 2 Int 3** smsc95xx_eth_get_info()** smsc95xx_write_hwaddr_common()MAC 00:50:55:01:28:e21 Ethernet Device(s) found
=> ping 192.168.42.100** smsc95xx_init_common()** smsc95xx_write_hwaddr_common()MAC 00:50:55:01:28:e2rx_urb_size=2560Read Value from BURST_CAP after writing: 0x00000005Read Value from BULK_IN_DLY after writing: 0x00002000Read Value from HW_CFG: 0x00000000Read Value from HW_CFG after writing: 0x00000022ID_REV = 0xec000002LED_GPIO_CFG setCOE_CR = 0x00000000phy initialised succesfullyWaiting for Ethernet connection... done.Using sms0 device** smsc95xx_send_common(), len 42, buf 0x4f569700Tx: len = 50, actual = 50, err = 0** smsc95xx_recv()Rx: len = 2560, actual = 0, err = 0** smsc95xx_recv()Rx: len = 2560, actual = 0, err = 0** smsc95xx_recv()<CUT>** smsc95xx_recv()Rx: len = 2560, actual = 0, err = 0
ARP Retry count exceeded; starting again** smsc95xx_recv()Rx: len = 2560, actual = 0, err = 0** smsc95xx_halt()ping failed; host 192.168.42.100 is not alive<END>
Can someone confirm that the driver works with the latest u-boot?
Am i missing something in my configuration? Help is appreciated.
Thanks- Lars



More information about the U-Boot mailing list