Re: [lwip-devel] STM32, FreeRTOS and lwIP - Timeout problems

[Rüdiger Asche]

so is your application a tcp server or a tcp client? Since you write
about timeouts, I assume it is a tcp client, and an attempt to
connect() returns with -1 and the error set to ETIMEOUT? It would help
if you installed a sniffer (eg wireshark) and logged the packet flow;
that would at least narrow down the problem.

What kind of TCP server do you communicate against? Bear in mind that
a timeout may also imply that the server is not able to service the
request! This happens frequently, for example when the TCP Server is
single threaded meaning that it services a client request without
spawning a new thread. When that happens, other TCP clients will first
end up in a queue, and when the queue overflows, nothing happens on
the net (one of those brain dead details of TCP practice). So a busy
server might as well the problem. Again, a sniffer trace would help
narrowing down the problem.

2013/1/8, Thomas Kølbæk Jespersen <address@hidden>:
> Thank you for your comments on this issue.
> I have been searching closely on this forum to see if could find anything
> related to this issue, without luck.
>
> I found this thread yesterday and have tried all the steps they recommend
> but it didn't solve the problem with the timeouts:
> http://www.freertos.org/FreeRTOS_Support_Forum_Archive/October_2011/freertos_Random_hangs_with_STM32_4753773.html
>
> I have been struggling so much with this issue by now that I am willing to
> pay anybody with exprience within the STM32, FreeRTOS and lwIP field, to
> get my already made project and source code working.
> Please have a look at this Freelancer post with some more details about the
> issue:
> https://www.freelancer.com/projects/Electronics-Microcontroller/STM-Ethernet-lwIP-FreeRTOS-FatFS.html
>
> Kind Regards
> Thomas Jespersen
>