Hi Gustavo,

First off, glad to see someone trying out this radio stack even though
there's no commercial hardware available.

I think the main problem here is the TinyOS 2.x baseline interfaces recently
changed and are not compatible with TinyOS-2.0.2.  The AMPacket, Packet,
AMSend, etc. interfaces are different, and the Blaze radio stack is
compatible with the newest interfaces.  You'll probably have to check out
the TinyOS baseline to get it fixed.

The CC1100Control errors are valid.  I've been developing on a CC2500, and
haven't had the chance to compile the CC1100 stuff on my machine.  I'll send
the CC1100 error messages you've found to Jared Hill (cc'd) who's also
working on the stack to see if he can solve it and check it back in.

So try getting the latest TinyOS baseline and we'll work on fixing those
CC1100 compile time errors.  Thanks,
-David




-----Original Message-----
From: Gustavo [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 08, 2007 8:54 AM
To: [EMAIL PROTECTED]
Subject: Using blaze

Mr. Moss,

We have been attempting to use your blaze radio in our mote since it
provides all the code for the CC1100 radio. However, installing the
files in the tinyos-2.x-contrib/blaze/ to the tos folder in
opt/tinyos-2.x/tos results in the following error when we attempt to run
make: (even with make tmote1100):


mkdir -p build/utmost
    compiling ContinuousTransmitC to a utmost binary
ncc -o build/utmost/main.exe -Os -O -mdisable-hwmul -Wall -Wshadow
-DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -mdisable-hwmul -target=utmost
-fnesc-cfile=build/utmost/app.c -board= -DIDENT_PROGRAM_NAME=
\"ContinuousTrans\" -DIDENT_USER_ID=\"gustavo\" -DIDENT_HOSTNAME=
\"Gustavo\" -DIDENT_USER_HASH=0xba450eabL -DIDENT_UNIX_TIME=0x470a4d36L
-DIDENT_UID_HASH=0xd5cf4b3fL  ContinuousTransmitC.nc -lm 
In file included
from /opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageC.nc:27,
                 from /opt/tinyos-2.x/tos/chips/blazeradio/BlazeC.nc:55,

from /opt/tinyos-2.x/tos/platforms/utmost/ActiveMessageC.nc:35,
                 from ContinuousTransmitC.nc:11:
In component `BlazeActiveMessageP':
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc:59:
conflicting types for `AMSend.getPayload'
/opt/tinyos-2.x/tos/interfaces/AMSend.nc:125: previous declaration of
`AMSend.getPayload'
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc: In
function `AMSend.getPayload':
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc:60: too
many arguments to function `SubSend.getPayload'
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc: At top
level:
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc:133:
conflicting types for `Packet.getPayload'
/opt/tinyos-2.x/tos/interfaces/Packet.nc:108: previous declaration of
`Packet.getPayload'
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc:32:
`Snoop.payloadLength' not implemented
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc:32:
`Snoop.getPayload' not implemented
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc:32:
`Receive.payloadLength' not implemented
/opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageP.nc:32:
`Receive.getPayload' not implemented
In file included
from /opt/tinyos-2.x/tos/chips/blazeradio/select/RadioSelectC.nc:36,

from /opt/tinyos-2.x/tos/chips/blazeradio/am/BlazeActiveMessageC.nc:41,
                 from /opt/tinyos-2.x/tos/chips/blazeradio/BlazeC.nc:55,

from /opt/tinyos-2.x/tos/platforms/utmost/ActiveMessageC.nc:35,
                 from ContinuousTransmitC.nc:11:
In component `RadioSelectP':
/opt/tinyos-2.x/tos/chips/blazeradio/select/RadioSelectP.nc:116:
conflicting types for `Send.getPayload'
/opt/tinyos-2.x/tos/interfaces/Send.nc:114: previous declaration of
`Send.getPayload'
/opt/tinyos-2.x/tos/chips/blazeradio/select/RadioSelectP.nc: In function
`Send.getPayload':
/opt/tinyos-2.x/tos/chips/blazeradio/select/RadioSelectP.nc:117: too
many arguments to function
/opt/tinyos-2.x/tos/chips/blazeradio/select/RadioSelectP.nc: At top
level:
/opt/tinyos-2.x/tos/chips/blazeradio/select/RadioSelectP.nc:26:
`Receive.payloadLength' not implemented
/opt/tinyos-2.x/tos/chips/blazeradio/select/RadioSelectP.nc:26:
`Receive.getPayload' not implemented
In file included
from /opt/tinyos-2.x/tos/chips/blazeradio/link/PacketLinkC.nc:51,
                 from /opt/tinyos-2.x/tos/chips/blazeradio/BlazeC.nc:68,

from /opt/tinyos-2.x/tos/platforms/utmost/ActiveMessageC.nc:35,
                 from ContinuousTransmitC.nc:11:
In component `PacketLinkP':
/opt/tinyos-2.x/tos/chips/blazeradio/link/PacketLinkP.nc:166:
conflicting types for `Send.getPayload'
/opt/tinyos-2.x/tos/interfaces/Send.nc:114: previous declaration of
`Send.getPayload'
/opt/tinyos-2.x/tos/chips/blazeradio/link/PacketLinkP.nc: In function
`Send.getPayload':
/opt/tinyos-2.x/tos/chips/blazeradio/link/PacketLinkP.nc:167: too many
arguments to function `SubSend.getPayload'
In file included
from /opt/tinyos-2.x/tos/chips/blazeradio/acks/AcknowledgementsC.nc:27,
                 from /opt/tinyos-2.x/tos/chips/blazeradio/BlazeC.nc:71,

from /opt/tinyos-2.x/tos/platforms/utmost/ActiveMessageC.nc:35,
                 from ContinuousTransmitC.nc:11:
In component `AcknowledgementsP':
/opt/tinyos-2.x/tos/chips/blazeradio/acks/AcknowledgementsP.nc: At top
level:
/opt/tinyos-2.x/tos/chips/blazeradio/acks/AcknowledgementsP.nc:106:
conflicting types for `Send.getPayload'
/opt/tinyos-2.x/tos/interfaces/Send.nc:114: previous declaration of
`Send.getPayload'
/opt/tinyos-2.x/tos/chips/blazeradio/acks/AcknowledgementsP.nc: In
function `Send.getPayload':
/opt/tinyos-2.x/tos/chips/blazeradio/acks/AcknowledgementsP.nc:107: too
many arguments to function
/opt/tinyos-2.x/tos/chips/blazeradio/acks/AcknowledgementsP.nc: At top
level:
/opt/tinyos-2.x/tos/chips/blazeradio/acks/AcknowledgementsP.nc:216:
conflicting types for `SubSend.getPayload'
/opt/tinyos-2.x/tos/interfaces/Send.nc:114: previous declaration of
`SubSend.getPayload'
In component `BlazeReceiveP':
/opt/tinyos-2.x/tos/chips/blazeradio/receive/BlazeReceiveP.nc:51:
`Receive.payloadLength' not implemented
/opt/tinyos-2.x/tos/chips/blazeradio/receive/BlazeReceiveP.nc:51:
`Receive.getPayload' not implemented
In file included
from /opt/tinyos-2.x/tos/chips/blazeradio/csma/CsmaC.nc:38,
                 from /opt/tinyos-2.x/tos/chips/blazeradio/BlazeC.nc:74,

from /opt/tinyos-2.x/tos/platforms/utmost/ActiveMessageC.nc:35,
                 from ContinuousTransmitC.nc:11:
In component `CsmaP':
/opt/tinyos-2.x/tos/chips/blazeradio/csma/CsmaP.nc:112: conflicting
types for `Send.getPayload'
/opt/tinyos-2.x/tos/interfaces/Send.nc:114: previous declaration of
`Send.getPayload'
In file included
from /opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueSendC.nc:49,
                 from /opt/tinyos-2.x/tos/chips/blazeradio/BlazeC.nc:77,

from /opt/tinyos-2.x/tos/platforms/utmost/ActiveMessageC.nc:35,
                 from ContinuousTransmitC.nc:11:
In component `UniqueSendP':
/opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueSendP.nc:99:
conflicting types for `Send.getPayload'
/opt/tinyos-2.x/tos/interfaces/Send.nc:114: previous declaration of
`Send.getPayload'
/opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueSendP.nc: In function
`Send.getPayload':
/opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueSendP.nc:100: too many
arguments to function `SubSend.getPayload'
In component `UniqueReceiveP':
/opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueReceiveP.nc: At top
level:
/opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueReceiveP.nc:55:
`Receive.payloadLength' not implemented
/opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueReceiveP.nc:55:
`Receive.getPayload' not implemented
/opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueReceiveP.nc:55:
`DuplicateReceive.payloadLength' not implemented
/opt/tinyos-2.x/tos/chips/blazeradio/unique/UniqueReceiveP.nc:55:
`DuplicateReceive.getPayload' not implemented
In file included
from /opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlC.nc:4:
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100.h:11:2: warning:
#warning "*** INCLUDING CC1100 RADIO ***"
In file included
from /opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlC.nc:25,

from /opt/tinyos-2.x/tos/platforms/utmost/ActiveMessageC.nc:36,
                 from ContinuousTransmitC.nc:11:
In component `CC1100ControlP':
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc: In
function `BlazeConfig.setFrequencyKhz':
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:206:
`freq' undeclared (first use in this function)
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:206: (Each
undeclared identifier is reported only once
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:206: for
each function it appears in.)
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:206:
`FREQ_MAX' undeclared (first use in this function)
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:206:
`FREQ_MIN' undeclared (first use in this function)
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc: In
function `freqToChannel':
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:259:
`BASE_FREQ' undeclared (first use in this function)
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:260:
`CHAN_WIDTH' undeclared (first use in this function)
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc: In
function `channelToFreq':
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:270:
`CHAN_WIDTH' undeclared (first use in this function)
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlP.nc:271:
`BASE_FREQ' undeclared (first use in this function)
In component `CC1100ControlC':
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlC.nc: At top
level:
/opt/tinyos-2.x/tos/chips/blazeradio/cc1100/CC1100ControlC.nc:54: cannot
find `TxInterrupt'
In component `ContinuousTransmitC':
ContinuousTransmitC.nc:21: no match
make: *** [exe0] Error 1


As you can see, there is a conflict. I suppose you have been
successfully using the code, so perhaps you know what is needed.
We modified the .platform file for both our platform and the tmote1100
to reflect the correct path i.e.:
 %T/../../blaze/tos/chips/blazeradio
was changed to
/tos/chips/blazeradio

we also attempted to put the blaze folder in the opt (since %T/../../
represents the opt folder.


I would appreciate any help on this matter.

Gustavo Litovsky



_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to