Jisha Mary Jose | 21 Sep 17:09 2014
Picon

Help for generating attacks in tossim

Hi,

Can anyone please help me and tell me how to demonstrate an attack in tinyos ie in TOSSIM. I have to generate a pollution attack when we do network coding for dissemination of packets.

please help me... urgent...

Regards,

Jisha Mary Jose
......jMj......
<div><div dir="ltr">
<div class="gmail_default">Hi,<br><br>
</div>
<div class="gmail_default">Can anyone please help me and tell me how to demonstrate an attack in tinyos ie in TOSSIM. I have to generate a pollution attack when we do network coding for dissemination of packets. <br><br>please help me... urgent...<br><br clear="all">
</div>
<div><div dir="ltr">Regards,<br><br>Jisha Mary Jose<br>......jMj......</div></div>
</div></div>
Hamidreza Hosseini | 21 Sep 12:58 2014
Picon

multihop routing does not work almost always

Hi all,

I want to use multihop libraries on TelosB motes. I programmed motes with SurgeTelos app, but it does not work correctly almost always. 

I have two motes and a gateway. First I put the motes in a location that both of them could reach the gateway and messages of both of them was received by gateway.
Then I placed one of them in a further location. Its messages received by the one near to the gateway, but then near one did not forward received messages to gateway. But messages of the near one was received by gateway. 
I placed motes in various locations, but more than 90 percents of times, messages were not forwarded to gateway.
I also used different multihop libraries, but still did not work correctly.

Do anyone have any suggestion?


--
Regards,
Hamidreza Hosseini
<div><div dir="ltr">
<div>Hi all,</div>
<div><br></div>
<div>I want to use multihop libraries on TelosB motes. I programmed motes with SurgeTelos app, but it does not work correctly almost always.&nbsp;</div>
<div><br></div>
<div>I have two motes and a gateway. First I put the motes in a location that both of them could reach the gateway and messages of both of them was received by gateway.</div>
<div>Then I placed one of them in a further location. Its messages received by the one near to the gateway, but then near one did not forward received messages to gateway. But messages of the near one was received by gateway.&nbsp;</div>
<div>I placed motes in various locations, but more than 90 percents of times, messages were not forwarded to gateway.</div>
<div>I also used different multihop libraries, but still did not work correctly.<br>
</div>
<div><br></div>
<div>Do anyone have any suggestion?</div>
<br clear="all"><div><br></div>-- <br><div dir="ltr">Regards,<br>Hamidreza Hosseini<br>
</div>
</div></div>
Thanh Ngoc Dinh | 19 Sep 14:36 2014
Picon
Picon

tinyos compile error "multiple targets specified" make: *** [exe0] Error 2 pls help

Hello everyone,
I am testing the low power listening protocol using the TestNetworkLPL in tinyos-2.1.2 and tinyos-2.1.1. I used msp430-gcc version 4.7.0. However, i got a compile error "multiple targets specified". The detail of error is described below. Do you know why this error happens? and please advise me a way to solve the error. 
Thank you very much!!!

---- detail of compiling and error------------------

