Hi Simon, Maybe I am wrong, it was 4-5 years ago :-).
As far as I remember communication stopped and maybe it crashed or not this is not the issue. The issue is that once I set my defines as suggested this problem was never happened again. >From what I understand every connection has a new PCB and a pBuf that holds >the received data. if the system does do not have sufficient buffers but have sufficient PCB's this causes an abnormal behavior. I do not remember if that was a problem with version 1.32 or also in 1.41 as I upgraded at some time. BR, Noam. -----Original Message----- From: lwip-users [mailto:lwip-users-bounces+noam=silrd....@nongnu.org] On Behalf Of Simon Goldschmidt Sent: Tuesday, November 29, 2016 11:26 AM To: lwip-users@nongnu.org Subject: Re: [lwip-users] lwIP with FreeRTOS memory problem Noam Weissman wrote: > Several years ago when I started working with LwIP I had a similar problems > to the one you raised. > System was working ok but out of the blue it crashed. > [..] > I found the hard way that I am getting MEM_ERR because of the above. I > did not had sufficient MEMP_NUM_TCP_SEG defined. After changing the above to > what it is now those issues were solved. How would your system crash because of insufficient tcp segment pool elements? You could get communication hiccups, but it shouldn't crash! Simon _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users