Faruk Baturalp Günay | 3 Feb 20:56 2013
Picon

problem

I'm a new beginer for tinyos and i bought some MAXFOR cm5000msp (similar with Telosb) motes.As i undermentioned i had a problem  in a simple helloworld application,in terminal.If you can help about this problem i'll be so pleased.Thank you from now.i look forward to your reply.

Kind regards,
Faruk

helloworldAppc.nc

configuration helloworldAppc
{
    //Do nothing
}
implementation
{
    components MainC;
    components LedsC;
     
    components helloworldc as App;
    //Wiring
    AppBoot -> MainC;
    AppLeds -> LedsC;
}



helloworldc.nc


module helloworldc
{
    uses interface Boot;
    uses interface Leds;
}
implementation
{
    void TurnOnLed()
{
    call Leds.led0On()
}

    event void Boot.booted()
    {
        TurnOnLed()
    }
}


Makefile

COMPONENT=helloworldAppc
include $(MAKERULES)







Terminal

Reference  Device           Description
---------- ---------------- ---------------------------------------------
FTVW8IUQ   /dev/ttyUSB0     FTDI MTM-CM5000MSP
baturalp <at> baturalp:~$ motelist
No devices found.
baturalp <at> baturalp:~$ motelist
Reference  Device           Description
---------- ---------------- ---------------------------------------------
FTVW8IUQ   /dev/ttyUSB0     FTDI MTM-CM5000MSP
baturalp <at> baturalp:~$ sudo chmod 666 /dev/ttyUSB0
[sudo] password for baturalp:
baturalp <at> baturalp:~$ cd workspace
baturalp <at> baturalp:~/workspace$ ls
BL1  Blip  helloWorld
baturalp <at> baturalp:~/workspace$ cd hel*
baturalp <at> baturalp:~/workspace/helloWorld$ ls
src  TinyOS_Plugin_Makefile
baturalp <at> baturalp:~/workspace/helloWorld$ ls
src  TinyOS_Plugin_Makefile
baturalp <at> baturalp:~/workspace/helloWorld$ cd src
baturalp <at> baturalp:~/workspace/helloWorld/src$ ls
helloworldAppc.nc  helloworldc.nc  Makefile
*************************THE PROBLEM IS HERE.................................(can it be related to MAXFOR model name? after we write after make command,if it is can you tell true command?)
baturalp <at> baturalp:~/workspace/helloWorld/src$ make telosb
make: *** No rule to make target `telosb'.  Stop.

<div><div>
<div>I'm a new beginer for tinyos and i bought some MAXFOR cm5000msp (similar with Telosb) motes.As i undermentioned i had a problem&nbsp; in a simple helloworld application,in terminal.If you can help about this problem i'll be so pleased.Thank you from now.i look forward to your reply.</div>
<div><br></div>
<div>Kind regards,</div>
<div>Faruk<br><br>helloworldAppc.nc<br><br>configuration helloworldAppc <br>{ <br>&nbsp;&nbsp;&nbsp; //Do nothing <br>} <br>implementation <br>{ <br>&nbsp;&nbsp;&nbsp; components MainC; <br>&nbsp;&nbsp;&nbsp;
 components LedsC; <br>&nbsp;&nbsp;&nbsp; &nbsp;<br>&nbsp;&nbsp;&nbsp; components helloworldc as App; <br>&nbsp;&nbsp;&nbsp; //Wiring <br>&nbsp;&nbsp;&nbsp; AppBoot -&gt; MainC; <br>&nbsp;&nbsp;&nbsp; AppLeds -&gt; LedsC; <br>}<br><br><br><br>helloworldc.nc<br><br><br>module helloworldc <br>{ <br>&nbsp;&nbsp;&nbsp; uses interface Boot; <br>&nbsp;&nbsp;&nbsp; uses interface Leds; <br>} <br>implementation <br>{ <br>&nbsp;&nbsp;&nbsp; void TurnOnLed() <br>{ <br>&nbsp;&nbsp;&nbsp; call Leds.led0On() <br>} <br><br>&nbsp;&nbsp;&nbsp; event void Boot.booted() <br>&nbsp;&nbsp;&nbsp; { <br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; TurnOnLed() <br>&nbsp;&nbsp;&nbsp; } <br>}<br><br><br>Makefile<br><br>COMPONENT=helloworldAppc <br>include $(MAKERULES)<br><br><br><br><br><br><br><br>Terminal<br><br>Reference&nbsp; Device&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description <br>---------- ---------------- ---------------------------------------------
 <br>FTVW8IUQ&nbsp;&nbsp; /dev/ttyUSB0&nbsp;&nbsp;&nbsp;&nbsp; FTDI MTM-CM5000MSP <br>baturalp <at> baturalp:~$ motelist <br>No devices found. <br>baturalp <at> baturalp:~$ motelist <br>Reference&nbsp; Device&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Description <br>---------- ---------------- --------------------------------------------- <br>FTVW8IUQ&nbsp;&nbsp; /dev/ttyUSB0&nbsp;&nbsp;&nbsp;&nbsp; FTDI MTM-CM5000MSP <br>baturalp <at> baturalp:~$ sudo chmod 666 /dev/ttyUSB0 <br>[sudo] password for baturalp: <br>baturalp <at> baturalp:~$ cd workspace <br>baturalp <at> baturalp:~/workspace$ ls <br>BL1&nbsp; Blip&nbsp; helloWorld <br>baturalp <at> baturalp:~/workspace$ cd hel* <br>baturalp <at> baturalp:~/workspace/helloWorld$ ls <br>src&nbsp; TinyOS_Plugin_Makefile <br>baturalp <at> baturalp:~/workspace/helloWorld$ ls <br>src&nbsp; TinyOS_Plugin_Makefile <br>baturalp <at> baturalp:~/workspace/helloWorld$ cd src <br>baturalp <at> baturalp:~/workspace/helloWorld/src$ ls
 <br>helloworldAppc.nc&nbsp; helloworldc.nc&nbsp; Makefile <br>*************************THE PROBLEM IS HERE.................................(can it be related to MAXFOR model name? after we write after make command,if it is can you tell true command?)<br>baturalp <at> baturalp:~/workspace/helloWorld/src$ make telosb <br>make: *** No rule to make target `telosb'.&nbsp; Stop. <br><br>
