actually this has already been done in the tp-freeforall tree ( https://github.com/tp-freeforall/prod) <https://github.com/tp-freeforall/prod>
It is implemented in https://github.com/tp-freeforall/prod/blob/tp-master/tos/system/SchedulerBasicP.nc it is in memory logging. there are some gdb functions that deal with this available at... https://github.com/tp-freeforall/prod/blob/tp-master/tools/99_gdb/gdb_tasks.py you need to be using GDB talking to a gdb remote stub implemented by a JTAG probe to the device under test (DUT). such as a segger jlink. On Sun, Dec 27, 2020 at 6:41 AM Jeremy J <redstripe...@gmail.com> wrote: > There are no built in functions. you will have to manually snapshot the > timer count at the start and stop of a task > > On Sun, Dec 27, 2020 at 8:59 AM Anita Patil <anitha.bija...@gmail.com> > wrote: > >> Is there any function in nesC to compute time taken by a task processing? >> >> In Timer.nc interface there are functions Iike getnow(), gett0() , >> getdt(), startperiodic() etc. But I didn't get any function to compute time >> taken by a task processing. I.e to start and stop the timer respectively >> before posting a task and after posting a task. >> >> Thank you in advance. >> _______________________________________________ >> Tinyos-help mailing list >> Tinyos-help@millennium.berkeley.edu >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > _______________________________________________ > Tinyos-help mailing list > Tinyos-help@millennium.berkeley.edu > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Eric B. Decker Senior (over 50 :-) Researcher
_______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
