Hello:
I've created my own local IP address in S32DS and disabled the local IP address in the LWIP protocol stack, but I get an error during single-step debugging, failing to establish a connection, as shown in the bottom right image above. What could be the problem? Is some setting missing? Is it that creating a local IP address is not allowed and must be configured in the protocol stack?
Thank you again for taking the time to reply despite your busy schedule!
Hello @sunshine88 ,
The IPv4 address itself is not the cause of this error. lwIP allows a static IPv4 address to be provided directly through netif_add().
According to the debugger screenshot, netif_add() returns NULL because the network-interface initialization callback, ETHIF_INIT, does not return ERR_OK. Therefore, the failure occurs during initialization of the Ethernet interface or its lower-level driver, before the interface can be added to lwIP.
In your TCP/IP Stack configuration screenshot, the Enable iface option is not selected. Please enable the network interface and configure the required static IPv4 address, subnet mask, and gateway there. Then regenerate the configuration and use the initialization sequence from the corresponding S32K3 lwIP example.
If you still want to assign the address in the application, please first verify whether netif_add()succeeds.
Please note that this only makes the initialization failure easier to detect. It does not correct the underlying GMAC/Ethernet configuration.
I recommend first building and running the original lwIP example for your exact S32K3 device and software-package versions without modifying its network initialization. Once the original example works, change only the static IPv4 address and confirm the result.
Please also provide the following information if the initialization still fails:
- Exact S32K3 device and evaluation board
- S32 Design Studio version
- RTD and TCP/IP Stack package versions
- The definition of
ETHIF_INITand the error returned by that function - Whether the unmodified lwIP example works on the same hardware
It appears that the same question was submitted in three separate Community posts. To keep the troubleshooting information in one place, please continue the discussion in only one of them.
Best regads,
Pavel