</div>
</div></div>
Swetha | 3 Feb 16:35 2013
Picon

packet delay calculation

hello all,

I am using tinyos 2.1.2 and telosB motes for multihop routing process.
In order to calculate packet delay in multi-hop transmission, I came up with two ways to calculate,

1- booting all the nodes at same time so that it would provide sort of time synchronisation,
  so by calculating the difference between send time  and received time will provide packet delay.

2- rather than time synchronisation, round trip delay [source to destination and destination to source(ACK)], by calculating the difference between send time and received time (both the timings are taken at the source) will provide round trip delay and by dividing with 2 it gives packet delay.


Is this good approach to calculate packet delay or is there any better approach? 

Swetha
swetha.p <at> aol.com
<div>hello all,
<div><br></div>

<div>I am using tinyos 2.1.2 and telosB motes for multihop routing process.</div>

<div>In order to calculate packet delay in multi-hop transmission, I came up with two ways to calculate,</div>

<div><br></div>

<div>1- booting all the nodes at same time so that it would provide sort of time synchronisation,</div>

<div>&nbsp; so by calculating the<span>&nbsp;difference between send time&nbsp;</span><span>&nbsp;and received time will provide packet delay.</span>
</div>

<div><span><br></span></div>

<div>
<span>2- rat</span>her than time synchronisation, round trip delay [source to destination and destination to source(ACK)], by calculating the difference between send time and received time (both the timings are taken at the source) will provide round trip delay and by dividing with 2<span>&nbsp;it gives packet delay.</span>
</div>

<div><span><br></span></div>

<div><span><br></span></div>

<div>Is this good approach to calculate packet delay or is there any better approach?<span>&nbsp;</span>
</div>

<div>
<br><div>Swetha<br>
swetha.p <at> aol.com<br>
</div>
</div>
</div>
Christopher Wilson | 3 Feb 03:36 2013

00b_Using_the_Repo instructions fail on checkout

I'm trying to figure out if the following line in 00b_Using_the_Repo doc is actually correct (and I'm
missing something), or is a typo?

git checkout -t up/master		# create a tracking branch.

Here's what happens when I try to follow the workflow perscribed in the doc:

[First, I forked the repo in github]

$ git clone git://github.com/FlyingCampDesign/tinyos-main.git tinyos-2.x
Cloning into 'tinyos-2.x'...
remote: Counting objects: 39119, done.
remote: Compressing objects: 100% (9688/9688), done.
remote: Total 39119 (delta 29065), reused 38823 (delta 28887)
Receiving objects: 100% (39119/39119), 30.68 MiB | 94 KiB/s, done.
Resolving deltas: 100% (29065/29065), done.
Checking out files: 100% (6110/6110), done.
$ cd tinyos-2.x/
$ git remote add up git://github.com/tinyos/tinyos-main
$ git fetch up
remote: Counting objects: 14, done.
remote: Compressing objects: 100% (1/1), done.
remote: Total 8 (delta 7), reused 8 (delta 7)
Unpacking objects: 100% (8/8), done.
From git://github.com/tinyos/tinyos-main
 * [new branch]      master     -> up/master
$ git branch
* master
$ git checkout -t up/master
fatal: A branch named 'master' already exists.

This fails because master branch already exists when I checked out the fork.  However, I'm not sure what this
line should actually read?  I'm assuming that the intention is to create a local branch that tracks the
tinyos-main(master) branch, but in that case I would assume that the line should be something like:

$ git checkout -t up/master-up

Anybody able to shed some insight into the workflow intended in the doc?

Thanks,
Chris
Christopher Wilson | 3 Feb 03:34 2013

