[lwip-users] Lwip 1.4.1 initialization

I am trying to use LwIP for the first time, and am having trouble figuring out what I need to do to properly initialize it. I am trying to run LwIP version 1.4.1 on an STM23F427 Arm processor, but I am NOT using the on-chip ethernet interface. I am using it with a Wiznet W810MJ ethernet module

[lwip-users] Initialization problem upgrading from 1.4.1 to 2.0.3

I am trying to use lwip on ARM cortex M4. My development software is Atollic Truestudio on Win10. So far I have gotten lwip 1.4.1 to work using raw api and a simple multitasking OS. Now I am trying to change over to lwip 2.0.3, and am having trouble with initialization. My initialization code

Re: [lwip-users] Lwip slow received data speed

ented, but those pbufs were not free, and became permanently unavailable for use. I was running out of pbufs! I changed pbuf_chain() to pbuf_cat() in my tcp receive callback, and everything works perfectly. Keith Rubow On 4/15/2018 11:30 AM, Sergio R. Caprile wrote: My best guess for a Sund

[lwip-users] Ethernet frames with extra padding bytes

hat a different Wiznet module padds out all frames to 60 bytes minimum, but is padding with all zero bytes. This module is working fine with LWIP. Keith Rubow ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo

[lwip-users] Problem re-opening listening pbc

l when the close is finished. There is no callback for it, and I am not permitted to access the pcb after calling tcp_close(). So how can I re-open a listening pcb on the port after a connection is closed? Keith Rubow ___ lwip-users mailing list l

Re: [lwip-users] Problem re-opening listening pbc

)? Any help is appreciated. Keith Rubow On 5/9/2018 1:11 PM, Keith Rubow wrote: I'm using LWIP for the first time (2.0.3, NO_SYS=1, callback API). Mostly things are going well. But I have an issue with allowing only a single TCP connection to a port. I open a listening pcb with tc

Re: [lwip-users] Problem re-opening listening pbc

, the question remains why lwip will not allow binding to a port number that has no current listening pcb, but does have one or more open connections. I don't understand why this would cause a problem. Keith Rubow On 5/11/2018 5:51 AM, Sergio R. Caprile wrote: Check this answer:

Re: [lwip-users] Problem re-opening listening pbc

ening pcb until ALL open connections are closed. But some connections might stay open indefinitely, in which case I can never open the listening pcb again. Keith Rubow On 5/12/2018 3:13 AM, Jens Nielsen wrote: Can't you just return an error from the accept callback (or tcp_abort() followed

Re: [lwip-users] Problem re-opening listening pbc

listening pcb again (as in step 2 above) if it is not already open. This exactly what I wanted. Up to "N" connections accepted simultaneously, with excess connection attempts refused. Works great. Keith Rubow On 5/14/2018 11:56 AM, goldsi...@gmx.de wrote: On 14.05.2018 18:27, Keith R

[lwip-users] Is this a memory fragmentation problem

sufficiently large block of memory? Any Ideas would be appreciated. I will try to collect more data to localize the problem, but it takes time. Keith Rubow ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users

Re: [lwip-users] Is this a memory fragmentation problem

ta polling, and then suddenly get into this strange out-of-memory problem? Any suggestions would be appreciated. Keith Rubow On 5/16/2018 11:07 AM, Keith Rubow wrote: I am using lwip 2.0.3, NO_SYS=1, callback api. I have an application that works for a while, then gets into a mode where it s

Re: [lwip-users] Is this a memory fragmentation problem

t of the day) before it fails. I'll post more information when I have anything to report. Keith Rubow On 5/18/2018 6:35 AM, Sergio R. Caprile wrote: First things first. Maybe we've already talked about this, but I don't remember everyone in the list... Are you calling all l

[lwip-users] lwip crashing, apparently in sys_check_timeouts

I am using lwip 2.0.3 with NO_SYS = 1 on a bare metal 386ex processor with a Wiznet IIM7010A ethernet interface operating in MAC RAW mode. Yes, this hardware is REALLY old, but we have lots of hardware out in the field and need to fix a problem, and lwip seems like the best way to fix it. My

[lwip-users] Lwip http server example raw api

Is there no longer an http server example using the raw api for lwip 2.x? I only see one in the contrib-1.4.1, but not in any contrib-2.x. Or does the old httpserver_raw from contrib-1.4.1 still work with lwip 2.0.2? (Not likely, I suspect). ___ lwip