Your "HTTP example for the SAM4E xplained pro board" has a layer-2
driver for the Ethernet controller, a port for the environment (be it
bare metal or OS: NO_SYS=?), the lwIP stack (version ?), the httpd
server (RAW API or netconn, is it lwIP's ?), the example itself (which
should be a safe bunch of html files but might have CGIs...), plus, your
debugging output is using some form of printf(), which is provided by
your environment.
I suggest you check with the ones who put that thing together, the ones
here who do things as recommended enjoy the good work of the lwIP
developers and debug on many platforms; check if that people payed
attention to the rules of single threading for low-level functions, it
is one of the most common mistakes. Check how your port tries to output
debugging info also, that might cause lots of bottlenecks leading to who
knows what if they didn't foresee that when they built the port.
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users