"
root <at> TinyOS:/opt/tinyos-2.1.2/apps/TestNetworkLpl$ make telosb oppxmac
/opt/tinyos-2.1.2/support/make/ident_flags.extra:13: warning: overriding commands for target `ident_cache'
../../support/make//ident_flags.extra:13: warning: ignoring old commands for target `ident_cache'
/opt/tinyos-2.1.2/support/make/tos_image.extra:8: warning: overriding commands for target `build_tosimage'
../../support/make//tos_image.extra:8: warning: ignoring old commands for target `build_tosimage'
../../support/make//msp/msp.rules:92: warning: overriding commands for target `setid'
../../support/make//msp/msp.rules:92: warning: ignoring old commands for target `setid'
../../support/make//msp/msp.rules:98: warning: overriding commands for target `tosimage'
../../support/make//msp/msp.rules:98: warning: ignoring old commands for target `tosimage'
../../support/make//msp/msp.rules:101: warning: overriding commands for target `ihex'
../../support/make//msp/msp.rules:101: warning: ignoring old commands for target `ihex'
../../support/make//msp/msp.rules:104: warning: overriding commands for target `exe'
../../support/make//msp/msp.rules:104: warning: ignoring old commands for target `exe'
../../support/make//msp/msp.rules:107: warning: overriding commands for target `exe0'
../../support/make//msp/msp.rules:107: warning: ignoring old commands for target `exe0'
../../support/make//msp/msp.rules:120: warning: overriding commands for target `builddir'
../../support/make//msp/msp.rules:120: warning: ignoring old commands for target `builddir'
../../support/make//msp/msp.rules:123: warning: overriding commands for target `bytes'
../../support/make//msp/msp.rules:123: warning: ignoring old commands for target `bytes'
/opt/tinyos-2.1.2/support/make/telosb.target:19: warning: overriding commands for target `telos'
../../support/make//telosb.target:19: warning: ignoring old commands for target `telos'
/opt/tinyos-2.1.2/support/make/telosb.target:22: warning: overriding commands for target `telosb'
../../support/make//telosb.target:22: warning: ignoring old commands for target `telosb'
mkdir -p build/telosb
    compiling TestNetworkLplAppC to a telosb binary
ncc -o build/telosb/main.exe  -Os -I../../tos/chips/cc2420 -I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/receive -I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/interfaces -I../../tos/chips/cc2420/opp -I../../tos/chips/cc2420/opp/debug -I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/dc -I../../tos/chips/cc2420/lpl  -I../../tos/chips/cc2420 -I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/receive -I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/interfaces -I../../tos/chips/cc2420/opp -I../../tos/chips/cc2420/opp/debug -I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/dc -I../../tos/chips/cc2420/lpl  -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x23 -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x23 -DLOW_POWER_LISTENING -DCC2420_NO_ADDRESS_RECOGNITION -DDELAY_AFTER_RECEIVE=30 -DNO_OPP_DEBUG -DLPL_DEF_LOCAL_WAKEUP=2048 -DLPL_DEF_REMOTE_WAKEUP=2048 -DTEST_NETWORK_PACKET_RATE=4096 -DIDENT_APPNAME=\"TestNetworkLplA\" -DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"instant-contiki\" -DIDENT_USERHASH=0x22a1ff22L -DIDENT_TIMESTAMP=0x541c1c1dL -DIDENT_UIDHASH=0xdc56cefcL -DIDENT_APPNAME=\"TestNetworkLplA\" -DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"instant-contiki\" -DIDENT_USERHASH=0x22a1ff22L -DIDENT_TIMESTAMP=0x541c1c1dL -DIDENT_UIDHASH=0xdc56cefcL  TestNetworkLplAppC.nc -lm 
multiple targets specified
make: *** [exe0] Error 2


"