Why is TinyOS split into tinyos-main and tinyos-release?

Why does the TinyOS organization on Github use two separate repositories for dev and release? 
(tinyos-main and tinyos-release)  Is there a reason why there isn't just a single repository that uses
branches and tags to record releases (instead of splitting them into a separate repo)?  Is there a
discussion available somewhere in the mailer archives that discusses the thinking behind the way the way
the TinyOS github org was structured (2 repos instead of 1)?

Thanks,
Chris
Gustavo Zanatta Bruno | 2 Feb 19:57 2013
Picon

Change packet before send to serial.

Do you have any examples where the content package is changed in the root node before being forwarded to the serial port?

--
Atenciosamente:
Gustavo Zanatta Bruno
<div><div dir="ltr">
<span>Do you have any examples where the content package is changed in the root node before being forwarded to the serial port?</span><div>
<br>-- <br><div>
Atenciosamente:</div>Gustavo Zanatta Bruno
</div>
</div></div>
Gustavo Zanatta Bruno | 2 Feb 19:53 2013
Picon

(no subject)

Do you have any examples where the content package is changed in the root node before being forwarded to the serial port?
--
Atenciosamente:
Gustavo Zanatta Bruno
<div><div dir="ltr">Do you have any examples where the content package is changed in the root node before being forwarded to the serial port?<br>-- <br><div>Atenciosamente:</div>Gustavo Zanatta Bruno
</div></div>
Eric Decker | 2 Feb 07:14 2013
Picon

Re: error make: *** [exe0] Error 1 in Blip2



On Fri, Feb 1, 2013 at 10:58 PM, Sheikh Jaaved <sheikh.jaaved <at> gmail.com> wrote:
hi Eric,
thanks for the reply i am using msp430-gcc (GCC) 4.6.3 20120301 tool chain on ubuntu 12.04 lts

where did you get it?

I tried compiling the same thing as you only mine worked.   I got the warnings but did not get the relocation errors that your compile showed.

my version of msp430-gcc is:

msp430-gcc (GCC) 4.6.3 20120301 (mspgcc LTS 20120406 unpatched)


I beleive what is happening is you're running out of ROM.   I beleive some changes were made to get PppRouter to fit in the 48K of the telosb ROM.

So you should move onto the development trunk where this has been fixed.

You will need GIT.

apt-get install

mkdir ~/w
cd ~w
git clone git://github.com/tinyos/tinyos-main.git

you will have a git remote called origin pointing at tinyos/tinyos-main branch master
A local working copy will exist in ~/w/tinyos-main

You will have to tweak your environment variables to reflect.

More details about using the repository is located at

https://github.com/tinyos/tinyos-main/blob/master/doc/00a_Getting_Started

https://github.com/tinyos/tinyos-main/blob/master/doc/00b_Using_the_Repo

 

On Sat, Feb 2, 2013 at 7:23 AM, Eric Decker <cire831 <at> gmail.com> wrote:

What toolchain are you using?

do:

msp430-gcc --version

On Fri, Feb 1, 2013 at 2:21 AM, Sheikh Jaaved <sheikh.jaaved <at> gmail.com> wrote:

hi all,
i am just trying to run the blip using the tutorials from tinyos and getting the foloing error and i am unable to compile the program any help will be appreciated.


make telosb blip
mkdir -p build/telosb
    compiling PppRouterC to a telosb binary
