Hello,
yes you are right, the call to sys_check_timeouts is enough. My
problem was that my connection has closed when my problem occurred. So
thanks, the timers.c is fine and suits all my needs. Thanks for your
support.
best
Matthias
On Tue, Oct 28, 2014 at 1:59 PM, goldsi...@gmx.de
Matthias Dübon wrote:
calling sys_check_timeouts in the main loop does not suffice, cause
the tcp_tmr is not activated in the timers.c module.
Matthias, there would be something seriously wrong with your code if
calling sys_check_timeouts wouldn't suffice.
I wonder how what are you actually
Hello everyone,
I am diving into lwip and I have found the timers.c module. This
module seems to be a nice possibility to setup the different timer
(e.g. for arp, DHCP, ...). But I am wondering why is the call to
tcp_tmr not included in timers.c? Are there any architectural reasons
or do I
All I can tell you, and I don't know if it suffices, is that you call
sys_check_timeouts();
in your main loop and all timing is done.
Check your lwipopts.h for the number of timers if using dhcp, dns, etc.
Should you need to use a timer for your own purposes:
static void
Hi Sergio,
calling sys_check_timeouts in the main loop does not suffice, cause
the tcp_tmr is not activated in the timers.c module. For me the
natural solution would be to add tcp_tmr activation to timers.c and
then call sys_check_timeouts in my main loop. But I am not sure if
there's a reasion
All my TCP examples and applications work, and I'm calling
sys_check_timeouts(); so, if tcp_tmr is really not called, then
something with the same functionality is being called.
I do use NO_SYS=1 and have provided a working sys_now() function.
DHCP and DNS timeouts are also handled through
