hi last reply: >I have compiled an example taken from CVS five minutes ago. The >uploaded from board webpage refreshes periodically without any >problems. In my case, board and host system is LAN connected. Maybe >you have some mixed-connections related problems? > >Regards, >Victor.
i started a test again and the problem is still present... it is no problem to reload the webpage 40.000 times (i've tested it)! the problem occurs some hours (2 - 15h) after i connect it to the internet. i guess this happens if the application receives corrupt or faked frames (this happens on i-net..) in this test i added a watch on TrmCtrl, TCPTimer and RetryCounter: TrmCtrl = 0x00 TCPTmr is counting RetryCount = 4 SockStatus = 0x0B : ACTIVE + CONNECTED + TX_BUF_RELEASED TCPStateMachine = 0x06 : FIN_WAIT_2 TCPFlags = 0x18 : TCP_CLOSE_REQUESTED + TIMER_TYPE_RETRY that means that TCP_TIMER_RUNNING isn't set -> no timeouthandling is done -> flags are never cleared !?! so i try to find out where the problem is ... but if someone has an idea or can help me ... please ... thanks, matthias -----Ursprüngliche Nachricht----- Von: Victor Antonovich [mailto:avml...@vlink.ru] Gesendet: Donnerstag, 03. April 2003 22:33 An: Fend, Matthias Betreff: Re: [Mspgcc-users] still problems with timeout in tcpip example Hello, Matthias, Thursday, April 3, 2003, 3:51:47 PM you wrote: FM> hello FM> i started testing the tcpip example from FM> mspgcc CVS (mspgcc/msp430-libc/examples/tcpip/*) FM> i've seen that victor antonovich applied a patch to fix FM> FIN_TIMEOUT handling... FM> but i think that there are still some problems left... FM> if i connect the device to internet i can happen that the FM> tcp-layer "hang up" -> you never can connect again FM> it seems that the layers below tcp are still working -> ping is working fine FM> what i found out till now: FM> the http server sent the page and has called tcpclose() FM> now the MSP runs in the mainloop and is calling DoNetworkstuff() again and again FM> normally the SocketStatus get rid of the active bit so that the mainloop FM> can do a TcpPassiveOpen again FM> the problem is that the SocketStatus (after TcpClose) stays unchanged for ever FM> i added some debug output a got these infos: FM> SockStatus = 0x0B : ACTIVE + CONNECTED + TX_BUF_RELEASED FM> TCPStateMachine = 0x06 : FIN_WAIT_2 FM> TCPFlags = 0x18 : TCP_CLOSE_REQUESTED + TIMER_TYPE_RETRY FM> these variables stay unchanged for ever... FM> has anybody some experience with this application or some ideas where FM> the problem could be ? FM> i'm trying to find out more - maybe i have to wait some hours again :-) FM> thanks for your help FM> matthias I have compiled an example taken from CVS five minutes ago. The uploaded from board webpage refreshes periodically without any problems. In my case, board and host system is LAN connected. Maybe you have some mixed-connections related problems? Regards, Victor. ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