ncc -o build/telosb/main.exe  -Os -DRPL_ROUTING -DRPL_STORING_MODE -I/opt/tinyos-2.1.2/tos/lib/net/rpl -I/opt/tinyos-2.1.2/tos/lib/ppp -I/opt/tinyos-2.1.2/tos/lib/fragpool -DPPP_HDLC_RX_FRAME_LIMIT=1 -DPPP_HDLC_TX_FRAME_LIMIT=8 -DIN6_PREFIX=\"fec0::\" -DBLIP_DERIVE_SHORTADDRS -DCC2420_HW_ACKNOWLEDGEMENTS  -DCC2420_HW_ADDRESS_RECOGNITION -DPACKET_LINK -DTOSH_DATA_LENGTH=112 -I/opt/tinyos-2.1.2/tos/lib/net/ -I/opt/tinyos-2.1.2/tos/lib/printf/ -I/opt/tinyos-2.1.2/support/sdk/c/blip/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/interfaces/  -I/opt/tinyos-2.1.2/tos/lib/net/blip/nwprog/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/shell/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/serial/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/platform/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/icmp/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/dhcp/ /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/iovec.c /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/in_cksum.c /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/ip_malloc.c /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/utility.c /opt/tinyos-2.1.2/tos/lib/net/blip/table.c -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"PppRouterC\" -DIDENT_USERNAME=\"jaaved\" -DIDENT_HOSTNAME=\"jaaved-HP-Pavil\" -DIDENT_USERHASH=0x3f9ae3f0L -DIDENT_TIMESTAMP=0x510b8747L -DIDENT_UIDHASH=0xa8e0b043L  PppRouterC.nc -lm 
/opt/tinyos-2.1.2/tos/platforms/telosa/PlatformHdlcUartC.nc:40:2: warning: #warning Enabling DMA on UART1RX
/opt/tinyos-2.1.2/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"
/opt/tinyos-2.1.2/tos/chips/cc2420/link/PacketLinkC.nc:38:2: warning: #warning "*** USING PACKET LINK LAYER"
/opt/tinyos-2.1.2/tos/lib/net/blip/shell/UDPShellP.nc:260: warning: call via function pointer
/opt/tinyos-2.1.2/tos/platforms/telosa/PlatformHdlcUartP.nc:181: warning: `HdlcUart.receivedByte' called asynchronously from `UsartInterrupts.rxDone'
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLDAORoutingEngineP.nc: In function ‘RPLDAORoutingEngineP__0__sendDAO__runTask’:
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLDAORoutingEngineP.nc:114:22: warning: variable ‘dao’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLRoutingEngineP.nc: In function ‘RPLRoutingEngineP__0__sendDIOTask__runTask’:
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLRoutingEngineP.nc:176:21: warning: variable ‘body’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLOF0P.nc: In function ‘RPLOF0P__RPLOF__recalculateRank’:
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLOF0P.nc:101:12: warning: variable ‘prevRank’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLOF0P.nc:101:12: warning: variable ‘prevEtx’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLRankP.nc: In function ‘RPLRankP__parseDIO’:
/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLRankP.nc:618:12: warning: variable ‘preRank’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/chips/msp430/dma/HplMsp430DmaXP.nc: In function ‘HplMsp430DmaXP__2__DMA__setState’:
/opt/tinyos-2.1.2/tos/chips/msp430/dma/HplMsp430DmaXP.nc:220:25: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/opt/tinyos-2.1.2/tos/chips/msp430/dma/HplMsp430DmaXP.nc:220:25: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/opt/tinyos-2.1.2/tos/lib/ppp/PppP.nc: In function ‘PppP__processError_task__runTask’:
/opt/tinyos-2.1.2/tos/lib/ppp/PppP.nc:413:16: warning: variable ‘ifd’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/lib/ppp/PppP.nc:412:15: warning: variable ‘in_frame_error’ set but not used [-Wunused-but-set-variable]
PppRouterP.nc: In function ‘PppRouterP__Boot__booted’:
PppRouterP.nc:57:11: warning: variable ‘rc’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/lib/net/blip/IPForwardingEngineP.nc: In function ‘IPForwardingEngineP__IPForward__recv’:
/opt/tinyos-2.1.2/tos/lib/net/blip/IPForwardingEngineP.nc:253:15: warning: variable ‘next_hop_key’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/lib/ppp/LcpAutomatonP.nc: In function ‘LcpAutomatonP__1__processEventActions_’:
/opt/tinyos-2.1.2/tos/lib/ppp/LcpAutomatonP.nc:543:81: warning: variable ‘in_actions’ set but not used [-Wunused-but-set-variable]
/opt/tinyos-2.1.2/tos/lib/ppp/LcpAutomatonP.nc: In function ‘LcpAutomatonP__0__processEventActions_’:
/opt/tinyos-2.1.2/tos/lib/ppp/LcpAutomatonP.nc:543:93: warning: variable ‘in_actions’ set but not used [-Wunused-but-set-variable]
/usr/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: build/telosb/main.exe section `.text' will not fit in region `rom'
/usr/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: section .vectors loaded at [0000ffe0,0000ffff] overlaps section .text loaded at [00004000,00010013]
/usr/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: region `rom' overflowed by 906 bytes
/usr/bin/../lib/gcc/msp430/4.6.3/mmpy-16/libcrt0.a(_copy_data.o): In function `__do_copy_data':
/home/cire/mm/w/tinyos-main.git/tinyos-2.x/packaging/msp430-46/gcc-4.6.3/build/gcc/../../gcc/config/msp430/crt0.S:195: relocation truncated to fit: R_MSP430_16_BYTE against symbol `__data_load_start' defined in *ABS* section in build/telosb/main.exe
/tmp/ccfrkCd8.o: In function `LcpAutomatonP__1__calculateEventActions_':
app.c:(.text+0x4f2): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
/tmp/ccfrkCd8.o: In function `LcpAutomatonP__0__calculateEventActions_':
app.c:(.text+0x89c): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
/tmp/ccfrkCd8.o: In function `IPDispatchP__lowpan_recon_start':
app.c:(.text+0x16f8): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
/tmp/ccfrkCd8.o: In function `UDPShellP__action_help':
app.c:(.text+0x406e): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
/tmp/ccfrkCd8.o: In function `UDPShellP__action_uptime':
app.c:(.text+0x432e): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
/tmp/ccfrkCd8.o: In function `IPForwardingEngineP__IPForward__recv.isra.315':
app.c:(.text+0x4f96): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
app.c:(.text+0x4fba): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
app.c:(.text+0x4ff8): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
app.c:(.text+0x5034): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'
/tmp/ccfrkCd8.o: In function `HdlcFramingP__0__HdlcUart__receivedByte':
app.c:(.text+0x5e3e): additional relocation overflows omitted from the output
collect2: ld returned 1 exit status
make: *** [exe0] Error 1


