Actually it was simple:
Operator error -- I can't fathom the TOS paradigm...
I was wiring to the code module rather than the config file
in the code that I attached, so the connections I thought I
had made were not. This was compounded by the compiler helping
me by eliminating code that was never called, so all the parts
of the module that I thought were compiling correctly were
never even touched.
thanks for all your help and support
MS
Michael Schippling wrote:
> This seems like it should be simple, but of course it's not...
>
> I have a T1 module with the usual standard control functions,
> implementing the SplitControl interface -- although it doesn't
> seem to matter, I tried StdControl too.
>
> For some reason I cannot put calls to other module interfaces
> in the *Control.start() function. I get this error:
>
> In component `cryoSensorM':
> cryoSensorM.nc: In function `SplitControl.start':
> cryoSensorM.nc:126: I2CPacketControl.start not connected
> cryoSensorM.nc:129: I2CPacket.writePacket not connected
>
> (The same thing happens with Timer.start() so it's not just
> the I2C stuff. And there seem to be plenty of examples of
> doing this in other modules that I don't need to use...)
>
> If I move the offending code to any other function, e.g.,
> init() or stop() I get no complaints and a no-error compile.
> And all other calls to the I2CPacket module in the file
> seem to pass muster just fine. If I move the code to a
> sub-function, or a sub-task, I still get the complaint,
> so somehow it knows what I want to do and refuses to comply.
> Moving the whole start() function around doesn't matter either.
>
> I'm using Moteworks, which is some mystery late version of TOS1.x,
> and compiling for the iris platform with the "route.hp" option
> that does some magic in their MULTIHOP XMESH compile system.
>
> I've attached the config and code files for this module, but not
> the entire program. If you really want to try compiling the whole
> thing I'll gladly send you everything. Look for `SplitControl.start'
> to see where I've marked the lines that cause the trouble.
>
> thx
> MS
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
