Sandra Gilge (ADATIS) wrote:
there is following line in cc.h:
extern u8_t memp_memory_PBUF_POOL_base[] __attribute__ ((aligned (32)));
I checked the address of memp_memory_PBUF_POOL_base it is 32byte aligned
That might not be enough. With this, you only have ensured the PBUF_POOL
memory
Patel wrote:
[..]
and that is when I get:
Assertion "dhcp_create_msg: dhcp->p_out == NULL" failed at line 1774 in
src/core/ipv4/dhcp.c
Assertion "dhcp_create_msg: dhcp->msg_out == NULL" failed at line 1775 in
src/core/ipv4/dhcp.c
In 2.0.0, there are no asserts on those l
The assertion in function: dhcp_create_msg line 1795, my assertion line code
may be off, but I have debugged it down to that. That line is in lwip 2.0.1
and lwip2.0.0RC2, I am using lwip2.0.0RC2.
Thanks
From: lwip-users
Freddie Chopin wrote:
[..]
Is there any other way than direct messing
with the tcp_pcb to set SOF_REUSEADDR in the so_options field? Maybe
I'm doing something wrong here (except force-closing the client
connections (; )?
In "specialities" like this one, the netconn API is (unfortunately)
Sandra,
I'm afraid problems like yours happend often in the past and only seldom
there has actually been a problem in lwIP. Most of the time, it's wrong
usage of lwIP (by the lwIP port).
Now I don't know the zero copy driver from Stephane, but zero copy
imposes some special requirements on
Hi again
I had a read through the pitfalls page, but still am a bit confused.
So what I have done is the following, in my own robot.c file, I have done the
following:
static struct udp_pcb *robot_pcb = NULL;
static void
robot_receive( void *arg, struct udp_pcb *pcb, struct pbuf *p,
Hello!
Currently in a project with lwIP I'm facing an issue with closing
netconns and I failed to find a solution by myself, so I'm writing here
in hope for some guidance.
Let's say that there are 5 listening netconns, each bound to a
different port, let's say 1001-1005. I'm accepting 5
If you want to send and receive on the same socket from two different threads,
you’ll need to enable LWIP_NETCONN_FULLDUPLEX in opt.h (by default it’s not
supported and feature is in alpha state):
/** LWIP_NETCONN_FULLDUPLEX==1: Enable code that allows reading from one thread,
* writing from a
