FreeRTOS info wrote >> why ? and how to check it? > > ...because you said the error was "temac error interrupt: rx fifo over > run". So presumably the driver is using a FIFO to store received > packets, but the rate at which packets have been received was too fast > for the CPU to process, so the FIFO became full and the driver returned > an error. Therefore the problem occurred in the driver, before the > packets were ever sent to lwIP. This is a perfectly legitimate > scenario, and not really an error. If there is no space to store the > packets then the packets will have to be dropped. If the dropped > packets contained TCP data then the TCP protocol will take care of > ensuring they get re-sent. If the dropped packets contained UDP data > then you lucked out - if they need to be re-sent then that has to be > done from the application level. > > Regards, > Richard. > > + http://www.FreeRTOS.org > Designed for microcontrollers. More than 107000 downloads in 2013. > > + http://www.FreeRTOS.org/plus > IoT, Trace, Certification, FAT FS, TCP/IP, Training, and more... > > > > _______________________________________________ > lwip-users mailing list
> lwip-users@ > https://lists.nongnu.org/mailman/listinfo/lwip-users Thanks. a lot of good information. you are right . there's a patch in xilinx site around this issue. http://www.xilinx.com/support/answers/32092.htm -- View this message in context: http://lwip.100.n7.nabble.com/ping-flood-crash-tp23232p23242.html Sent from the lwip-users mailing list archive at Nabble.com. _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
