You are debugging an embedded application on an embedded system. The usual techniques for debugging embedded applications on embedded systems still apply. If you can't use a UART to log messages, you can surely use Cortex-M's SWD or put breakpoints or use any other debugging resources you surely reserved for your application at design time. lwIP provides statistics you can enable to be compiled in. You should check them for memory loss and things like that. Is there any reason why you are using lwIP 1.3.2 ? I know 1.4.1 is stable and git head seems to be rock solid, but I can't bet on 1.3.2 and don't know if anyone here (besides the maintainers) will be able to help you in case you do find something that is lwIP's fault. I would check your driver and port if I was in your shoes.
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