Best regards,
William
<div><div dir="ltr">Hello everyone,<div>I am testing the low power listening protocol using the TestNetworkLPL in tinyos-2.1.2 and tinyos-2.1.1. I used msp430-gcc version 4.7.0. However, i got a compile error "multiple targets specified". The detail of error is described below. Do you know why this error happens? and please advise me a way to solve the error.&nbsp;</div>
<div>Thank you very much!!!</div>
<div><br></div>
<div>---- detail of compiling and error------------------</div>
<div><br></div>
<div>
<div>"</div>
<div>
<div>root <at> TinyOS:/opt/tinyos-2.1.2/apps/TestNetworkLpl$ make telosb oppxmac</div>
<div>/opt/tinyos-2.1.2/support/make/ident_flags.extra:13: warning: overriding commands for target `ident_cache'</div>
<div>../../support/make//ident_flags.extra:13: warning: ignoring old commands for target `ident_cache'</div>
<div>/opt/tinyos-2.1.2/support/make/tos_image.extra:8: warning: overriding commands for target `build_tosimage'</div>
<div>../../support/make//tos_image.extra:8: warning: ignoring old commands for target `build_tosimage'</div>
<div>../../support/make//msp/msp.rules:92: warning: overriding commands for target `setid'</div>
<div>../../support/make//msp/msp.rules:92: warning: ignoring old commands for target `setid'</div>
<div>../../support/make//msp/msp.rules:98: warning: overriding commands for target `tosimage'</div>
<div>../../support/make//msp/msp.rules:98: warning: ignoring old commands for target `tosimage'</div>
<div>../../support/make//msp/msp.rules:101: warning: overriding commands for target `ihex'</div>
<div>../../support/make//msp/msp.rules:101: warning: ignoring old commands for target `ihex'</div>
<div>../../support/make//msp/msp.rules:104: warning: overriding commands for target `exe'</div>
<div>../../support/make//msp/msp.rules:104: warning: ignoring old commands for target `exe'</div>
<div>../../support/make//msp/msp.rules:107: warning: overriding commands for target `exe0'</div>
<div>../../support/make//msp/msp.rules:107: warning: ignoring old commands for target `exe0'</div>
<div>../../support/make//msp/msp.rules:120: warning: overriding commands for target `builddir'</div>
<div>../../support/make//msp/msp.rules:120: warning: ignoring old commands for target `builddir'</div>
<div>../../support/make//msp/msp.rules:123: warning: overriding commands for target `bytes'</div>
<div>../../support/make//msp/msp.rules:123: warning: ignoring old commands for target `bytes'</div>
<div>/opt/tinyos-2.1.2/support/make/telosb.target:19: warning: overriding commands for target `telos'</div>
<div>../../support/make//telosb.target:19: warning: ignoring old commands for target `telos'</div>
<div>/opt/tinyos-2.1.2/support/make/telosb.target:22: warning: overriding commands for target `telosb'</div>
<div>../../support/make//telosb.target:22: warning: ignoring old commands for target `telosb'</div>
<div>mkdir -p build/telosb</div>
<div>&nbsp; &nbsp; compiling TestNetworkLplAppC to a telosb binary</div>
<div>ncc -o build/telosb/main.exe &nbsp;-Os -I../../tos/chips/cc2420 -I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/receive -I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/interfaces -I../../tos/chips/cc2420/opp -I../../tos/chips/cc2420/opp/debug -I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/dc -I../../tos/chips/cc2420/lpl &nbsp;-I../../tos/chips/cc2420 -I../../tos/chips/cc2420/csma -I../../tos/chips/cc2420/receive -I../../tos/chips/cc2420/transmit -I../../tos/chips/cc2420/interfaces -I../../tos/chips/cc2420/opp -I../../tos/chips/cc2420/opp/debug -I../../tos/chips/cc2420/unique -I../../tos/chips/cc2420/dc -I../../tos/chips/cc2420/lpl &nbsp;-fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x23 -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x23 -DLOW_POWER_LISTENING -DCC2420_NO_ADDRESS_RECOGNITION -DDELAY_AFTER_RECEIVE=30 -DNO_OPP_DEBUG -DLPL_DEF_LOCAL_WAKEUP=2048 -DLPL_DEF_REMOTE_WAKEUP=2048 -DTEST_NETWORK_PACKET_RATE=4096 -DIDENT_APPNAME=\"TestNetworkLplA\" -DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"instant-contiki\" -DIDENT_USERHASH=0x22a1ff22L -DIDENT_TIMESTAMP=0x541c1c1dL -DIDENT_UIDHASH=0xdc56cefcL -DIDENT_APPNAME=\"TestNetworkLplA\" -DIDENT_USERNAME=\"user\" -DIDENT_HOSTNAME=\"instant-contiki\" -DIDENT_USERHASH=0x22a1ff22L -DIDENT_TIMESTAMP=0x541c1c1dL -DIDENT_UIDHASH=0xdc56cefcL &nbsp;TestNetworkLplAppC.nc -lm&nbsp;</div>
<div>multiple targets specified</div>
<div>make: *** [exe0] Error 2</div>
<div><br></div>
</div>
<div><br></div>
<div>"</div>
</div>
<div><br></div>
<div>Best regards,</div>
<div>William</div>
</div></div>
Alex | 16 Sep 04:02 2014
Picon