thanks in advance 

 
--
Regards
Sheikh Jaaved Hassan

_______________________________________________
Tinyos-help mailing list
Tinyos-help <at> millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help



--
Eric B. Decker
Senior (over 50 :-) Researcher




--
Regards
Sheikh Jaaved Hassan



--
Eric B. Decker
Senior (over 50 :-) Researcher

<div>
<br><br><div class="gmail_quote">On Fri, Feb 1, 2013 at 10:58 PM, Sheikh Jaaved <span dir="ltr">&lt;<a href="mailto:sheikh.jaaved <at> gmail.com" target="_blank">sheikh.jaaved <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
hi Eric,<div>thanks for the reply i am using&nbsp;msp430-gcc (GCC) 4.6.3 20120301 tool chain on ubuntu 12.04 lts<br>
</div>
</blockquote>
<div>
<br>where did you get it?<br><br>I tried compiling the same thing as you only mine worked. &nbsp; I got the warnings but did not get the relocation errors that your compile showed.<br><br>my version of msp430-gcc is:<br><br>msp430-gcc (GCC) 4.6.3 20120301 (mspgcc LTS 20120406 unpatched)<br><br><br>I beleive what is happening is you're running out of ROM.&nbsp;&nbsp; I beleive some changes were made to get PppRouter to fit in the 48K of the telosb ROM.<br><br>So you should move onto the development trunk where this has been fixed.<br><br>You will need GIT.<br><br>apt-get install <br><br>mkdir ~/w<br>cd ~w<br>git clone git://<a href="http://github.com/tinyos/tinyos-main.git">github.com/tinyos/tinyos-main.git</a><br><br>you will have a git remote called origin pointing at tinyos/tinyos-main branch master<br>A local working copy will exist in ~/w/tinyos-main<br><br>You will have to tweak your environment variables to reflect.<br><br>More details about using the repository is located at <br><br><a href="https://github.com/tinyos/tinyos-main/blob/master/doc/00a_Getting_Started">https://github.com/tinyos/tinyos-main/blob/master/doc/00a_Getting_Started</a><br><br><a href="https://github.com/tinyos/tinyos-main/blob/master/doc/00b_Using_the_Repo">https://github.com/tinyos/tinyos-main/blob/master/doc/00b_Using_the_Repo</a><br><br>&nbsp;<br>
</div>
<blockquote class="gmail_quote">
<div>
<br><div class="gmail_quote">On Sat, Feb 2, 2013 at 7:23 AM, Eric Decker <span dir="ltr">&lt;<a href="mailto:cire831 <at> gmail.com" target="_blank">cire831 <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<br>What toolchain are you using?<br><br>do:<br><br>msp430-gcc --version<br><br><div class="gmail_quote">
<div><div>
On Fri, Feb 1, 2013 at 2:21 AM, Sheikh Jaaved <span dir="ltr">&lt;<a href="mailto:sheikh.jaaved <at> gmail.com" target="_blank">sheikh.jaaved <at> gmail.com</a>&gt;</span> wrote:<br>
</div></div>
<blockquote class="gmail_quote">
<div><div>
<br clear="all"><div>hi all,</div>
<div>i am just trying to run the blip using the tutorials from tinyos and getting the foloing error and i am unable to compile the program any help will be&nbsp;appreciated.</div>

<div><br></div>
<div><br></div>
<div>
<div><span>make telosb blip</span></div>
<div><span>mkdir -p build/telosb</span></div>
<div><span>&nbsp; &nbsp; compiling PppRouterC to a telosb binary</span></div>
<div><span>ncc -o build/telosb/main.exe &nbsp;-Os -DRPL_ROUTING -DRPL_STORING_MODE -I/opt/tinyos-2.1.2/tos/lib/net/rpl -I/opt/tinyos-2.1.2/tos/lib/ppp -I/opt/tinyos-2.1.2/tos/lib/fragpool -DPPP_HDLC_RX_FRAME_LIMIT=1 -DPPP_HDLC_TX_FRAME_LIMIT=8 -DIN6_PREFIX=\"fec0::\" -DBLIP_DERIVE_SHORTADDRS -DCC2420_HW_ACKNOWLEDGEMENTS &nbsp;-DCC2420_HW_ADDRESS_RECOGNITION -DPACKET_LINK -DTOSH_DATA_LENGTH=112 -I/opt/tinyos-2.1.2/tos/lib/net/ -I/opt/tinyos-2.1.2/tos/lib/printf/ -I/opt/tinyos-2.1.2/support/sdk/c/blip/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/interfaces/ &nbsp;-I/opt/tinyos-2.1.2/tos/lib/net/blip/nwprog/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/shell/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/serial/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/platform/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/icmp/ -I/opt/tinyos-2.1.2/tos/lib/net/blip/dhcp/ /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/iovec.c /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/in_cksum.c /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/ip_malloc.c /opt/tinyos-2.1.2/support/sdk/c/blip/lib6lowpan/utility.c /opt/tinyos-2.1.2/tos/lib/net/blip/table.c -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"PppRouterC\" -DIDENT_USERNAME=\"jaaved\" -DIDENT_HOSTNAME=\"jaaved-HP-Pavil\" -DIDENT_USERHASH=0x3f9ae3f0L -DIDENT_TIMESTAMP=0x510b8747L -DIDENT_UIDHASH=0xa8e0b043L &nbsp;PppRouterC.nc -lm&nbsp;</span></div>

