[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] R: ping slow down

From: Rastislav Uhrin
Subject: [lwip-users] R: ping slow down
Date: Mon, 30 May 2016 23:26:50 +0200

Thank you for answering.

This task waits on semaphore from interrupt routine which is invoked when Eth 
frame is received.

The driver is form Infineon.

Port to RTOS should be OK because I have compared many I found on internet and 
they are all the same.

OK. I will investigate further.


-----Messaggio originale-----
Da: lwip-users [mailto:address@hidden Per conto di Sergio R. Caprile
Inviato: lunedì 30 maggio 2016 23:07
A: address@hidden
Oggetto: Re: [lwip-users] ping slow down

And that task runs every...
>> Most likely your code is polling at regular intervals and what you 
>> see as varying delay is the phase difference of your ping frequency 
>> and your poll frequency "signals".
Try to move pins every time that task runs Try to move pins every time you see 
a packet, and check on a scope Read the wiki and see if you are doing things 
right for an RTOS-based port
Make sure you don't call low level routines from interrupt code, all non socket 
nor netconn calls must be on the same thread.

No, it is not normal to have delays unless something is causing those delays. 
lwIP is mostly event driven, when a frame comes in and you notice that, you 
send it to lwIP and it peels protocol by protocol until it either calls you 
(RAW API)/delivers to netconn/socket (which I don't
master) or responds itself (ping).
If it does not responds itself asap is because you don't give it the frame or 
you don't let it run fast enough to do its job.

You can also check for known caveats with your port to your RTOS.

lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]