Hi,
You probably won't get any errors anymore because the program is not
being compiled. I would guess that this line is the single most
important line in the whole Makefile :-)
I don't know the detailed meaning of this line, but the $(LDFLAGS) is
usually the set of flags specific for linking.
Hi,
Many of our friends, especially the ones knowing about routing, are in
the United States. Maybe you should take time differences into account
before becoming impatient :-)
Assuming that you use acknowledgments, then the sendDone() function is
called with a parameter describing the outcome.
Hi Sam,
The MicaZ uses the same radio chip (cc2420). Usually applications for
the MicaZ also work on the Telosb platforms. The main differences are
the sensors, but they should be relatively straight forward to change.
Of course the Telosb platform use a different microcontroller (msp430
instead
dear friend:
yeah, but my sensor can not use the Photo mudule, it is only humidity senses.
many samples in /apps if installed into my sensor will occur an error. I
found that most of the sample code is only suitable to mica/micasb, so do you
know where I can get the corresponding code for my
Hi Sam,
You could try boomerang from the former Moteiv. Their Tmote Skys should
be compatible with the telosb platform.
http://docs.tinyos.net/index.php/Boomerang
Cheers,
Urs
Renee Azhen schrieb:
dear friend:
yeah, but my sensor can not use the Photo mudule, it is only humidity
senses.
Hi, I am a new learner of TinyOS, use crossbow's IRIS module.
My program is sample.I send data from my own board to IRIS using
UART0,when it received ,it send back to my board. When it running,I saw it have
got the data,but the data it send back was not right.I don't know why.
Below
Hi,
So do I understand this correctly, that you are trying to implement a
new platform? I cannot really help you there, but other people on the
list might. We would need to know the processor that your platform uses
and what compiler you intend to use for your platform.
If the Null application
Hello David
The next code is in the RXFIFO.readDone function in the CC2420ReceiveP.
From what I can understand when we activate the hardware address
recognition and provide the device short address and activate the
transceiver address recognition field, this address is used in the
Hello,
i´m trying to compile the Null application, I type ´make isense´
when I compile because my new platform is called isense
yes when I commit out this line the program is not compiled. what do
you mean by a problem with the software setup?
I didn´t try to compile Blink right now, I want
I'm wondering whether I can define global function.
The global function mean, I define a function in
component A, and I can call this function in component
B without using interface, just call the function directly?
No, all interaction between components has to go through the commands and
Michiel Konstapel wrote:
I'm wondering whether I can define global function.
The global function mean, I define a function in
component A, and I can call this function in component
B without using interface, just call the function directly?
No, all interaction between components has to go
Hello all, the question is: if I install on Telosb the BlinkC component or any
other program running on Tinyos-2.x, I see a current absorption on the
expansion connectors (channel ADC0, ADC1 ADC2 ADC3) about of 7-10 mA . Instead
if install the same component on Tinyos-1.x, the current equals 0
For instance:
for a file,
/tos/platforms/intelmote2/chips/cc2420/HplCC2420SpiC.nc
./tos/platforms/micaz/chips/cc2420/HplCC2420SpiC.nc
./tos/platforms/telosa/chips/cc2420/HplCC2420SpiC.nc
where I want to use the telosa version, since it is the same in the
ecosens1 platform:
HPL
Hi
I've managed to install tinyos2.x on Mac Os X Leopard following the
great tutorial available at
http://docs.google.com/View?docid=ajjph9mvqk3z_bchp66xkmgk6npli=1#Installing_Stow
Nonetheless I've found two mistakes the first when compiling the
tinyos-2.x tools and the second while generating
My guess would be that there is a 'hidden' main() component
that sets the entry address _start. The tos/system/RealMain.nc
might have something to do with this, but probably something needs
to be defined into the compiler or assembler to tie it all together...
Of course, if your controller's
There is a dreaded DemoSensor impl in the T1 msp430 directory
so that should handle the demo apps which use such, like O'scope.
After that, it's probably an exercise for the reader of the
tutorial to swap out sensors.
Other than the specifics of sensing devices, which would
necessarily be
Sure - you can modify the basestation application to retransmit if you don't
get an ack. Take a look at the PacketLink component and interface, it will
help you do so automatically. For my deployment applications where good
connectivity is required, I've modified base station to use the
Ian,
Porting your apps from mica2 to iris should not be an issue. The radios
are different, other than that they are pretty similar from the software
point of view. On the iris, you will get better power consumption, twice
as much ram and better radio range and bandwidth.
Janos
Hi Roman,
First of all, thanks for your help.
Today with Tektronic tds3052 and a Agilent 34401A 6 1/2 digit multimeter, I can
measure the various LPM modes with success.
With Null application,
Mode Active - 1.63 mA
LPM0 - 0.151 mA
LPM1 - 0.150 mA
LPM2 - 25 uA
LPM3 - 6 uA
LPM4 - 4 uA
With a
You should be able to use the .platform file to back reference to
other directories or explicitly add them with -I at NCC time.
Of course everything else will be included if you 'accidentally'
use modules which your platform doesn't support.
MS
John Griessen wrote:
For instance:
for a file,
Hi All,
My Girl, who conveniently stayed out of the camera had this idea...
http://www.youtube.com/watch?v=H-eXATQajWg
BTW: It's a joke; so do not take seriously
--
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
Juan Alberto Cirez, CFAA/CFAT, CIPS/ISP(e), HSA(e), CSD(e)
I didn't really understand if this warning comes from TinyOS or from the
Toolchain !
II'm porting TinyOS to Jennic JN5139R1 microcontroller and i'm compiling for my
new platform called iSense which is based on the JN5139R1 microcontroller, it
seams to compile the Null application but I still
I'm sorry, but there's been too much water under the bridge for me...
What I was trying to say, and it seems to be somewhat true, is that
you need a symbol named _start that tells the link/loader where to put
the very first executable instruction in 'physical' memory. I believe
there was an
I get the following error when trying to compile my file for TOSSIM in
TinyOS 2.0.2.
make micaz sim
...
newdisC.nc: In function `Timer2.fired':
newdisC.nc:142: implicit declaration of function `itoa'
make: *** [sim-exe] Error 1
Note, the file compiles (and runs) fine on the real micaz.
The
KURT PETERS wrote:
I get the following error when trying to compile my file for TOSSIM in
TinyOS 2.0.2.
make micaz sim
...
newdisC.nc: In function `Timer2.fired':
newdisC.nc:142: implicit declaration of function `itoa'
make: *** [sim-exe] Error 1
Note, the file compiles (and runs) fine
25 matches
Mail list logo
