Roadstar Runner, can you please do a verbose build and send us the output.
That will tell us exactly what modules you are pulling in. Also where did your source come from? Is from the release on github or the development trunk on github or somewhere else. On Wed, Jan 8, 2014 at 6:18 AM, Miklos Maroti <[email protected]>wrote: > Hi! > > The original radio stack makes sure that the RadioAlarm is never used > by two components simultaneously. So this lockup with the stock > software should not happen. Did you see this with the standard stack? > > Best, > Miklos > > On Fri, Dec 6, 2013 at 10:44 PM, Roadstar Runner <[email protected]> > wrote: > > > > I have been experiencing intermittent lockups with the radio stack Iris > > modules. After some debugging i figured that the problem starts in the > > routine SubReceive.receive() in the file RandomCollisionLayerP.nc. > > > > If for some reason RadioAlarm is not free (used by some other module) , > the > > state variable is updated (state |= STATE_BARRIER;) . > > The only way for the state variable to be reset is in RadioAlarm.fired(), > > which will not be triggered since we were unable to get hold of the > > RadioAlaram in the first place. > > > > Please comment if my analysis > > > > Thanks in advance . > > > > Lewis > > > > > > _______________________________________________ > > Tinyos-help mailing list > > [email protected] > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- Eric B. Decker Senior (over 50 :-) Researcher
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
