Is this a commercial development board or home brew?Īssuming the PHY section has been implemented correctly and is functional, I would recommend using one of the example codes for the STM32CubeF1 as a template, rather than rely on the graphical wizard to generate the necessary header files. What is the PHY target device you are using to complete the implementation of the Ethernet connection? LwIP TCP/IP stack demonstration for STM32F107xx (AN3102)Įither way, there are typically header files which contain the macros which enable/disable various features or options within the LwIP library, you need to ensure the proper settings are enabled within these option header files, to enable the ICMP and its associated Echo Reply Message.
#Lwip loopback cable code
If you are NOT using the STM32CubeFx library package in your application, then reviewing the following example code of a LwIP implementation may yield the answers you seek:
#Lwip loopback cable series
Typically, the STM32CubeFx example codes, specific to the actual device series utilized in your design, offers one or more LwIP example applications which can be utilized as a template for your specific project. If you are using the STM32CubeFx library package in your application: The STM32CubeMx is a tool, primarily for the development of graphical user interfaces (GUIs), I suspect you are more specifically referring to the STMCubeFx library packages.Īs you have not specified the device you've employed in your design, my advice is thus somewhat limited. * When the netif link is down this function must be called */ * When the netif is fully configured this function must be called */ * Registers the default network interface */ Netif_add(&gnetif, &ipaddr, &netmask, &gw, NULL, ðernetif_init, ðernet_input) IP4_ADDR(&gw, GATEWAY_ADDRESS, GATEWAY_ADDRESS, GATEWAY_ADDRESS, GATEWAY_ADDRESS) IP4_ADDR(&netmask, NETMASK_ADDRESS, NETMASK_ADDRESS, NETMASK_ADDRESS, NETMASK_ADDRESS)
IP4_ADDR(&ipaddr, IP_ADDRESS, IP_ADDRESS, IP_ADDRESS, IP_ADDRESS) GET / HTTP/1.1\r\nUser-Agent: Mozilla/4.0 (compatible MSIE 6.0 Windows NT 5.1 SV1.
In that case, as the server isn't responding properly, could it be something with the HTTP header?
#Lwip loopback cable full
Tcpdump: verbose output suppressed, use -v or -vv for full protocol decode