[En-Nut-Discussion] TCP/IP Stack crashes

Harald Kipp harald.kipp at egnite.de
Wed Jan 11 12:01:52 CET 2006


At 11:46 11.01.2006 +0100, you wrote:

>So for me it looks like especially the LAN91C111 has the problem, not the
>Realtek.

I see. Well, I still don't think that the controller is the problem.
But that's not based on any facts. :-)


> > real trouble. I'd suggest to open stdout on devDebug and
> > insert printf() statements in the hole Ethernet receive chain.
>Hm, I will try it, but what would make sense to monitor. I think I would run
>into problems if I send some debug infos on every received interrupt,
>because the Uart is much slower than the Ethernet, so I would break down the
>receiver routines by the Uart output.

Right, sometimes the delay caused by the debug output eliminates the
initial trouble. But sometimes it does the opposite, so you have to
try it. 115.2 kBaud is quite fast.

If Ethernut is not responding, I'd suggest to check the receiver
path first. Start in front of

   NutEventWait(&ni->ni_rx_rdy, 2000);

in THREAD(NicRxLanc, arg). Then add an output to NutEtherInput(),
NutIpInput() and so on. You may use a simple putchar() first to
minimize the impact of the debug output and add a more advanced
printf() later.

Harald




More information about the En-Nut-Discussion mailing list