Re: [lwip-users] Assertion "memp sanity" failed at line463in../lwip_1_4_0/Src/core/memp.c

[Barry Andrews]

Now have this working, thanks for the detailed check list.
I found that I had set the Ethernet Interrupt priority above the maximum
for the critical sections, so it was able to interrupt during a critical
section.
Corrected this and now it has run for over 39 million flood fill pings
without issue.

Once again thanks for the help.

Regards
Barry Andrews

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Artem Pisarenko
Sent: Monday, 19 November 2012 14:52
To: Mailing list for lwIP users
Subject: Re: [lwip-users] Assertion "memp sanity" failed at
line463in../lwip_1_4_0/Src/core/memp.c

> Once again thanks for the detailed response, much appreciated.
I faced with exactly same problems and spent a lot of time to debug it. 
I'm glad to share my experience and save other people from such
nightmares. :)

Additionally I found that pbuf_alloc() call hierarchy contains
sys_mbox_***() calls. It may cause non-***FromISR() calls. Even if your
lwip configuration exclude them, check whether your port do system calls
in LWIP_PLATFORM_DIAG() and LWIP_PLATFORM_ASSERT() which are used in
LWIP_DEBUGF() across all the lwip code.

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users