But the issue was not seen with the lwip 1.4 version which points towards the posibility of something wrong with the newer version of stack or some optimisation issues of the lwipopts
On Mon, Feb 25, 2019, 21:25 Sergio R. Caprile <[email protected]> wrote: > Yes, I remember analyzing your capture file about 15 days ago and > pointing to that possibility. Glad it was a hit. > > "lpc_low_level_output" is not something related to lwIP, it is your > vendor driver code. Ask your vendor. > > Want to find it yourself ? Great! Then grab a debugger and place > breakpoints in the driver until you get it. You can write a small > application that just tries to send lots of data or just work on the > driver alone (without lwIP). My advice is to work on just the driver. > > The output function of the driver is a piece of software that takes what > will go in the Ethernet payload (prepared by lwIP) and sends it to the > Ethernet hardware. It should be simple, unless it is DMA driven, in > which case it is a bit more complicated. Good luck, I suggest you try > asking for help in your vendor forum anyway. > > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
