Usually the driver asks for PBUF_POOL, while TCP takes from PBUF_RAM.
Whatever you free in rx callbacks shouldn't mess with tx since they use
different areas.
PBUF_POOL is allocated as memp_malloc(MEMP_PBUF_POOL), which takes
memory from a pool of pbufs defined in the MEMP_ are of lwipopts
PBUF_RAM
I'll try to answer your questions. No, we haven't talked about this problem.
Yes, all lwip RAW API functions are being called from the same context
(main loop). Nothing called from interrupt.
My driver was written by myself, not vendor supplied. It seems to work
well. It is not interrupt driven,
First things first.
Maybe we've already talked about this, but I don't remember everyone in
the list...
Are you calling all lwIP RAW API functions from the same context ?
Either main loop or interrupts but only one of them and always the same one.
Did you run a known-good application long enough in
Update on the problem below. I added some debug code and enabled
LWIP_STATS. After letting my system run overnight (continuously polling
modbus data) it had finally failed once again. Connection attempts are
usually timing out (even connection attempts to port number with no
listening pcb). Whe