Dose Blip use any encryption algorithm.


Hi, all

    I followed the instructions at the page http://tinyos.stanford.edu/tinyos-wiki/index.php/BLIP_Tutorial

    I used UDPEcho and IPBaseStation in tinyos 2.x with BLIP (I guess it is blip 1). The node and the base communicates, while a sniffer node is nearby. There is some data sniffer catched:

7E 42 FF FF 64 00 40 03 94 3A FF 00 64 A4 01 86 00 20 09 40 00 00 00 00 00 00 00 00 00 00 00 03 04 40 C0 00 27 8D 00 00 09 3A 80 00 00 00 00 FE C0 00 00 00 00 00 00 00 00 00 00 00 00 00 64 11 01 00 00 00 00 00 00 E3 00 BE F3 7E
7E 42 09 00 64 00 12 04 D4 40 00 64 00 09 80 D0 28 00 46 5C A3 68 65 6C 70 E3 00 BF 9D 7E
7E 42 64 00 09 00 1C 04 94 3C 41 00 09 00 64 11 0A 0A 08 C0 8C 0A 08 00 64 00 46 D0 28 00 0A 2B 7B 06 02 C5 00 58 C4 7E 

The above is 3 types of data catched. I tried to parse them, the result is below

7E 42 // Start flag and 42
FF FF 64 00 40 03 94 // Tinyos header, destination addr, source addr , length,  am type and group.
3A FF 00 64 A4 01 86 00 20 09 40 00 00 00 00 00 00 00 00 00 00 00 03 04 40 C0 00 27 8D 00 00 09 3A 80 00 00 00 00 
FE C0 00 00 00 00 00 00 00 00 00 00 00 00 00 64 11 01 00 00 00 00 00 00 E3 00 // the red letter are source IPv6 addr in full format.(it's wired I do not find destin)
BE F3 7E // crc and stop flag
(I configure it as a broadcast msg)
7E 42 // Start flag and 42
09 00 64 00 12 04 D4 // tinyos header
40 00 64 00 09 80 D0 28 00 46 5C A3 68 65 6C 70 E3 00 // the red letter are 70 in decimal which I opened as a UDP port
BF 9D 7E // crc and stop flag
(It is a request)
7E 42 // Start flag and 42
64 00 09 00 1C 04 94 // tinyos header
3C 41 00 09 00 64 11 0A 0A 08 C0 8C 0A 08 00 64 00 46 D0 28 00 0A 2B 7B 06 02 C5 00 // the red letter are my payload data.
58 C4 7E // crc and stop flag
(this is a answer)

I tried my best, and the above is all I could parse. What the other part mean? Is there any document? I had read some docs about 6lowpan which told me dispatch, next header, but I could not see any accordance with the packets I catched. Are they 6lowpan packets?

Another thing weird, when I pinged the node through base, the sniffer could catch nothing while ping6 got responses. Does blip use any encryption algorithm that make it impossible to parse?



    Anyone who knows about it?

--

Best regards,
Alex.






