mbox.err is used in the OS-interface layer only. My implementation
(FreeRTOS) increments it if sending a message fails or if the mailbox is
not empty when deleted.
Jan
On 08.08.2017 10:58, Mohsin Madki wrote:
> SYS
> sem.used: 6
> sem.max: 11
> sem.err: 0
> mutex.used: 0
>
SYS
sem.used: 6
sem.max: 11
sem.err: 0
mutex.used: 0
mutex.max: 0
mutex.err: 0
mbox.used: 6
mbox.max: 11
mbox.err: 1
what is mbox.err?
On Tue, Aug 8, 2017 at 2:14 PM, Mohsin Madki wrote:
> here is the data got from lwip_stats when ethernet stopped working.
>
here is the data got from lwip_stats when ethernet stopped working.
LINK
xmit: 0
recv: 0
fw: 0
drop: 0
chkerr: 0
lenerr: 0
memerr: 0
rterr: 0
proterr: 0
opterr: 0
err: 0
cachehit: 0
ETHARP
xmit: 10
recv: 5291
fw: 0
drop: 5
chkerr: 0
lenerr: 0
memerr: 0
rterr: 0
proterr: 5
opterr: 0
err: 0
Thanks Simon,
I mean rest of the processes are working but only ethernet related
functions stops working.
It's my first project with LwIP so dont know from where to start debug.
Now as you suggested I'll try to get data from lwip_stats first.
Thanks again.
On Tue, Aug 8, 2017 at 10:02 AM, Simon
Mohsin Madki wrote:
> can anybody reply to this email.
That's hard. First, I don't know what "stops working" means. Then: no way to
tell from here. Get a debugger and start searching what's wrong. "lwip_stats"
might help you.
Simon
___
lwip-users
can anybody reply to this email.
On Fri, Aug 4, 2017 at 10:10 AM, Mohsin Madki wrote:
> Hi,
>
> I am using STM32F107 with FreeRTOS+LWIP with Netconn APIs.
>
> I have created 4 tcp ports (server in listening mode) and trasfers data
> received to UARTS and viseversa. i.e.
and TCP related defines :
/* -- TCP options -- */
#define LWIP_TCP1
#define TCP_TTL 255
/* Controls if TCP should queue segments that arrive out of
order. Define to 0 if your device is low on memory. */
#define TCP_QUEUE_OOSEQ 0
/* TCP