No subject

interfaces. Simple enough for me to fix within my own code, however errors 1 and
3 were triggered from CC2420ControlC as HplCC2420InterruptsC had signals coming
from multiple provided interfaces, not all of which were wired.

Last I checked, you can choose _not_ to wire an interface provided by another
component if you desire, which seems to be what the authors of the
CC2420ControlC component were doing. So then, I ask, did the rules change with
the release of 2.1?

The second error I fixed by connecting the rest of the interfaces provided by
CC2420ControlC to my module, moving from:
  PowerTestP.RadioConfig -> CC2420ControlC.CC2420Config;
to 
  PowerTestP.RadioPower -> CC2420ControlC.CC2420Power;
  PowerTestP.RadioConfig -> CC2420ControlC.CC2420Config;
  PowerTestP.RadioControl -> CC2420ControlC.Resource;
  PowerTestP.RadioRSSI -> CC2420ControlC.ReadRssi;

(omitting contents of PowerTestP - so far the module only has empty event
handlers in it)

..However the first and the third errors I had to repeat the same effort by
adding wirings and event handlers to CC2420ControlC and CC2420ControlP
themselves, using about the same method as above, moving from:
  components HplCC2420InterruptsC as Interrupts;
  CC2420ControlP.InterruptCCA -> Interrupts.InterruptCCA;
to 
  components HplCC2420InterruptsC as Interrupts;
  CC2420ControlP.InterruptCCA -> Interrupts.InterruptCCA;
  CC2420ControlP.CaptureSFD -> Interrupts.CaptureSFD;
  CC2420ControlP.InterruptFIFOP -> Interrupts.InterruptFIFOP;

..which made me ponder my second question:

2) Is this going to work?
The above solution of modifying the CC2420Control* files got my skeleton module
to compile, however I'm paranoid about changing the tinyOS distribution to get
my programs to work. Will this likely blow up on me?

Best,
Charley Robinson
UVM Graduate Student
MS Computer Science