<div>
<div>
<div>
<div>
<br><div>Hi, all</div>
<div><br></div>
<div>&nbsp; &nbsp; I followed the instructions at the page&nbsp;http://tinyos.stanford.edu/tinyos-wiki/index.php/BLIP_Tutorial</div>
<div><br></div>
<div>&nbsp; &nbsp; I used UDPEcho and IPBaseStation in tinyos 2.x with BLIP (I guess it is blip 1). The node and the base communicates, while a sniffer node is nearby. There is some data sniffer catched:</div>
<div><br></div>
<div>
<div>7E 42 FF FF 64 00 40 03 94 3A FF 00 64 A4 01 86 00 20 09 40 00 00 00 00 00 00 00 00 00 00 00 03 04 40 C0 00 27 8D 00 00 09 3A 80 00 00 00 00 FE C0 00 00 00 00 00 00 00 00 00 00 00 00 00 64 11 01 00 00 00 00 00 00 E3 00 BE F3 7E</div>
<div>7E 42 09 00 64 00 12 04 D4 40 00 64 00 09 80 D0 28 00 46 5C A3 68 65 6C 70 E3 00 BF 9D 7E</div>
<div>7E 42 64 00 09 00 1C 04 94 3C 41 00 09 00 64 11 0A 0A 08 C0 8C 0A 08 00 64 00 46 D0 28 00 0A 2B 7B 06 02 C5 00 58 C4 7E&nbsp;</div>
</div>
<div><br></div>
<div><span>The above is 3 types of data catched. I tried to parse them, the result is below</span></div>
<div><br></div>
<div>7E 42 // Start flag and 42</div>
<div>
<span>FF FF</span><span> 64 00</span> <span>40</span> <span>03</span> 94 // Tinyos header, destination addr, source addr , length, &nbsp;am type and group.</div>
<div>3A FF 00 64 A4 01 86 00 20 09 40 00 00 00 00 00 00 00 00 00 00 00&nbsp;03 04 40 C0 00 27 8D 00 00 09 3A 80 00 00 00 00&nbsp;</div>
<div>
<span>FE C0 00 00 00 00 00 00 00 00 00 00 00 00 00 64</span> 11 01 00 00 00 00 00 00 E3 00 // the red letter are source IPv6 addr in full format.(it's wired I do not find destin)</div>
<div>BE F3 7E // crc and stop flag</div>
<div>(I configure it as a broadcast msg)</div>
<div>7E 42&nbsp;// Start flag and 42</div>
<div>09 00 64 00 12 04 D4&nbsp;// tinyos header</div>
<div>40 00 64 00 09 80 D0 28 <span>00 46 </span>5C A3 68 65 6C 70 E3 00 // the red letter are 70 in decimal which I opened as a UDP port</div>
<div>BF 9D 7E&nbsp;// crc and stop flag</div>
<div>(It is a request)</div>
<div>7E 42&nbsp;// Start flag and 42</div>
<div>64 00 09 00 1C 04 94 // tinyos header</div>
<div>3C 41 00 09 00 64 11 0A 0A 08 C0 8C 0A 08 00 64 00 46 D0 28 00 0A 2B 7B <span>06 02</span> C5 00 // the red letter are my payload data.</div>
<div>58 C4 7E&nbsp;// crc and stop flag</div>
<div>(this is a answer)</div>
<div><br></div>
<div>I tried my best, and the above is all I could parse. What the other part mean? Is there any document? I had read some docs about 6lowpan which told me dispatch, next header, but I could not see any accordance with the packets I catched. Are they 6lowpan packets?</div>
<div><br></div>
<div><div>Another thing weird, when I pinged the node through base, the sniffer could catch nothing while ping6 got responses. Does blip use any encryption algorithm that make it impossible to parse?</div></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div>&nbsp; &nbsp; Anyone who knows about it?</div>
<div><br></div>
<div>--<br><div><br></div>
<div>Best regards,</div>
<div>Alex.</div>
</div>
</div>
<br><br><span title="neteasefooter"><span><span title="neteasefooter"><span><a href="#" target="_blank"></a></span></span>
</span></span>
</div>
<br><br><span title="neteasefooter"><span><span title="neteasefooter"><span><a href="#" target="_blank"></a></span></span>
</span></span>
</div>
<br><br><span title="neteasefooter"><span><span title="neteasefooter"><span><a href="#" target="_blank"></a></span></span>
</span></span>
</div>
Roadstar Runner | 14 Sep 07:29 2014
Picon

Does anyone have a fix for a bug i reported in June ?


On Sat, Jun 7, 2014 at 7:03 PM, Roadstar Runner <redstripeva2 at gmail.com> wrote: > I am not sure if this is a bug, though certainly not the behavior i > expected. > i am using FcfsArbiterC to manage my resources. . > I currently have 2 modules using interfaces Resource and > ResourceRequested.If module# 2 calls Resource.request() after module #1 > calls Resource.request() but before module#1 is granted the resource, then > ResourceRequested.requested() is never signaled.
<div><div dir="ltr">
<br><div>On Sat, Jun 7, 2014 at 7:03 PM, Roadstar Runner &lt;<a href="https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help">redstripeva2 at gmail.com</a>&gt;
wrote:

