goldsi...@gmx.de wrote
> nrichard wrote:
>> I have been able to get these all running
>> at the same time using the HEAP? method by setting both MEM_LIBC_MALLOC
>> and
>> MEMP_MEM_MALLOC to 1. However it is not consistent. Sometimes the
>> system
>> tells me "memp_malloc: out of memory in pool
Simon Koudijs | Intellifi wrote
> Hello everyone,
>
> I'm working a project that uses wired Ethernet, lwip is working pretty
> nice there!
>
> Now we would like to start using wifi as well. We are now searching for
> a suitable and cheap wifi module that can be used on the ethernet level.
>
So, I found the problem on my end:
The initialization code was called twice...
The first time when NETIF was UP, the second time when DHCP got an
IP-address... (And the initialization the second time obviously was badly
written and screwed up the list of lpcbs)
I guess this behaved differently
And one more thing:
In our app, when the network starts, the following code is how the
listening is initialized. This was working OK in 1.3.2, but I suspect this
breaks 2.0.2 and could cause the problems I see now. Is this a correct way
to initialize the listening connection, or is this code
One more observation from a debugging session (with n=2) with these settings
#define MEMP_NUM_TCP_PCB2
#define MEMP_NUM_TCP_PCB_LISTEN 2
(Hex numbers are addresses of pcbs or lpcbs)
Two listening lpcb initially:
0xb78c
0xb76c
The first two connections use the following
Hi, Sylvain, I am grateful for your advice and help. I found hardware
problem in my project.
27 июля 2017 г. 19:40 пользователь "Sylvain Rochet"
написал:
Hi Roman,
On Wed, Jul 26, 2017 at 06:08:55AM -0700, Roman wrote:
> Hi, lwip. I still can't solve my problem, it has
On 3 August 2017 at 21:16, goldsi...@gmx.de wrote:
> Tony wrote:
>
>> The aim is to only allow n open TCP connection at a time, and reject all
>> further connection requests. This worked reasonably well in 1.3.2, but now
>> fails in 2.0.2.
>> [..]
>> HOWEVER: this n+1