[En-Nut-Discussion] NutTcpConnect and NutTcpCloseSocket problem
ole.reinhardt at embedded-it.de
Fri Aug 10 14:04:46 CEST 2012
> Yes, the board reseted !
> I understand what you said in your explanation.
> This means that NutTcpSocketClose should use somewhere NutSleep(1) instead of NutThreadYeald().
> As NutSleep(1) can releases the CPU to a lower priority thread...
No, not necessarily. There _might_ be a bug. But however the solution
would not be to introduce a sleep there but to find the possible race
condition (if there is any at all).
I think we will have to check this further before changing anything
hasty. For now it's just an idea. I will do some tests with the
debugger. But I only can do so on my LCP or ARM boards, as I don't have
an ethernut 2.1 at hand.
Perhaps Harald could also do some tests?
Thermotemp GmbH, Embedded-IT
Embedded Hard-/ Software and Open Source Development,
Integration and Consulting
Geschäftsstelle Siegen - Steinstraße 67 - D-57072 Siegen -
tel +49 (0)271 5513597, +49 (0)271-73681 - fax +49 (0)271 736 97
Hauptsitz - Hademarscher Weg 7 - 13503 Berlin
Tel +49 (0)30 4315205 - Fax +49 (0)30 43665002
Geschäftsführer: Jörg Friedrichs, Ole Reinhardt
Handelsregister Berlin Charlottenburg HRB 45978 UstID DE 156329280
More information about the En-Nut-Discussion