TINI replies with TCP window size set to 0

Hi,

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.

I am developing a product based on DS80C400 and
writing the code in C using uVision 2. I have
downloaded the HTTP timeserver demo program and it
runs fine. In my program I initialise some hardware
and then create and run 3 tasks:

Task 1 scans a keypad and updates an LCD 
Task 2 gets processes data from the a serial interface
on serial port 2 (serial port 2 is interrupt driven
and puts rx data into a input buffer and gets tx data
from a buffer)
Task 3 is a HTTP server task which is a basically a
clone of the time server example

The program is quite big and uses 11170 bytes of xdata
(all my variables are declared as ‘far’) and 17002
bytes of code. I’m wondering if the TINI socket code
is looking for space in only the first 64K, which is
full.

Any help would be gratefully received as my deadline
is quickly approaching :-(

Cheers, Mark

P.S. I am running in contiguous mode 16MB mixed
program/data



	
	
		
____________________________________________________________
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