Hi, thank you all for your posts.
- yes, using NO_SYS = 0.
- yes, using multithreading. I´m sure, the calling of lwip_thread is only
from one location. In other threads is used netconn api for bind or listen
sockets.
- port is made by Giovanni Di Sirio(I think), the author of ChibiOs. How
much
on behalf of Sergio R.
Caprile
Sent: Fri 6/20/2014 10:03 PM
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] [LwIP-1.4.1 + ChibiOS-2.6 + STM32F407]memp_malloc:
out of memory in pool PBUF_POOL
Hi,
I will guess:
- Since you describe something ending with 'OS', you are using an (RT)OS
port, probably
Hi everyone,
I am still getting hard error on memp_malloc after not null check.
Statistic writes this error: memp_malloc: out of memory in pool
PBUF_POOL, despite MEM PBUF_POOL: avail: 20, used 4, max 8.
Then tcpip stack stops receive anything. The call to memp_malloc is when
pbuf_malloc tries
Hi,
I will guess:
- Since you describe something ending with 'OS', you are using an (RT)OS
port, probably with NO_SYS = 0.
-- If you have multiple tasks, check you call lwIP only from one task
(unless you know exactly what you do and why you are doing it). This
includes the netif input.
-- Who did