&gt; I am not sure if this is a bug, though certainly not the behavior i
&gt; expected.
&gt; i am using FcfsArbiterC to manage my resources. .
&gt; I currently have 2 modules using interfaces Resource and
&gt; ResourceRequested.If module# 2 calls Resource.request() after module #1
&gt; calls Resource.request() but before module#1 is granted the resource, then
&gt; ResourceRequested.requested() is never signaled.</div>
</div></div>
Michael Andersen | 14 Sep 01:13 2014
Picon

Overriding include paths for goals

Hi

I am wanting to change the "printf.h" that is used by blip, but any PFLAGS include paths added in the foo.platform file in support/make/platforms/ appear after the include flags for the goals added in the application makefile, leading to them being ignored. How do I solve this in the correct way?

This is just a specific example of a more general question of how to add includes that are higher priority than those specified by extras like blip.

Thanks
Michael
<div><div dir="ltr">Hi<div><br></div>
<div>I am wanting to change the "printf.h" that is used by blip, but any PFLAGS include paths added in the foo.platform file in support/make/platforms/ appear after the include flags for the goals added in the application makefile, leading to them being ignored. How do I solve this in the correct way?</div>
<div><br></div>
<div>This is just a specific example of a more general question of how to add includes that are higher priority than those specified by extras like blip.</div>
<div><br></div>
<div>Thanks</div>
<div>Michael</div>
</div></div>
Brad Goold | 13 Sep 05:36 2014
Picon

AM timing amongst CTP


Hi,


I'm a research student and I am using TelosB motes and TinyOS to perform a localisation task.
I use the CTP protocol to route information back to a root node and then use the serial forwarder as a bridge between the WSN and a PC.
I use a 'target node' to send simple AM's to the static nodes which recieve this AM, retrieve the RSSI information and then use the CTP to route the information back to the root.
The problem I have is that I can only perform 1 to 2 beacons per second. The recieved packets at the PC are often missing a packet from a particular sensor.
So my questions (of limited knowledge I may add) are:
When sending simple AM's in conjunction with the CTP, do I need to do some sort of arbitration? Or is this included in the lower layers? Am I doing something really wrong?

Any advice or direction is greatly appreciated,

Regards,
Brad



--
Brad Goold
Phone: +61 413 955 125
Email: brad_goold <at> dodo.com.au



<div>
<br>
Hi, <br><br><br>
I'm a research student and I am using TelosB motes and TinyOS to perform a localisation task. <br>
I use the CTP protocol to route information back to a root node and then use the serial forwarder as a bridge between the WSN and a PC. <br>
I use a 'target node' to send simple AM's to the static nodes which recieve this AM, retrieve the RSSI information and then use the CTP to route the information back to the root. <br>
The problem I have is that I can only perform 1 to 2 beacons per second. The recieved packets at the PC are often missing a packet from a particular sensor. <br>
So my questions (of limited knowledge I may add) are: <br>
When sending simple AM's in conjunction with the CTP, do I need to do some sort of arbitration? Or is this included in the lower layers? Am I doing something really wrong? <br><br>
Any advice or direction is greatly appreciated, <br><br>
Regards, <br>
Brad<br><br><br><br><table cellspacing="0" cellpadding="0" width="100%"><tr>
<td>
-- <br>Brad Goold<br>Phone: +61 413 955 125<br>Email: <a href="mailto:brad_goold <at> dodo.com.au">brad_goold <at> dodo.com.au</a><br><br><br><br>
</td>
</tr></table>
</div>
Robert Clove | 12 Sep 08:09 2014
Picon

Tiny OS Error for TOOLS how to resolve

Hi All,

I was trying to run tinyos

I did the following steps

|sudo apt-get install build-essential openjdk-6-jdk openjdk-6-jre python2.7 python2.7-dev automake avarice avr-libc msp430-libc avrdudebinutils-avr binutils-msp430 gcc-avr gcc-msp430 gdb-avr gdb-msp430 subversion graphviz python-docutils git checkinstall


