nobody wrote on Tuesday, April 04, 2006:
> I’m using the lwip demo for rowley from the commandline. I integrated a fat
> filesytem and read out a sdcard located on the spi. Using the at91sam7x-ek board
> with the at91sam7x256.
Cool. Which file system are you using?
> The problem I encouter is that after receiving a couple of packages the controller
> starts sending RST,ACK packages sometimes just a few and sometimes blocks of
> 5 or 6 RST,ACK packages.
Don’t know too much about TCP/IP but there is an lwIP mail list that may be able to point to some possible sources of this.
>And eventualy the webserver task dies. I’m still able
> to ping the webserver and the errorchecktask stays alive. I removed the usb
> and flash task.
> Any suggestions?
Normally the first answer on this forum is "check the stack depths", but I think in this case the lwIP demo allocates quite large stacks to the lwIP related tasks. May be worth a look anyway, especially if your file system uses calls to C routines such as string handlers, etc that use a lot of stack.
I think the pings are handled by the lwIP stack task directly, whereas new connections require allocation of memory for various features that persist with the connection. If the pings are working but the TCP/IP connections are not then maybe there is a problem with the allocation of memory for new connections or freeing of memory for old connections?
It might be worth getting an updated version of the lwIP code?
A few posts ago there was a thread about the function that creates the buffer of task information not being ideal for real applications also. Maybe try taking this out of the demo.