That shouldn't be necessary. TimerB5 does not interfere with TimerB4.
These are the current hardware timer allocations in TinyOS 1.x for
the Telos platform:
TimerA0 is used by msp430/MSP430ADC12.nc
TimerA1 is used by msp430/MSP430ADC12.nc
TimerB1 is used by telos/HPLCC2420C.nc
TimerB3 is used by msp430/TimerC.nc
TimerB4 is used by telos/TimerJiffyAsyncC.nc
That leaves you TimerA2, TimerB0, TimerB2, TimerB5, and TimerB6 as
entirely safe timers to use -- none of them should impact radio
communication.
probably not the radio hardware, but i believe it messes up something (probably the state machine in CC2420RadioM) in the process of sending messagses:
i'm sending messages every 1 second and have the async timer fire every 128 ticks (each tick is 1/32768 second). and i notice that:
1) any where between the 8th and 25th second, the radio starts to not signal sendDone events.
2) after a while (1 minute or so), the sendDone is signaled.
3) then it's back to normal for a little bit.
4) and the process repeats.
if if stop the async timer as soon as send() returns SUCCESS, then the above behavior does not show up.
by the way, what are the resolutions of each of the timers you mentioned above? you can just point me in the direction to look.
thanks.
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