<div><span>/opt/tinyos-2.1.2/tos/platforms/telosa/PlatformHdlcUartC.nc:40:2: warning: #warning Enabling DMA on UART1RX</span></div>
<div><span>/opt/tinyos-2.1.2/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning "*** LOW POWER COMMUNICATIONS DISABLED ***"</span></div>

<div><span>/opt/tinyos-2.1.2/tos/chips/cc2420/link/PacketLinkC.nc:38:2: warning: #warning "*** USING PACKET LINK LAYER"</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/net/blip/shell/UDPShellP.nc:260: warning: call via function pointer</span></div>

<div><span>/opt/tinyos-2.1.2/tos/platforms/telosa/PlatformHdlcUartP.nc:181: warning: `HdlcUart.receivedByte' called asynchronously from `UsartInterrupts.rxDone'</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLDAORoutingEngineP.nc: In function &lsquo;RPLDAORoutingEngineP__0__sendDAO__runTask&rsquo;:</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLDAORoutingEngineP.nc:114:22: warning: variable &lsquo;dao&rsquo; set but not used [-Wunused-but-set-variable]</span></div>

<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLRoutingEngineP.nc: In function &lsquo;RPLRoutingEngineP__0__sendDIOTask__runTask&rsquo;:</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLRoutingEngineP.nc:176:21: warning: variable &lsquo;body&rsquo; set but not used [-Wunused-but-set-variable]</span></div>

<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLOF0P.nc: In function &lsquo;RPLOF0P__RPLOF__recalculateRank&rsquo;:</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLOF0P.nc:101:12: warning: variable &lsquo;prevRank&rsquo; set but not used [-Wunused-but-set-variable]</span></div>

<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLOF0P.nc:101:12: warning: variable &lsquo;prevEtx&rsquo; set but not used [-Wunused-but-set-variable]</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLRankP.nc: In function &lsquo;RPLRankP__parseDIO&rsquo;:</span></div>

<div><span>/opt/tinyos-2.1.2/tos/lib/net/rpl/RPLRankP.nc:618:12: warning: variable &lsquo;preRank&rsquo; set but not used [-Wunused-but-set-variable]</span></div>
<div><span>/opt/tinyos-2.1.2/tos/chips/msp430/dma/HplMsp430DmaXP.nc: In function &lsquo;HplMsp430DmaXP__2__DMA__setState&rsquo;:</span></div>

<div><span>/opt/tinyos-2.1.2/tos/chips/msp430/dma/HplMsp430DmaXP.nc:220:25: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]</span></div>
<div><span>/opt/tinyos-2.1.2/tos/chips/msp430/dma/HplMsp430DmaXP.nc:220:25: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/ppp/PppP.nc: In function &lsquo;PppP__processError_task__runTask&rsquo;:</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/ppp/PppP.nc:413:16: warning: variable &lsquo;ifd&rsquo; set but not used [-Wunused-but-set-variable]</span></div>

<div><span>/opt/tinyos-2.1.2/tos/lib/ppp/PppP.nc:412:15: warning: variable &lsquo;in_frame_error&rsquo; set but not used [-Wunused-but-set-variable]</span></div>
<div><span>PppRouterP.nc: In function &lsquo;PppRouterP__Boot__booted&rsquo;:</span></div>

<div><span>PppRouterP.nc:57:11: warning: variable &lsquo;rc&rsquo; set but not used [-Wunused-but-set-variable]</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/net/blip/IPForwardingEngineP.nc: In function &lsquo;IPForwardingEngineP__IPForward__recv&rsquo;:</span></div>

<div><span>/opt/tinyos-2.1.2/tos/lib/net/blip/IPForwardingEngineP.nc:253:15: warning: variable &lsquo;next_hop_key&rsquo; set but not used [-Wunused-but-set-variable]</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/ppp/LcpAutomatonP.nc: In function &lsquo;LcpAutomatonP__1__processEventActions_&rsquo;:</span></div>