After that, i have downloaded/clone tinyos source code repository from githubgit clone https://github.com/tinyos/tinyos-main.git Then
git clone https://github.com/tinyos/nesc.git

Then

cd nesc/

./Bootstrap

./configure

make

sudo make install


then

cd ../tinyos-main


sudo nano .bashrc



export TOSROOT=”/home/pi/tinyos-main-master”
export TOSDIR=”$TOSROOT/tos”
export CLASSPATH=$CLASSPATH:$TOSROOT/support/sdk/java
export MAKERULES=”$TOSROOT/support/make/Makerules”
export PYTHONPATH=$PYTHONPATH:$TOSROOT/support/sdk/python

echo “setting up TinyOS on source path $TOSROOT”



source .bashrc


tinyos-main# source .bashrc
setting up TinyOS on source path /home/pi/tinyos-main-master

Then


cd apps/Blink/
:/home/pi/tinyos-main/apps/Blink# make telosb
../../support/make/Makerules:56:  Old TinyOS environment variables detected.

    This version of the TinyOS make system has deprecated the TOSDIR, TOSROOT,
    and MAKERULES environment variables. Generally, you shouldn't need
    environment variables with this version of the TinyOS make system, and if
    you are not using any older versions of TinyOS on your system you should
    delete these environment variables. If you wish to leave these variables
    but hide this warning, set the TINYOS_NO_DEPRECATION_WARNING environment
    variable. If you are looking to compile against a different TinyOS tree,
    configure the makefiles used when compiling, or setup an external TinyOS
    tree with additional source files, please visit
    https://github.com/tinyos/tinyos-main/blob/master/support/make/README.md
    for more information about the TinyOS make system.

/bin/bash: tos-ident-flags: command not found
../../support/make/Makerules:157: *** [ERROR] Your version of tinyos-tools is too old (<2.2.0).Please build and install the tinyos-tools in the tinyos-main/tools directory.  Stop.



I get the following error.

I mine os installed or not how should i verify?
<div><div dir="ltr">
<div>
<div>
<div>Hi All,<br><br>
</div>I was trying to run tinyos <br>
</div>
<br>
</div>I did the following steps<br><br>|sudo apt-get install build-essential openjdk-6-jdk openjdk-6-jre&nbsp;python2.7 python2.7-dev automake avarice avr-libc msp430-libc avrdudebinutils-avr binutils-msp430 gcc-avr gcc-msp430 gdb-avr gdb-msp430&nbsp;subversion graphviz python-docutils git checkinstall<br><br><br>After that, i have downloaded/clone tinyos source code repository&nbsp;from githubgit clone <a href="https://github.com/tinyos/tinyos-main.git" rel="nofollow">https://github.com/tinyos/tinyos-main.git</a>

