Re: [lwip-users] Missed Ethernet Frame

[Sergio R. Caprile]

My best bet is that lwIP is not missing an ethernet frame, but you are.
Your frame enters your chip, goes to your driver and is then sent to
lwIP, which runs in your system (your port of it), then the TCP data (I
guess you are using TCP because you talk about ACKs) is sent to your
application, and your application must tell the stack the data is done
so lwIP can ACK. Let's put this last one aside as it is a bit more involved.
Have you checked between your driver and lwIP ?
Have you checked between your driver and your chip ?
Is your port a good one ? Do you know it works OK ?
BTW, are you running with or without an OS (NO_SYS=?)
Are you honoring the thread-safety recommendations ? That includes not
calling lwIP from main loop and interrupt handler at the same time.

This list has seen lots of reports from people running vendor provided
demos with broken drivers that miss (at least) the second frame on a
burst because they don't poll the chip for more data after an interrupt,
and so on.

Try to be more specific, 1.4.1 runs more than OK, and git HEAD has lots
of bugfixes, you should upgrade anyway, but to me this problem is not
lwIP's.

--