<div><span>/opt/tinyos-2.1.2/tos/lib/ppp/LcpAutomatonP.nc:543:81: warning: variable &lsquo;in_actions&rsquo; set but not used [-Wunused-but-set-variable]</span></div>
<div><span>/opt/tinyos-2.1.2/tos/lib/ppp/LcpAutomatonP.nc: In function &lsquo;LcpAutomatonP__0__processEventActions_&rsquo;:</span></div>

<div><span>/opt/tinyos-2.1.2/tos/lib/ppp/LcpAutomatonP.nc:543:93: warning: variable &lsquo;in_actions&rsquo; set but not used [-Wunused-but-set-variable]</span></div>
<div><span>/usr/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: build/telosb/main.exe section `.text' will not fit in region `rom'</span></div>

<div><span>/usr/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: section .vectors loaded at [0000ffe0,0000ffff] overlaps section .text loaded at [00004000,00010013]</span></div>
<div><span>/usr/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: region `rom' overflowed by 906 bytes</span></div>
<div><span>/usr/bin/../lib/gcc/msp430/4.6.3/mmpy-16/libcrt0.a(_copy_data.o): In function `__do_copy_data':</span></div>

<div><span>/home/cire/mm/w/tinyos-main.git/tinyos-2.x/packaging/msp430-46/gcc-4.6.3/build/gcc/../../gcc/config/msp430/crt0.S:195: relocation truncated to fit: R_MSP430_16_BYTE against symbol `__data_load_start' defined in *ABS* section in build/telosb/main.exe</span></div>

<div><span>/tmp/ccfrkCd8.o: In function `LcpAutomatonP__1__calculateEventActions_':</span></div>
<div><span>app.c:(.text+0x4f2): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>

