Re: [lwip-users] (no subject)

[Anirudha Sarangi]

Hi Kieran,

Just cross-checked. There is a mistake. With my present timer setup, tcp_tmr is getting called every 350 msec instead of every 250 msec. Do you think it could be causing my issue ?

Then as I understand, once I am in tcp_tmr, I should disable all other interrupts so that there could be no corruption. Will that be fine?

 

regards

Anirudha

---

From: Kieran Mansley <address@hidden>
To: Mailing list for lwIP users <address@hidden>
Sent: Thursday, 7 July 2011 15:45:41
Subject: Re: [lwip-users] (no subject)

On Thu, 2011-07-07 at 18:07 +0800, Anirudha Sarangi wrote:
> Hi,
> I am new to lwip. Just took over from someone who has left my
> organization. Could you tell me exactly which timer functions in lwIP?
> If I know it I can cross-check if they are getting called at regular
> intervals or not.
> 
> As I said my lwIP application does not have any OS. I have used a
> timer to call "tcp_fasttmr" and "tcp_slowtmr" at regular intervals.
> Are you referring to these functions?
> And if so, what is the interval at which "tcp_fasttmr" should be
> called and what interval "tcp_slowtmr" should be called?


If you call tcp_tmr() every 250ms it will call tcp_fasttmr and
tcp_slowtmr for you at the appropriate intervals.  You need to be
careful about making sure you don't call tcp_tmr when there are other
threads active (including interrupts) in lwIP however; this is a common
problem in ports of lwIP that leads to internal state being corrupted.

Kieran



_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users