On May 1, 2008, at 10:16 AM, Kevin Klues wrote: > I doesnt provide start and stop though. It only uses it. Return > EBUSY to whom? > > Kevin
Uh, the point is that SplitControl.stop should only return EBUSY if the underlying component is in the starting state. So the question is whether the observed lockup is due to 1) PowerManagerP is calling stop() when the component is in the starting state (PowerManagerP is not managing state transitions correctly), 2) more than one component is wired to SplitControl (violates wire- once and power management), or 3) the underlying component is not compliant with TEP 115. Phil _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
