Re: TINI replies with TCP window size set to 0

Mark Underwood <basicmark-/[email protected]>
Newsgroups gmane.comp.hardware.microcontrollers.tini
Message-ID <[email protected]>
Thanks for the reply. After some investigation I found
that the problem was that my XDATA variables where
over writing the interrupt vector table. I reserved
the first 1K of memory 0x0 - 0x3FF in the
startup400.a51 file and it worked fine.

Cheers, Mark


 --- Robert Muchsel <robert.muchsel-6tN4nzCoH/[email protected]>
wrote: > > Has anyone had a problem where in response
to a
> TCP
> > request TINI has replied with a window size of 0?
> I am
> > using "Analyzer" (an Ethernet packet sniffer) I
> can
> > see the TINI receives the message and sends a
> reply,
> > but sets the window size to 0.
> 
> This happens when the TINI's input buffers (rather
> small compared to a
> PC) are full. You need to read from the socket (on
> the TINI), then the
> window size will increase.
> 
> 
> -- 
>   Robert Muchsel - Dallas Semiconductor -
> http://www.maxim-ic.com/TINI/
>  


	
	
		
____________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html
_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.