Then<br><div>git clone <a href="https://github.com/tinyos/nesc.git" rel="nofollow">https://github.com/tinyos/nesc.git</a><br><br>Then<br><br><p>cd nesc/</p>
<p>./Bootstrap</p>
<p>./configure</p>
<p>make</p>
<p>sudo make install</p>
<p><br></p>
<p>then</p>
<p>cd ../tinyos-main</p>
<p><br>sudo&nbsp;nano .bashrc</p>
<p><br></p>
<p><br></p>
<p>export TOSROOT=&rdquo;/home/pi/tinyos-main-master&rdquo;<br>export TOSDIR=&rdquo;$TOSROOT/tos&rdquo;<br>export CLASSPATH=$CLASSPATH:$TOSROOT/support/sdk/java<br>export MAKERULES=&rdquo;$TOSROOT/support/make/Makerules&rdquo;<br>export PYTHONPATH=$PYTHONPATH:$TOSROOT/support/sdk/python</p>
<p>echo &ldquo;setting up TinyOS on source path $TOSROOT&rdquo;</p>
<p><br></p>
<p><br>source .bashrc</p>
<p><br></p>
<p>tinyos-main# source .bashrc<br>setting up TinyOS on source path /home/pi/tinyos-main-master<br></p>
<p>Then</p>
<p><br></p>
<p>cd apps/Blink/≤br>:/home/pi/tinyos-main/apps/Blink# make telosb<br>../../support/make/Makerules:56:&nbsp; Old TinyOS environment variables detected.<br><br>&nbsp;&nbsp;&nbsp; This version of the TinyOS make system has deprecated the TOSDIR, TOSROOT,<br>&nbsp;&nbsp;&nbsp; and MAKERULES environment variables. Generally, you shouldn't need<br>&nbsp;&nbsp;&nbsp; environment variables with this version of the TinyOS make system, and if<br>&nbsp;&nbsp;&nbsp; you are not using any older versions of TinyOS on your system you should<br>&nbsp;&nbsp;&nbsp; delete these environment variables. If you wish to leave these variables<br>&nbsp;&nbsp;&nbsp; but hide this warning, set the TINYOS_NO_DEPRECATION_WARNING environment<br>&nbsp;&nbsp;&nbsp; variable. If you are looking to compile against a different TinyOS tree,<br>&nbsp;&nbsp;&nbsp; configure the makefiles used when compiling, or setup an external TinyOS<br>&nbsp;&nbsp;&nbsp; tree with additional source files, please visit<br>&nbsp;&nbsp;&nbsp; <a href="https://github.com/tinyos/tinyos-main/blob/master/support/make/README.md">https://github.com/tinyos/tinyos-main/blob/master/support/make/README.md</a><br>&nbsp;&nbsp;&nbsp; for more information about the TinyOS make system.<br><br>/bin/bash: tos-ident-flags: command not found<br>../../support/make/Makerules:157: *** [ERROR] Your version of tinyos-tools is too old (&lt;2.2.0).Please build and install the tinyos-tools in the tinyos-main/tools directory.&nbsp; Stop.<br><br></p>
<br><br>I get the following error.<br><br>I mine os installed or not how should i verify?<br>
</div>
</div></div>
deepak khatri | 11 Sep 13:48 2014
Picon

Unrecognized packets in xsniffer

Hello all,

I am using testmts4200cctestM standrad code to test mts420 sensor using Xsniffer application. The sensor is interfaced with a micaz. Another micaz board is used as base and packets are extracted serially using Xsniffer. In the output i can see packets received in the log data but xsniffer is not able to recognize these packets. Can anybody help in understanding these packets.

Thank you
<div><div dir="ltr"><div class=""><div class=""><div dir="ltr">
<div>
<div>Hello all, <br><br>
</div>I
 am using testmts4200cctestM standrad code to test mts420 sensor using 
Xsniffer application. The sensor is interfaced with a micaz. Another 
micaz board is used as base and packets are extracted serially using 
Xsniffer. In the output i can see packets received in the log data but 
xsniffer is not able to recognize these packets. Can anybody help in 
understanding these packets.<br><br>
</div>Thank you</div></div></div></div></div>
Michiel Konstapel | 11 Sep 11:02 2014
Picon

PMM settings in msp430x5xx/cc430

In the CC430 User's Guide, I found the following:

25.2.4 Using Radio With Low-Power Modes
The radio works seamlessly in LPM0 to LPM2. To enable radio operation in LPM3 or LPM4, the
application must set the PMMHPMRE bit in the PMMCTL0 register of the PMM module to 1. This enables
the PMM to provide sufficient current while the radio is active.

The documentation only mentions PMMHPMRE in one other place, the PMMCTL0 register:

"Global high power module request enable. If the PMMHPMRE bit is set, any module is able to request the PMM
high-power mode."

It sounds like this bit should be set, at least on the CC430, and there doesn't seem to be a downside to not
setting it. Looks like the easiest place to add this would be in Msp430PmmP.nc, where the core voltage is set:

PMMCTL0_L = PMMHPMRE | (PMMCOREV0 * level);

Anyone have experience with this chip, and know if it's necessary/desirable to do this?

Kind regards,
Michiel

Omid S | 10 Sep 18:48 2014
Picon

pcb of mica2

Hi

How can I find pcb schematic of mica2?

Gmane