I used instrumentation. I can add a profiling function at the beginning of each
generated C function. Also, I know the C function that represents the event
handler (e.g BlinkC$Timer0$fired). So, I can know the Interval time between
each two repeated events. As a result, I can compute the average time interval
between events. (e.g. every 0.023 s)
Philip Levis <[EMAIL PROTECTED]> wrote:
On Apr 6, 2008, at 5:41 PM, Mustafa Hammad wrote:
> Dear Philip,
>
> Thank you for your replay.
>
> In Blink application under app/ directory:
> Timer0 fire every 0.023 s (at average) while it should fire every
> 0.25 s
> Timer1 fire every 0.046 s (at average) while it should fire every
> 0.5 s
> Timer2 fire every 0.09 s (at average) while it should fire every 1 s
>
> Also, in BlinkTask application under app/tutorial directory:
> Timer0 fire every 0.038 s (at average) while it should fire every
> one second.
>
> The last one I have tested is Sense application under app/ directory:
> Timer fire every 0.019 s (at average) while it should fire every 0.1
> s.
>
> I am using Tinyos 2.x under xubuntu. To run the simulater, I used
> the standard variables.py example script.
>
> I am now working on timing analysis for nesC application under
> TOSSIM. But with these results I dont know how I can get an
> accurate statistics.
>
How are you measuring time? I.e., when you say it fires 0.023s, what
do you mean?
Phil
---------------------------------
You rock. That's why Blockbuster's offering you one month of Blockbuster Total
Access, No Cost._______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
