hello 

i started testing the tcpip example from 
mspgcc CVS (mspgcc/msp430-libc/examples/tcpip/*)

i've seen that victor antonovich applied a patch to fix
FIN_TIMEOUT handling...

but i think that there are still some problems left...

if i connect the device to internet i can happen that the
tcp-layer "hang up" -> you never can connect again

it seems that the layers below tcp are still working -> ping is working fine

what i found out till now:

the http server sent the page and has called tcpclose()
now the MSP runs in the mainloop and is calling DoNetworkstuff() again and again
normally the SocketStatus get rid of the active bit so that the mainloop
can do a TcpPassiveOpen again

the problem is that the SocketStatus (after TcpClose) stays unchanged for ever

i added some debug output a got these infos:

SockStatus = 0x0B      : ACTIVE + CONNECTED + TX_BUF_RELEASED
TCPStateMachine = 0x06 : FIN_WAIT_2
TCPFlags = 0x18        : TCP_CLOSE_REQUESTED + TIMER_TYPE_RETRY

these variables stay unchanged for ever...

has anybody some experience with this application or some ideas where
the problem could be ?

i'm trying to find out more - maybe i have to wait some hours again :-)

thanks for your help
matthias





Reply via email to