U-boot and ping commands

U-boot and ping commands

The Development Board runs U-boot. The ping command on the terminal can be used to ping the PC, but the PC can ping different U-boot.

When developing an Ethernet Driver Under U-boo, you can only ping the external host on the target to check whether the Ethernet is connected. If you ping the target board on the external host, the Ping fails even if all Ethernet entries on the target board are OK. This is because the Row U-boo is a single-thread main_loop Function + interrupt processing architecture, Interrupt ProcessingProgramProcessing serial port input and output, main_loop parses the U-boot command, and no other task accepts and processes ICMP packets, even if u-boot supports the ICMP protocol stack.

The Ping of U-boot sends and accepts ARP packets through a netloop! Loop constantly checks whether ARP reply is received. Therefore, you can ping the PC. However, in the U-boot mode, it is a single thread and will not always stop there to check for ARP. The premise for PC ping to U-boot is that U-boot has a daemon process similar to ARP request response.