In lwip_stats.tcp I see (non zero values):
- xmit 2478
- recv 2341
but in 'sys.mbox' section:
- used 21
- max 22
- err782
Could you tell me if you see anything incorrect in my opts (maybe any other
opts needed)?
#define TCPIP_MBOX_SIZE 64
#define
Tomek wrote:
but in 'sys.mbox' section:
- used 21
- max 22
- err 782
The meaning of that stats depends on your port. I don't know if it means mbox
full wehn trying to put something in the mbox or no more mboxes left when
creating a new mbox (every socket/netconn needs one).
In the latter
Hi Grzegorz,
let's make this a kickstarter for the FAQ ;^)
single thread applies mostly to raw API users and/or vendor code; they
use an RTOS and the raw API and forget to call the lwIP stack from a
single thread. I've seen some vendor code which also calls the stack
from within interrupt code.
According to the wiki, the correct way to initialize a DHCP interface is
to call dhcp_start() and not netif_set_up(). So, summarizing:
you can poll for netif.dhcp-state == DHCP_BOUND
you can define LWIP_NETIF_STATUS_CALLBACK, and call
void netif_set_status_callback(struct netif *netif,
There is a thread on a guy needing something like source routing last
month, in which Simon discussed some hooks to provide routing.
As far as I can see, you are better off using embedded Linux. Even
though nothing forbids you from runnig RIP or OSPF on top of lwIP and
build a routing table and
Hi Sergio,
thanks for the reply, you are probably talking about the LWIP_HOOK_IP4_ROUTE
and this sounds like a yes to my first question! We do have to implement
our own stack per a customer requirement (even though it will be running on
top of a Linux OS, they have their reasons for that, but
It can be some problem with memory management but there is no place I should
free memory. There are just automatic variables (allocated on stack) and
public variables (allocated on heap). There are also four FreeRTOS queues,
but they are created only once, when one of tasks starts. I don't use
