The crashes are your responsibility. Or your vendor's...
If you clearly indicate which API are you using and how you use the
stack, someone here might guide you.
The dup acks are indicating your lwIP is not seeing some expected
frames. This is usually a driver fault. Most common culprit is that
Thank You for Your response.
So I'm using the lwip 1.4.1 stack. To configure my controller I used the
CubeMx from ST. The Cube Mx generated this library to my project (in
2016). I read that the ST is working on next upgrade of Cube Mx that
will contain the lwip 2.0.
The problem is that my pr
Hi
Which version of CubeMx? And are you using their ethernetif.c or did you
get it somewhere else? I don't remember when it was fixed but old
versions had the exact problem Sergio mentioned. Search for anything
related to ST from a couple of years ago and you'll definitely find it
BR /Jens
What your vendor offers belongs to your vendor, you should ask them for
support.
lwIP has several APIs, most of us can only help at the API level;
although if you are lucky you'll find a fellow advocate who can guide
you through your vendor nightmare. I still think your vendor's forums
are a be
Thanks for the update, vendors are really thriving these days.
And to answer your question (sorry I'm late, but I was not checking the
list these days), assertions usually mean something has gone out of
bounds. In this case, it is informing you that a function was trying to
free an already fre
