I have found weird things like that is often the cache. Put a break point in the code where you are checking if the packet has been received in the GMAC and see if the cache is enabled. It most likely is.
When you do the debug prints it has to load data from other memory locations which can force the cache to be flushed on the GMAC DMA buffer and then things seem to magically work. Trampas On Wed, Nov 6, 2019 at 8:42 AM vinu <vinu.gopalakrish...@gadgeon.com> wrote: > Sorry Trampas, i cant share my codebase, but can send you the config files > or > snippets. > Another finding is that when i enable the debug prints of the stack, i dont > see the issue. I guess its something related to timing. > > > > -- > Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html > > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
