Hi Maxim,
On Thu, Nov 30, 2023 at 5:39 AM Maxim Uvarov maxim.uvarov@linaro.org wrote:
If networking for some reason doesn't work on that board (I tested only virtual board). Please try to compile with:
Could you also try on a real board?
Tom tested on a Raspberry Pi3 and it failed too:
https://lore.kernel.org/u-boot/20231127185953.GW2513409@bill-the-cat/
CONFIG_LWIP_LIB_DEBUG=y #CONFIG_LWIP_LIB_NOASSERT is not set
It should make network activity more verbose. In many cases I saw issues that physically MAC address do not match to lwip initialized value, and lwip drops such packets.
The ping response with:
CONFIG_LWIP_LIB_DEBUG=y #CONFIG_LWIP_LIB_NOASSERT is not set
u-boot=> ping 192.168.0.16 init already done for eth1 Using eth1 device pinging addr: 192.168.0.16 ping: send 192.168.0.16 ip4_output_if: 0IP header: +-------------------------------+ | 4 | 5 | 0x00 | 60 | (v, hl, tos, len) +-------------------------------+ | 40 |000| 0 | (id, flags, offset) +-------------------------------+ | 255 | 1 | 0x3994 | (ttl, proto, chksum) +-------------------------------+ | 192 | 168 | 0 | 164 | (src) +-------------------------------+ | 192 | 168 | 0 | 16 | (dest) +-------------------------------+ ip4_output_if: call netif->output() etharp_find_entry: found matching entry 0 etharp_query: queued packet 00000000bdf03e70 on ARP entry 0 ping_tmo: ping failed; host 192.168.0.16 is not alive u-boot=>