<div><span>/tmp/ccfrkCd8.o: In function `LcpAutomatonP__0__calculateEventActions_':</span></div>
<div><span>app.c:(.text+0x89c): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>

<div><span>/tmp/ccfrkCd8.o: In function `IPDispatchP__lowpan_recon_start':</span></div>
<div><span>app.c:(.text+0x16f8): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>
<div><span>/tmp/ccfrkCd8.o: In function `UDPShellP__action_help':</span></div>
<div><span>app.c:(.text+0x406e): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>
<div><span>/tmp/ccfrkCd8.o: In function `UDPShellP__action_uptime':</span></div>
<div><span>app.c:(.text+0x432e): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>
<div><span>/tmp/ccfrkCd8.o: In function `IPForwardingEngineP__IPForward__recv.isra.315':</span></div>
<div><span>app.c:(.text+0x4f96): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>

<div><span>app.c:(.text+0x4fba): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>
<div><span>app.c:(.text+0x4ff8): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>

<div><span>app.c:(.text+0x5034): relocation truncated to fit: R_MSP430_16_BYTE against `no symbol'</span></div>
<div><span>/tmp/ccfrkCd8.o: In function `HdlcFramingP__0__HdlcUart__receivedByte':</span></div>

<div><span>app.c:(.text+0x5e3e): additional relocation overflows omitted from the output</span></div>
<div><span>collect2: ld returned 1 exit status</span></div>
<div><span>make: *** [exe0] Error 1</span></div>
</div>
<div><span><br></span></div>
<div><span><br></span></div>
<div><span>thanks in advance&nbsp;</span></div>
<span><div><br></div>
<div>&nbsp;</div>
-- <br>Regards<div>Sheikh<span></span> Jaaved Hassan</div>
</span><br>
</div></div>_______________________________________________<br>
Tinyos-help mailing list<br><a href="mailto:Tinyos-help <at> millennium.berkeley.edu" target="_blank">Tinyos-help <at> millennium.berkeley.edu</a><br><a href="https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help" target="_blank">https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help</a><span><br></span>
</blockquote>
</div>
<span><br><br clear="all"><span class="HOEnZb"><br>
-- <br>Eric B. Decker<br>Senior (over 50 :-) Researcher<br><br></span></span>
</blockquote>
</div>
<span class="HOEnZb"><br><br clear="all"><div><br></div>-- <br>Regards<div>Sheikh<span></span> Jaaved Hassan</div>
</span>
</div>
</blockquote>
</div>
<br><br clear="all"><br>-- <br>Eric B. Decker<br>Senior (over 50 :-) Researcher<br><br>
</div>
Electronics Pub | 31 Jan 12:12 2013

Re: HELP AODV implementation

Hi,

Sorry I have no expirience with that. you might ask you question from tinyos mailing list:

tinyos-help <at> millennium.berkeley.edu



On 31-1-2013 7:21 AM, - wrote:
SENDER: BALAJI EMAIL: balajigupta.s1231 <at> gmail.com SUBJECT: HELP AODV implementation IP: 115.248.50.22 MESSAGE: Iam a final year student doing my project on TINY OS AODV implementation in telosb.Can u Please send me the source code of that to my mail id and hoping that you will reply soon...

<div>
    Hi,<br><br>
    Sorry I have no expirience with that. you might ask you question
    from tinyos mailing list:<br><br><a class="moz-txt-link-abbreviated" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a><br><br><br><br><div class="moz-cite-prefix">On 31-1-2013 7:21 AM, - wrote:<br>
</div>
    <blockquote cite="mid:20130131062131.6713F1F3126 <at> mailsa1.servage.net" type="cite">
      SENDER: BALAJI 

EMAIL: <a class="moz-txt-link-abbreviated" href="mailto:balajigupta.s1231 <at> gmail.com">balajigupta.s1231 <at> gmail.com</a> 

SUBJECT: HELP AODV implementation 

IP: 115.248.50.22 

MESSAGE: 

Iam a final year student doing my project  
on TINY OS AODV implementation in 
telosb.Can u Please send me the source 
code of that to my mail id and hoping that 
you will reply soon...        

    </blockquote>
    <br>
</div>
IPSN'13 Publicity | 30 Jan 07:26 2013
Picon

IPSN'13: CALL FOR DEMOS AND POSTERS

The 12th International Conference on Information Processing in Sensor Networks (IPSN 2013) draws upon
many disciplines including networking, signal and image processing, information and coding theory,
databases, information management, distributed algorithms, embedded systems, wireless
communications, and machine learning. In addition to full-length technical papers, IPSN welcomes
exciting demonstrations of novel sensor network technology, applications, and hardware as well as
posters showing promising early work. IPSN seeks participation from both industry and academia for
demos and posters. 

Selection of demos and posters will be based on a short abstract, evaluated based on technical merit and
innovation as well as the potential to stimulate interesting discussions and exchange of ideas at the
conference. Accepted abstracts will appear in the regular conference proceedings. The poster and demo
submission does not distinguish between the IP track and the SPOTS track; submissions of interest to both
tracks are welcome. At least one author of every accepted demo or poster abstract is required to attend the
conference. 

Abstracts should be at most 2 pages in length, and submitted in PDF format by following the IPSN
regular-paper formatting guidelines. Abstract need not be anonymous. Please refer to the IPSN
regular-paper submission instructions for other details.

DEMOS

Demo abstracts should describe both the technology being showcased as well as the user experience of the
demo. Tables, power, and wireless connectivity will be provided. If a demonstration requires
additional special arrangements, please describe them clearly in your submission. 

If you have any questions, please contact the IPSN 2013 demo chair: Luca Mottola (luca.mottola <at> polimi.it).

POSTERS

Poster abstracts should report on research work where at least some preliminary results are available,
but they need not necessarily describe completed work. An easel will be provided for all posters. 

If you have any questions, please contact the IPSN 2013 poster chair: Tian He (tianhe <at> cs.umn.edu).

SUBMISSION

Submissions will be handled via e-mail. 

For demos, please send your PDF submission to Luca Mottola (luca.mottola <at> polimi.it) with subject line
"IPSN13 Demo Submission". 

For posters, please send your PDF to Tian He (tianhe <at> cs.umn.edu) with subject line "IPSN13 Poster
Submission". 

Messages not adhering to the above guidelines will not be considered. Every submission will be
individually acknowledged by the respective chairs.

IMPORTANT DATES

Poster and demo submission deadline:	 February 4th, 2013
Notification of acceptance:	February 15th, 2013
Camera-ready abstracts due:	February 18th, 2013

############################

To unsubscribe from the SENSORNET list:
write to: mailto:SENSORNET-SIGNOFF-REQUEST <at> LISTSERV.ACM.ORG
or click the following link:
http://listserv.acm.org/scripts/wa-ACMLPX.exe?SUBED1=SENSORNET&A=1

Alpha Gama | 30 Jan 10:26 2013
Picon

ticks to seconds

Hi all,
I want to simulate my protocol during 30 mn, so please what have I to put in this line of the test file :  while (t.time() < 600 * t.ticksPerSecond()) 
Thank you 

<div><div>
<div>Hi all,</div>
<div>I want to simulate my protocol during 30 mn, so please what have I to put in this line of the test file :&nbsp;<span class="Apple-tab-span">	</span>while (t.time() &lt; 600 * t.ticksPerSecond())&nbsp;</div>
<div>Thank you&nbsp;</div>
<div><span><br></span></div>
</div></div>
Suresh Kumar Das | 2 Feb 01:24 2013
Picon

put a node in lowpower state in Tossim

hi

How does a node put in low power state in Tossim. Which interface should I  use to put a node in periodical sleep and listening state in Tossim.
 
 Any solution or help is appreciated.
Thanks

--
Best regards
Suresh Kumar Das
M Tech , Computer Science
University of Hyderabad

<div><p>hi<br><br>How does a node put in low power state in Tossim. Which interface should I&nbsp; use to put a node in periodical sleep and listening state in Tossim.<br>&nbsp;<br>&nbsp;Any solution or help is appreciated. <br>Thanks<br clear="all"><br>-- <br>Best regards<br>Suresh Kumar Das<br>M Tech , Computer Science<br>University of Hyderabad<br></p></div>

Gmane