Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-15 Thread jbhoi
@Sergio R. Caprile I think you are right, i haven't check buffer in tcp/udp call back. Now i am free the buffer in call back and it's working longer. Will let you know after more testing. Thanks -- View this message in context:

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-15 Thread Slava Zilberfayn
Hello, I'm having some issues with lwip stack, or rather with the system as whole. At this point I studied the stack relatively well at seems to work as intended. However I might be still mistaken, so I'm posting here. The root of the problems is that sometimes packets are being lost for no

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-15 Thread Slava Zilberfayn
Hello Slava, Hm, the driver was missing error handling, naturally the missing packets returned some error. Looking further... Regards, Slava Wednesday, October 15, 2014, 3:54:16 PM, you wrote: SZ Hello, SZ I'm having some issues with lwip stack, or rather with the system as SZ whole. At this

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-15 Thread Vincent Cui
] On Behalf Of Slava Zilberfayn Sent: 2014年10月16日 10:34 To: Mailing list for lwIP users Subject: Re: [lwip-users] pbuf_alloc failed after sometime at driver side. Hello Slava, Hm, the driver was missing error handling, naturally the missing packets returned some error. Looking further... Regards

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-14 Thread Sergio R. Caprile
Isn't the stack responsible for freeing PBUFs? No Grzegorz, the stack isn't more responsible than you are. The Ethernet driver usually allocates the pbufs when signalled by the Ethernet controller. This code does not belong to lwIP but to the driver developer. It is responsible for freeing

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-11 Thread jbhoi
I don't think the issue related to the driver because driver have pass after checking the eth type of the pakcet it pass to the upper layer stack. And now upper laye stack have resposibilty to free this packat after it no longer in use. Here peace of drive code /* move received packet

[lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-10 Thread jbhoi
I am using lwip 1.4.1 for lpc1833 microcontroller with freeRTOS version 7.3.0.Have used driver for lpc18xx_43xx family http://docs.lpcware.com/lpcopen/v1.03/lpc18xx__43xx__emac_8c.html http://docs.lpcware.com/lpcopen/v1.03/lpc18xx__43xx__emac_8c.html I am successfully able to up and run the

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-10 Thread TJO
Hi, I had the same problem in my lpc1788. When I ran it on the companies local network it was just a couple of minutes before it halted. On a closed network it ran like forever! I fixed it by increasing the mem size so I had space enough for allocation. So I had to move it from internal PIRAM

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-10 Thread jbhoi
Thanks for replying @Thomas But my device have limited memory. I am able to use 16K memory so have defined it #define MEM_SIZE(16 * 1024). Also my lwip not crashes but just lost the ping from other device. Any other way to overcome this issue? Can we force the upper

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-10 Thread Sergio R. Caprile
Please don't repost the same issue with a different name... Check your driver code, from what the other user said, looks like non-IP packets are being discarded without freeing their buffer. Check with the one who wrote the driver and/or the port. When the Ethernet controller signals frame(s)

Re: [lwip-users] pbuf_alloc failed after sometime at driver side.

2014-10-10 Thread Grzegorz Niemirowski
Sergio R. Caprile scapr...@gmail.com napisał(a): Please don't repost the same issue with a different name... Check your driver code, from what the other user said, looks like non-IP packets are being discarded without freeing their buffer. Check with the one who wrote the driver and/or the port.