Hello,

I recently had an issue with RadioCoordinator giving 'previous declaration'
errors. I had commented code out randomly to see if I could change the
errors, and at one point, they looked like this:

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

However, I changed them back and got my normal previous declaration errors.
At the suggestion of someone who kindly helped me, I added AM.h to
RadioCoordinator to help with the typedef of TOS_MsgPtr to get rid of my
errors, but now the above error has come back, even though the other code
has changed back. What's worse is that even before including AM.h in
RadioCoordinator, another previously compiling application was giving the
same error. Anyone have any suggestions as to how to correct this?

Thank you,
Chris
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to