[Tinyos-help] Alternate reasons for 'not connected' error

[Christopher Jenkins]

Hello,

This is my error output when I execute the make command:

In component `CC1000RadioM':
C:\Crossbow\cygwin\opt\MoteWorks\tos\platform\cricket\CC1000RadioM.nc: In
function `SpiByteFifo.dataReady':
C:\Crossbow\cygwin\opt\MoteWorks\tos\platform\cricket\CC1000RadioM.nc:539:
RadioSendCoordinator.blockTimer not connected
C:\Crossbow\cygwin\opt\MoteWorks\tos\platform\cricket\CC1000RadioM.nc:540:
RadioReceiveCoordinator.blockTimer not connected
C:\Crossbow\cygwin\opt\MoteWorks\tos\platform\cricket\CC1000RadioM.nc:567:
RadioSendCoordinator.startSymbol not connected
C:\Crossbow\cygwin\opt\MoteWorks\tos\platform\cricket\CC1000RadioM.nc:575:
RadioSendCoordinator.byte not connected
C:\Crossbow\cygwin\opt\MoteWorks\tos\platform\cricket\CC1000RadioM.nc:751:
RadioReceiveCoordinator.startSymbol not connected
C:\Crossbow\cygwin\opt\MoteWorks\tos\platform\cricket\CC1000RadioM.nc:785:
RadioReceiveCoordinator.byte not connected
make: *** [exe0] Error 1


Is there any reason I would experience this error OTHER than the events not
being connected, (missing declaration in a header, shared file confusion
etc.) because I'm sure that they are.

Thank you,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20070809/f0cae5e2/attachment.htm