We dont want to
upgrade to VDSP 5.0 and an entirely new version of lwIP at this stage of our
project development.
Do you know if there
has been any fix for this particular bug in the lwIP 1.2.0 , or the VDSP 5.0
port? I will file a bug anyway as Kieran
suggested.
What could possibly
go wrong if I simply ignored this assertion for the
time-being?
Thanks and
regards,
Aparna
From:
address@hidden
[mailto:address@hidden
On Behalf Of S. Ali
Tokmen
Sent: Monday, December
10, 2007 6:34 PM
To:
Mailing list for lwIP
users
Subject: Re: [lwip-users] Receiving
RSTs
I think the February 2007 update of VisualDSP has lwIP
0.6. Is it possible for you to upgrade to VisualDSP 5.0 -it includes lwIP
1.2.0?
GSM (fr): +33 66 43 00 555 [Bouygues Telecom]
GSM
(tr): +90 555 266 52 73 [Avea]
----- Original Message -----
Sent:
Saturday, December 08, 2007 11:27 AM
Subject:
[lwip-users] Receiving RSTs
We are using Lwip ported onto
the Analog Devices VDSP++ 4.5 (Blackfin family , Feb 2007 update) to develop
a client which tries to connect to a windows PC server using the socket
connect() API.
When the Windows server is not
up, the PC responds with a RST for a received SYN. The connect() API returns
an error, and the client retries connect() after every few seconds.
After retrying for the number of
times equal to the SYS_MBOX_SIZE, the code fails with the assertion
sys_mbox_post: mbox not full".
Receiving an RST triggers the
err_tcp() error function which posts a NULL message. It appears that the
mbox is getting populated with NULL messages, but these messages are not
being read out at all, and so the mbox is getting
full.
Is this correct behaviour
?
Thanks and
regards,
Aparna
_______________________________________________
lwip-users
mailing
list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users