Thanks for your reply Simon. That would be the eth_drv.c/.h which is the port for Ecos did u mean that file? but could it also be the Ethernet Driver? I have the AT91RM9200 Controller and got a ecos driver for it which i tought worked properly because of the reason that i can ping it and the raw api works on it.
Option 2: I also tried the port from LWIP 1.3.2 from the latest ecos CVS on my Ecos 2.0 but there the function tcpip_init_done never returns so it never initialize the lwip stack. What could be the problem? What would be your advise? try to get the newer port working where i dont get any initialization or try to work on the old stack and fix the threading problem? Simon Goldschmidt wrote: > > Fred39 <[email protected]> wrote: >> i am using Ecos 2.x with the lwip Port of Ecos 3.0. The Lwip Stack >> version >> is 1.1.1 last changelog is 2009-03-12 splipif. > > That's a least strange: lwIP 1.1.1 is from Jan-2005! > > As to the netconn problem, it sounds like threading doesn't work > correctly, which would be a problem in the Ecos port... > > Simon > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users > > -- View this message in context: http://old.nabble.com/LWIP-1.1.1-on-Ecos-Raw-api-works-but-Netconn-Api-not--tp33938020p33939898.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
