Re: [Tinyos-help] Asking you about implement of RPL, i did not see it
I heard Mr.Stephen told that RPL is implemented in tinyos in folder blip/rpl. But I find it in cvs source of tinyos in google group and sourceforge , but I did not see it. Could you let me know where can I find it? http://code.google.com/p/tinyos-main/source/browse/#svn%2Ftrunk%2Ftos%2Flib%2Fnet%2Frpl Have not tested myself how it works, but I suppose this are the files. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Unable to decrypt CC2420 AES packets manually
Hi, we are using an AVR RZRAVEN USB stick to sniff the traffic sent between TelosB motes running TinyOS 2.1.1. The traffic is encrypted using the hardware AES-encryption provided by the CC2420 transceiver. The problem is, I am unable to successfully decrypt the packets, even though I know the key and all (almost; see below) information for constructing the IV/nonce. For verification, I use the openssl command by specifying the appropriate 'iv' and 'K' parameters. According to the CC2420 data sheet [1] (Table 7, page 45) the nonce consists of flags, EUI64 source address, frame counter, key sequence counter and block counter. Going through the fields, here are the issues I am facing: 1) TinyOS sets the flags to 0x01. Why does it not set the flags according to the data sheet? 2) TinyOS does not use a EUI64 address. In the TinyOS sources, I can see that it sets this address field to all 0's. 3) I assume the 'key sequence counter' is just the *index* of the key used for encryption. So this value should either be 0 or 1. But then, why does TinyOS always set this to 0? 4) TinyOS also seems to set the block counter to 0x0001. According to IEEE 802.15.4-2003 (7.6.2.2, page 173), this should be set to 0 for the first block. These issues raise the question, if there are things going on inside the CC2420 chip, which TinyOS does not have control over. For one thing, the CC2420 data sheet is not very explicit about which information has to be filled in by software and which fields are overwritten by the chip. To my understanding, only the block counter is set by the chip. On the other hand, attempts to decrypt the payload with a source address of all 0's, the correct frame counter and key index (as given in the header) and a block counter of 0 or 1 and all possible variations for the flags field, have failed. As far as I can see, the only reason for failure can be some 64bit source address I am not aware of. Consequently, I tried reading out the IEEEADR value from the CC2420 RAM. But after each reset, this gave slightly different values, suggesting that the value in there is garbage (it is not set by TinyOS either, according to the sources). Can someone please shed some light on this? Note that the traffic can successfully be decrypted by other TinyOS motes. So given knowledge about the key and all packet bytes only, the mote is able to construct a valid nonce value. [1] http://focus.ti.com/lit/ds/swrs041b/swrs041b.pdf Kind regards, -- Jakob Bieling, Computer Science 4, University of Bonn ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problem with PacketIndicator / EnergyIndicator interfaces
I dont know whether its a technical issue with PacketIndicator /
EnergyIndicator interfaces or is there something I am doing wrong. I am
trying the following code to sense the channel before sending my packet. I
want to make sure that each sender reserve the time window before sending
something so as to avoid simultaneous transmissions of frames from 2
different senders ( this is unlike BMAC in which 2 transmitters can send
simultaneously as long as the transmissions dont collide and for that it
uses backoff timer). But unfortunately even after sensing the channel for
100 msec I am still having interventions between different transmissions
even though difference between each back-to-back sending within one
transmission window is from 8-20msec.
here is the my piece of code:
atomic {
for( ccaChecks = 0; ccaChecks 12000; ccaChecks++) {
if(call PacketIndicator.isReceiving()) {
return FALSE;
}
if(call EnergyIndicator.isReceiving()) {
detects++;
if(detects MIN_SAMPLES_BEFORE_DETECT) {
return FALSE;
}
}
}
}
12000 equals to 100msec sensing the channel for any potential sender. Can
someone please help me in making the right use of this thing, if there is
any.
BR
Wasif Masood
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] problem in avrora
Hi
In the link http://compilers.cs.ucla.edu/avrora/simulator.html the following
sample is avaialble
avrora simple.od
Avrora [Beta 1.6.0] - (c) 2003-2005 UCLA Compilers Group
This simulator and analysis tool is provided with absolutely no warranty,
either expressed or implied. It is provided to you with the hope that it be
useful for evaluation of and experimentation with microcontroller and sensor
network programs. For more information about the license that this software
is
provided to you under, specify the license option.
Loading simple.od...[OK: 0.928 seconds]
=={ Simulation events
}===
Node Time Event
--
==
*Simulated time: 166 cycles**
**Time for simulation: 0.475 seconds**
**Total throughput: 3.4947367E-4 mhz**
*
*
*
But
when i used the same i am not getting any results as such
*[r...@wsn2 mica2]# avrora radio.od*
Avrora [Beta 1.6.0] - (c) 2003-2005 UCLA Compilers Group
This simulator and analysis tool is provided with absolutely no warranty,
either expressed or implied. It is provided to you with the hope that it be
useful for evaluation of and experimentation with microcontroller and sensor
network programs. For more information about the license that this software
is
provided to you under, specify the license option.
Loading radio.od...[OK: 0.228 seconds]
=={ Simulation events
}===
Node Time Event
--
*[r...@wsn2 mica2]# avrora -action=simulate radio.od*
Avrora [Beta 1.6.0] - (c) 2003-2005 UCLA Compilers Group
This simulator and analysis tool is provided with absolutely no warranty,
either expressed or implied. It is provided to you with the hope that it be
useful for evaluation of and experimentation with microcontroller and sensor
network programs. For more information about the license that this software
is
provided to you under, specify the license option.
Loading radio.od...[OK: 0.146 seconds]
=={ Simulation events
}===
Node Time Event
--
[r...@wsn2 mica2]#
what can be done for that ?
Thanks in advance...
--
Regards,
S.Haripriya
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problem with PacketIndicator / EnergyIndicator interfaces
This same thing is used in BAMC with LPL_CHECKS of 400 which is merely
around 12-15msec, but this time is just to avoid congestion in the channel.
I think if this time is enhanced, it can also be used for what I mentioned.
shouldn't it be?
On Fri, Jan 7, 2011 at 12:43 PM, wasif masood rwmas...@gmail.com wrote:
I dont know whether its a technical issue with PacketIndicator /
EnergyIndicator interfaces or is there something I am doing wrong. I am
trying the following code to sense the channel before sending my packet. I
want to make sure that each sender reserve the time window before sending
something so as to avoid simultaneous transmissions of frames from 2
different senders ( this is unlike BMAC in which 2 transmitters can send
simultaneously as long as the transmissions dont collide and for that it
uses backoff timer). But unfortunately even after sensing the channel for
100 msec I am still having interventions between different transmissions
even though difference between each back-to-back sending within one
transmission window is from 8-20msec.
here is the my piece of code:
atomic {
for( ccaChecks = 0; ccaChecks 12000; ccaChecks++) {
if(call PacketIndicator.isReceiving()) {
return FALSE;
}
if(call EnergyIndicator.isReceiving()) {
detects++;
if(detects MIN_SAMPLES_BEFORE_DETECT) {
return FALSE;
}
}
}
}
12000 equals to 100msec sensing the channel for any potential sender. Can
someone please help me in making the right use of this thing, if there is
any.
BR
Wasif Masood
--
Wasif Masood
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Deluge T2 and netbsl
Hi to all!I've a TmoteConnect unit, and a TmoteSky moteconnectedto it.I can install a "normal" program through "netbsl" command. For example, the Blink app(previously compiled):[cygwin]$ make telosbreinstall netbsl,192.168.1.100:10001cpbuild/telosb/main.ihexbuild/telosb/main.ihex.out installing telosbbinary using netbsl/opt/tinyos-2.x/support/make/msp/netbsl192.168.1.100:10001 build/telosb/main.ihex.out --telosb-r -e -I -pUsing mote on port /dev/ttyUSB0.Mass erase.Invoking BSL.BSLversion 1.61, MCUdevice id f16c.Changing to 38400 baud.Program image /tmp/_dev_ttyUSB0, 2648 bytes.Invoking BSL.BSLversion 1.61, MCUdevice id f16c.Changing to 38400 baud.Program.Programmed 2680 bytes.Resetrm-f build/telosb/main.exe.out build/telosb/main.ihex.out[cygwin]It works OK.Then, I try the test/deluge/Blink appin a motewhich is connecteddirectly to the USB(COM15) of the PC:[cygwin]$ CFLAGS=-DDELUGE_BASESTATIONmake telosbreinstall bsl,14cpbuild/telosb/main.ihexbuild/telosb/main.ihex.out installing telosbbootloaderusing bsltos-bsl--telosb-c 14 -r -e -I -p C:/cygwin/opt/tinyos-2.x/tos/lib/tosboot/build/telosb/main.ihexMSP430 Bootstrap Loader Version: 1.39-telos-8Mass Erase...Transmit default password ...Invoking BSL...Transmit default password ...Current bootstrap loader version: 1.61 (Device ID: f16c)Changing baudrate to 38400 ...Program ...2118 bytes programmed.Reset device ... installing telosb binary using bsl (without mass erase)tos-bsl --telosb -c 14 -r -I -p build/telosb/main.ihex.outMSP430 Bootstrap Loader Version: 1.39-telos-8Invoking BSL...Transmit default password ...Current bootstrap loader version: 1.61 (Device ID: f16c)Changing baudrate to 38400 ...Program ...39616 bytes programmed.Reset device ...rm -f build/telosb/main.exe.out build/telosb/main.ihex.out[cygwin]It works OK too. (The three leds are on and then only the red one blinks).I want to program (via Ethernet) a mote conected to the Tmote Connect device.[cygwin]$ CFLAGS=-DDELUGE_BASESTATION make telosb reinstall netbsl,192.168.1.100:10001cp build/telosb/main.ihex build/telosb/main.ihex.out installing telosb bootloader using netbsl/opt/tinyos-2.x/support/make/msp/netbsl 192.168.1.100:10001 C:/cygwin/opt/tinyos-2.x/tos/lib/tosboot/build/telosb/main.ihex --telosb -r -e -I -pUsing mote on port /dev/ttyUSB0.Mass erase.Invoking BSL.BSL version 1.61, MCU device id f16c.Changing to 38400 baud.Program image /tmp/_dev_ttyUSB0, 2118 bytes.Invoking BSL.BSL version 1.61, MCU device id f16c.Changing to 38400 baud.Program.Programmed 2118 bytes.Reset installing telosb binary using netbsl (without mass erase)/opt/tinyos-2.x/support/make/msp/netbsl 192.168.1.100:10001 build/telosb/main.ihex.out --telosb -r -I -pUsing mote on port /dev/ttyUSB0.Program image /tmp/_dev_ttyUSB0, 39584 bytes.Invoking BSL.BSL version 1.61, MCU device id f16c.Changing to 38400 baud.Program.Programmed 39616 bytes.Resetrm -f build/telosb/main.exe.out build/telosb/main.ihex.out[cygwin]When I reboot the mote (by pressing the RESET button), the three leds are on, but afterwards no led blinks.Is there any way to program a remote sensor (via Tmote Connect) using Deluge protocol?Thank you very much!!Regards,Jose A.P.D. I've attached the "netbsl" and "netbsl.extra" files I'm using. I've changed line#29 of "netbsl.extra" from $(BOOTLOADER) -- $(BOOTLOADER_IMG)╔══╗║ José A. Tarifa Galisteo║║ Estudiante Ingeniería de Telecomunicación║ Escuela Superior de Ingenieros - U. Sevilla║ http://alumno.us.es/j/jostargal/╚══╝ netbsl Description: Binary data netbsl.extra Description: Binary data ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Deluge T2 and netbsl
Hi to all! I've a Tmote Connect unit, and a Tmote Sky mote connected to it. I can install a normal program through netbsl command. For example, the Blink app (previously compiled): [cygwin] $ make telosb reinstall netbsl,192.168.1.100:10001 cp build/telosb/main.ihex build/telosb/main.ihex.out installing telosb binary using netbsl /opt/tinyos-2.x/support/make/msp/netbsl 192.168.1.100:10001 build/telosb/main.ihex.out --telosb -r -e -I -p Using mote on port /dev/ttyUSB0. Mass erase. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program image /tmp/_dev_ttyUSB0, 2648 bytes. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program. Programmed 2680 bytes. Reset rm -f build/telosb/main.exe.out build/telosb/main.ihex.out [cygwin] It works OK. Then, I try the test/deluge/Blink app in a mote which is connected directly to the USB (COM15) of the PC: [cygwin] $ CFLAGS=-DDELUGE_BASESTATION make telosb reinstall bsl,14 cp build/telosb/main.ihex build/telosb/main.ihex.out installing telosb bootloader using bsl tos-bsl --telosb -c 14 -r -e -I -p C:/cygwin/opt/tinyos-2.x/tos/lib/tosboot/build/telosb/main.ihex MSP430 Bootstrap Loader Version: 1.39-telos-8 Mass Erase... Transmit default password ... Invoking BSL... Transmit default password ... Current bootstrap loader version: 1.61 (Device ID: f16c) Changing baudrate to 38400 ... Program ... 2118 bytes programmed. Reset device ... installing telosb binary using bsl (without mass erase) tos-bsl --telosb -c 14 -r -I -p build/telosb/main.ihex.out MSP430 Bootstrap Loader Version: 1.39-telos-8 Invoking BSL... Transmit default password ... Current bootstrap loader version: 1.61 (Device ID: f16c) Changing baudrate to 38400 ... Program ... 39616 bytes programmed. Reset device ... rm -f build/telosb/main.exe.out build/telosb/main.ihex.out [cygwin] It works OK too. (The three leds are on and then only the red one blinks). I want to program (via Ethernet) a mote conected to the Tmote Connect device. [cygwin] $ CFLAGS=-DDELUGE_BASESTATION make telosb reinstall netbsl,192.168.1.100:10001 cp build/telosb/main.ihex build/telosb/main.ihex.out installing telosb bootloader using netbsl /opt/tinyos-2.x/support/make/msp/netbsl 192.168.1.100:10001 C:/cygwin/opt/tinyos-2.x/tos/lib/tosboot/build/tel osb/main.ihex --telosb -r -e -I -p Using mote on port /dev/ttyUSB0. Mass erase. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program image /tmp/_dev_ttyUSB0, 2118 bytes. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program. Programmed 2118 bytes. Reset installing telosb binary using netbsl (without mass erase) /opt/tinyos-2.x/support/make/msp/netbsl 192.168.1.100:10001 build/telosb/main.ihex.out --telosb -r -I -p Using mote on port /dev/ttyUSB0. Program image /tmp/_dev_ttyUSB0, 39584 bytes. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program. Programmed 39616 bytes. Reset rm -f build/telosb/main.exe.out build/telosb/main.ihex.out [cygwin] When I reboot the mote (by pressing the RESET button), the three leds are on, but afterwards no led blinks. Is there any way to program a remote sensor (via Tmote Connect) using Deluge protocol? Thank you very much!! Regards, Jose A. P.D. netbsl and netbsl.extra files I'm using: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20110107/9e927f2d/attachment.obj https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20110107/9e927f2d/attachment-0001.obj I've changed line#29 of netbsl.extra from $(BOOTLOADER) -- $(BOOTLOADER_IMG) ╔══╗ ║José A. Tarifa Galisteo ║ ║ Estudiante Ingeniería de Telecomunicación ║ Escuela Superior de Ingenieros - U. Sevilla ║ http://alumno.us.es/j/jostargal/ ╚══╝ ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How can test 6LoWPAN and capture with wireshark 6LoWPAN packet
Dear Everyone, I want to see 6LoWPAN is implemented successful in TinyOS. So I am going to run some example of 6LoWPAN and capture with wireshark to analyze packet format. Does it has anyone know some good example, and how can capture with wireshark or other tools? If you know, pls help me some guides. Thank you very much, William ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
