Antonis Tzounis | 27 Jan 21:03 2015
Picon

Problem compiling Blink app in Z1 nodes

Hello,
Today I came up a strange issue while trying to compile a simple blink application for my new Zolertia Z1 nodes. While I can complile blink for telosb, when I chanve target to z1 I have the following error:

---------------------------------------------------------------------------------------
mkdir -p build/z1
    compiling BlinkAppC to a z1 binary
ncc -o build/z1/main.exe  -Os -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=z1 -fnesc-cfile=build/z1/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"ubuntu\" -DIDENT_USERHASH=0xa3473ba6L -DIDENT_TIMESTAMP=0x54c7edbeL -DIDENT_UIDHASH=0xba6f7826L  BlinkAppC.nc -lm 
In file included from /opt/tinyos-2.1.2/tos/system/SchedulerBasicP.nc:52:
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:43:28: error: msp430hardware.h: No such file or directory
In file included from /opt/tinyos-2.1.2/tos/system/SchedulerBasicP.nc:52,
                 from /opt/tinyos-2.1.2/tos/system/TinySchedulerC.nc:51:
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:46: syntax error before `5'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:46: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:46: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:47: syntax error before `5'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:47: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:47: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:48: syntax error before `5'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:48: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:48: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:51: syntax error before `3'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:51: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:51: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:52: syntax error before `3'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:52: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:52: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:53: syntax error before `3'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:53: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:53: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:54: syntax error before `3'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:54: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:54: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:55: syntax error before `3'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:55: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:55: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:56: syntax error before `3'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:56: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:56: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:57: syntax error before `3'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:57: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:57: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:58: syntax error before `5'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:58: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:58: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:59: syntax error before `5'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:59: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:59: warning: data definition has no type or storage class
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:60: syntax error before `5'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:60: warning: return-type defaults to `int'
/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:60: warning: data definition has no type or storage class
In component `TinySchedulerC':
/opt/tinyos-2.1.2/tos/system/TinySchedulerC.nc:52: component McuSleepC not found
/opt/tinyos-2.1.2/tos/system/TinySchedulerC.nc:55: no match
In file included from /opt/tinyos-2.1.2/tos/platforms/z1/PlatformC.nc:47,
                 from /opt/tinyos-2.1.2/tos/system/MainC.nc:61,
                 from BlinkAppC.nc:56:
In component `PlatformP':
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc: In function `Init.init':
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: `WDTCTL' undeclared (first use in this function)
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: (Each undeclared identifier is reported only once
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: for each function it appears in.)
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: `WDTPW' undeclared (first use in this function)
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: `WDTHOLD' undeclared (first use in this function)
In component `PlatformC':
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformC.nc: At top level:
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformC.nc:47: component Msp430ClockC not found
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformC.nc:49: cannot find `Init'
In file included from /opt/tinyos-2.1.2/tos/system/LedsC.nc:49,
                 from BlinkAppC.nc:56:
In component `PlatformLedsC':
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:51: component HplMsp430GeneralIOC not found
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:52: component Msp430GpioC not found
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:52: component `Msp430GpioC' is not generic
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:53: component `Msp430GpioC' is not generic
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:54: component `Msp430GpioC' is not generic
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:60: no match
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:62: cannot find `Port54'
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:64: no match
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:65: cannot find `Port56'
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:67: no match
/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:68: cannot find `Port55'
In file included from /opt/tinyos-2.1.2/tos/system/TimerMilliC.nc:48,
                 from BlinkAppC.nc:57:
In component `TimerMilliP':
/opt/tinyos-2.1.2/tos/system/TimerMilliP.nc:52: component HilTimerMilliC not found
/opt/tinyos-2.1.2/tos/system/TimerMilliP.nc:53: no match
/opt/tinyos-2.1.2/tos/system/TimerMilliP.nc:54: no match
make: *** [exe0] Error 1
-------------------------------------------------------------------------------------------------

I checked if msp430hardware.h file was missing, but it doesn't.
Any ideas what could possibly cause this problem?
Please note that I am using Ubuntu 13 on VMware. 
Has anyone had a similar issue?
Thank you in advance,
Antonis
<div><div dir="ltr">Hello,
<div>Today I came up a strange issue while trying to compile a simple blink application for my new Zolertia Z1 nodes. While I can complile blink for telosb, when I chanve target to z1 I have the following error:</div>
<div><br></div>
<div>---------------------------------------------------------------------------------------</div>
<div>
<div>mkdir -p build/z1</div>
<div>&nbsp; &nbsp; compiling BlinkAppC to a z1 binary</div>
<div>ncc -o build/z1/main.exe &nbsp;-Os -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=z1 -fnesc-cfile=build/z1/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"ubuntu\" -DIDENT_USERHASH=0xa3473ba6L -DIDENT_TIMESTAMP=0x54c7edbeL -DIDENT_UIDHASH=0xba6f7826L &nbsp;BlinkAppC.nc -lm&nbsp;</div>
<div>In file included from /opt/tinyos-2.1.2/tos/system/SchedulerBasicP.nc:52:</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:43:28: error: msp430hardware.h: No such file or directory</div>
<div>In file included from /opt/tinyos-2.1.2/tos/system/SchedulerBasicP.nc:52,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from /opt/tinyos-2.1.2/tos/system/TinySchedulerC.nc:51:</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:46: syntax error before `5'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:46: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:46: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:47: syntax error before `5'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:47: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:47: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:48: syntax error before `5'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:48: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:48: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:51: syntax error before `3'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:51: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:51: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:52: syntax error before `3'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:52: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:52: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:53: syntax error before `3'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:53: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:53: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:54: syntax error before `3'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:54: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:54: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:55: syntax error before `3'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:55: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:55: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:56: syntax error before `3'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:56: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:56: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:57: syntax error before `3'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:57: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:57: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:58: syntax error before `5'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:58: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:58: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:59: syntax error before `5'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:59: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:59: warning: data definition has no type or storage class</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:60: syntax error before `5'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:60: warning: return-type defaults to `int'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/hardware.h:60: warning: data definition has no type or storage class</div>
<div>In component `TinySchedulerC':</div>
<div>/opt/tinyos-2.1.2/tos/system/TinySchedulerC.nc:52: component McuSleepC not found</div>
<div>/opt/tinyos-2.1.2/tos/system/TinySchedulerC.nc:55: no match</div>
<div>In file included from /opt/tinyos-2.1.2/tos/platforms/z1/PlatformC.nc:47,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from /opt/tinyos-2.1.2/tos/system/MainC.nc:61,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from BlinkAppC.nc:56:</div>
<div>In component `PlatformP':</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc: In function `Init.init':</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: `WDTCTL' undeclared (first use in this function)</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: (Each undeclared identifier is reported only once</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: for each function it appears in.)</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: `WDTPW' undeclared (first use in this function)</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformP.nc:51: `WDTHOLD' undeclared (first use in this function)</div>
<div>In component `PlatformC':</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformC.nc: At top level:</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformC.nc:47: component Msp430ClockC not found</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformC.nc:49: cannot find `Init'</div>
<div>In file included from /opt/tinyos-2.1.2/tos/system/LedsC.nc:49,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from BlinkAppC.nc:56:</div>
<div>In component `PlatformLedsC':</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:51: component HplMsp430GeneralIOC not found</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:52: component Msp430GpioC not found</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:52: component `Msp430GpioC' is not generic</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:53: component `Msp430GpioC' is not generic</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:54: component `Msp430GpioC' is not generic</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:60: no match</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:62: cannot find `Port54'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:64: no match</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:65: cannot find `Port56'</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:67: no match</div>
<div>/opt/tinyos-2.1.2/tos/platforms/z1/PlatformLedsC.nc:68: cannot find `Port55'</div>
<div>In file included from /opt/tinyos-2.1.2/tos/system/TimerMilliC.nc:48,</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from BlinkAppC.nc:57:</div>
<div>In component `TimerMilliP':</div>
<div>/opt/tinyos-2.1.2/tos/system/TimerMilliP.nc:52: component HilTimerMilliC not found</div>
<div>/opt/tinyos-2.1.2/tos/system/TimerMilliP.nc:53: no match</div>
<div>/opt/tinyos-2.1.2/tos/system/TimerMilliP.nc:54: no match</div>
<div>make: *** [exe0] Error 1</div>
</div>
<div>-------------------------------------------------------------------------------------------------</div>
<div><br></div>
<div>I checked if msp430hardware.h file was missing, but it doesn't.</div>
<div>Any ideas what could possibly cause this problem?</div>
<div>Please note that I am using Ubuntu 13 on VMware.&nbsp;</div>
<div>Has anyone had a similar issue?</div>
<div>Thank you in advance,</div>
<div>Antonis</div>
</div></div>
housam eddin bouzgaya | 26 Jan 09:18 2015
Picon

(no subject)

Spam detection software, running on the system "mail.Millennium.Berkeley.EDU", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Good MorningI have a problem with (IMB 400) I have three
  of them and I want to use them as sounlocalization in aisle of my company
  , that means when someone made noise the nearest mote start flashing . I researched
   on the internet unfortunately I found very little things,I will be grateful
   if someone help mebest regards to all [...] 

Content analysis details:   (6.1 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 2.0 DNS_FROM_AHBL_RHSBL    RBL: Envelope sender listed in dnsbl.ahbl.org
 0.0 HTML_MESSAGE           BODY: HTML included in message
 2.8 MIME_BASE64_TEXT       RAW: Message text disguised using base64 encoding
 1.3 MISSING_SUBJECT        Missing Subject: header

The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam.  If you wish to view
it, it may be safer to save it to a file and open it with an editor.

Picon
From: housam eddin bouzgaya <housam2318 <at> hotmail.com>
Subject: housam2318 <at> hotmail.com
Date: 2015-01-26 08:18:28 GMT

 Good Morning


I have a problem with (IMB 400) I have three of them and I want to use them as sounlocalization in aisle of my company , that means when someone made noise the nearest mote start flashing . I researched on the internet unfortunately I found very little things,

I will be grateful if someone help me


best regards to all
<div><div dir="ltr">&nbsp;<span data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$0:0">Good Morning</span><br data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$1:0"><br data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$3:0"><br data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$5:0"><span data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$6:0">I have a problem with (IMB 400) I have three of them and I want to use them as sounlocalization in aisle of my company , that means when someone made noise the nearest mote start flashing . I researched on the internet unfortunately I found very little things,</span><br data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$7:0"><br data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$9:0"><span data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$10:0">I will be grateful if someone help me</span><br data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$11:0"><br data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$13:0"><br data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$15:0"><span data-reactid=".19.$mid=11422258282977=2aa3827c6d8908ea548.2:0.0.0.0.0.0.$end:0:$16:0">best regards to all</span> 		 	   		  </div></div>
Lynda Algerienne | 25 Jan 08:23 2015
Picon

Linking Math Library

Hello,

I writing a tinyos code. I need to use the logarithm function. I got the following error:

undefined reference to log"

I have tried two solutions: adding -lm option to my make file but it did not work

I have tried to use logf but the returned result is wrong.

Can anyone please help me to solve this issue?

Thank you in advance.

Regards,

Lynda.
<div><div dir="ltr">Hello,<div><br></div>
<div>I writing a tinyos code. I need to use the logarithm function. I got the following error:</div>
<div><br></div>
<div>undefined reference to log"</div>
<div><br></div>
<div>I have tried two solutions: adding -lm option to my make file but it did not work</div>
<div><br></div>
<div>I have tried to use logf but the returned result is wrong.</div>
<div><br></div>
<div>Can anyone please help me to solve this issue?</div>
<div><br></div>
<div>Thank you in advance.</div>
<div><br></div>
<div>Regards,</div>
<div><br></div>
<div>Lynda.</div>
</div></div>
Picon

Re: PROBLEM WITH COMPILER

Dear Friends

I am working with a Z1 mote and Gateway from Zolertia, I bougth the devices one month ago, so the devices are new, I have read a lot of tutorials about how to work with BLIP2 and these devices, but there aren't so clear, that's why I need your help, my project is about to communicate the gateway and the mote using 6lowpan, I wanna know if there is a very good tutorial about do this, I'll really appreciate your help.

If u need more information about my devices I 'll give you, I wanna know if I have to install something, the software version of the Z1 gateway is Voyage 0.8.0

I am new in this fields, please help me

Have a nice day
Juan Pablo

Date: Sat, 27 Dec 2014 14:02:57 -0500
Subject: FW: Re: [Tinyos-help] PROBLEM WITH COMPILER
From: jpablogv86 <at> hotmail.com
To: pabln.ms <at> hotmail.com; mountain.trance <at> hotmail.com

Porfa chicos analicen lo q me contestan y ayuden a ver el problema xfa

Sent from my Sony Xperia™ smartphone



---- Original Message ----
Subject: Re: [Tinyos-help] PROBLEM WITH COMPILER
Sent: Dec 27, 2014 9:27 AM
From: Antonio Linan <alinan <at> zolertia.com>
To: Eric Decker <cire831 <at> gmail.com>
Cc: juan pablo gallardo velásquez <jpablogv86 <at> hotmail.com>,tinyos-help <at> millennium.berkeley.edu,CARLOS EGAS <kyviis <at> hotmail.com>,Andres Muñoz <mountain.trance <at> hotmail.com>,Pablo Morales <pabln.ms <at> hotmail.com>

Did you "source environment.sh" ?

--Antonio

On Sat, Dec 27, 2014 at 7:40 AM, Eric Decker <cire831 <at> gmail.com> wrote:

that's not a compiler problem.  you haven't installed correctly.

looks like you chmod'd the environment.sh shell script but never executed it.



what instructions did you follow for installing?

where did you get the source code?   

what version of tinyos are you using?

etc etc etc


On Fri, Dec 26, 2014 at 11:38 AM, juan pablo gallardo velásquez <jpablogv86 <at> hotmail.com> wrote:
Dear friends,
I'm having troubles trying to compile some examples in Gateway Z1 (zolertia) , I'll provide you the code lines to let you know exactly what I am doing.

I'll really appreciate your support ,
Sincerely
JP

root <at> ZolertiaGW:/opt# chmod 666 environment.sh

root <at> ZolertiaGW:/opt# ls

Contiki environment.sh mosquitto-1.0.2 README.Os Yaler

Cosm MansOS openssl-1.0.1c TinyOS ZGW

root <at> ZolertiaGW:/opt# cd TinyOS/tinyos-2.x/apps/Blink/

root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink# ls

BlinkAppC.nc BlinkC.nc Makefile README.txt

root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink# motelist

Reference Device Description

---------- ---------------- ---------------------------------------------

Z1RC4547 /dev/ttyUSB0 Silicon Labs Zolertia Z

chmod 666 /dev/ttyUSB0

root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink# make z1

make: *** No rule to make target `z1'. Stop.

root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink# make z1 reinstall

make: *** No rule to make target `z1'. Stop.

root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink#



_______________________________________________
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




--
<div><div dir="ltr">Dear Friends<br><br>I am working with a Z1 mote and Gateway from Zolertia, I bougth the devices one month ago, so the devices are new, I have read a lot of tutorials about how to work with BLIP2 and these devices, but there aren't so clear, that's why I need your help, my project is about to communicate the gateway and the mote using 6lowpan, I wanna know if there is a very good tutorial about do this, I'll really appreciate your help.<br><br>If u need more information about my devices I 'll give you, I wanna know if I have to install something, the software version of the Z1 gateway is Voyage 0.8.0<br><br>I am new in this fields, please help me<br><br>Have a nice day<br>Juan Pablo<br><br><div>Date: Sat, 27 Dec 2014 14:02:57 -0500<br>Subject: FW: Re: [Tinyos-help] PROBLEM WITH COMPILER<br>From: jpablogv86 <at> hotmail.com<br>To: pabln.ms <at> hotmail.com; mountain.trance <at> hotmail.com<br><br><p dir="ltr">Porfa chicos analicen lo q me contestan y ayuden a ver el problema xfa
</p>
<p dir="ltr">Sent from my Sony Xperia&trade; smartphone</p>
<br><br>
---- Original Message ----<br>
Subject: Re: [Tinyos-help] PROBLEM WITH COMPILER<br>
Sent: Dec 27, 2014 9:27 AM<br>
From: Antonio Linan &lt;alinan <at> zolertia.com&gt;<br>
To: Eric Decker &lt;cire831 <at> gmail.com&gt;<br>
Cc: juan pablo gallardo vel&aacute;squez &lt;jpablogv86 <at> hotmail.com&gt;,tinyos-help <at> millennium.berkeley.edu,CARLOS EGAS &lt;kyviis <at> hotmail.com&gt;,Andres Mu&ntilde;oz &lt;mountain.trance <at> hotmail.com&gt;,Pablo Morales &lt;pabln.ms <at> hotmail.com&gt;<br><br><div>
<div dir="ltr">
<div>Did you "source environment.sh" ?<br><br>
</div>
--Antonio<br>
</div>
<div class="ecxx_gmail_extra">
<br><div class="ecxx_gmail_quote">On Sat, Dec 27, 2014 at 7:40 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="ecxx_gmail_quote">
<div dir="ltr">
<br><div>that's not a compiler problem. &nbsp;you haven't installed correctly.</div>
<div><br></div>
<div>looks like you chmod'd the environment.sh shell script but never executed it.</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div>what instructions did you follow for installing?</div>
<div><br></div>
<div>where did you get the source code? &nbsp;&nbsp;</div>
<div><br></div>
<div>what version of tinyos are you using?</div>
<div><br></div>
<div>etc etc etc</div>
<div><br></div>
</div>
<div class="ecxx_gmail_extra">
<br><div class="ecxx_gmail_quote">
<div>
<div class="ecxx_h5">On Fri, Dec 26, 2014 at 11:38 AM, juan pablo gallardo vel&aacute;squez
<span dir="ltr">&lt;<a href="mailto:jpablogv86 <at> hotmail.com" target="_blank">jpablogv86 <at> hotmail.com</a>&gt;</span> wrote:<br>
</div>
</div>
<blockquote class="ecxx_gmail_quote">
<div>
<div class="ecxx_h5">
<div>
<div dir="ltr">Dear friends,<br>
I'm having troubles trying to compile some examples in Gateway Z1 (zolertia) , I'll provide you the code lines to let you know exactly what I am doing.<br><br>
I'll really appreciate your support ,<br>
Sincerely<br>
JP<br><br><p>root <at> ZolertiaGW:/opt# <span>
chmod 666 environment.sh </span></p>
<p>root <at> ZolertiaGW:/opt# ls </p>
<p>Contiki environment.sh mosquitto-1.0.2 README.Os Yaler
</p>
<p>Cosm MansOS openssl-1.0.1c TinyOS ZGW
</p>
<p>root <at> ZolertiaGW:/opt# cd TinyOS/tinyos-2.x/apps/Blink/
</p>
<p>root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink# ls
</p>
<p>BlinkAppC.nc BlinkC.nc Makefile README.txt
</p>
<p>root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink#
<span>motelist </span></p>
<p>Reference Device Description </p>
<p>---------- ---------------- ---------------------------------------------
</p>
<p>Z1RC4547 /dev/ttyUSB0 Silicon Labs Zolertia Z</p>
<p><span>chmod 666 /dev/ttyUSB0
</span></p>
<p>root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink#
<span>make z1 </span></p>
<p><span>make: *** No rule to make target `z1'. Stop.
</span></p>
<p>root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink#
<span>make z1 reinstall </span></p>
<p><span>make: *** No rule to make target `z1'. Stop.
</span></p>
<p>root <at> ZolertiaGW:/opt/TinyOS/tinyos-2.x/apps/Blink#
</p>
<p></p>
<br>
</div>
</div>
<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 class="ecxx_HOEnZb"><br></span>
</blockquote>
</div>
<span class="ecxx_HOEnZb"><br><br clear="all"><div><br></div>
-- <br><div>Eric B. Decker<br>
Senior (over 50 :-) Researcher<br><br>
</div>
</span>
</div>
</blockquote>
</div>
<br><br clear="all"><br>
-- <br><div class="ecxx_gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">--<br>
Antonio Li&ntilde;&aacute;n Colina<br>
R+D Engineer<br>
 <at> : <a href="mailto:alinan <at> advancare.com" target="_blank">alinan <at> advancare.com</a><br>
 <at> : <a href="mailto:alinan <at> zolertia.com" target="_blank">alinan <at> zolertia.com</a><br>
------------------------------<br><div>Advancare<br><span>Ph.: 
<a target="_blank">+34 931 426 166</a></span><br><a href="http://www.advancare.com/" target="_blank">http://www.advancare.com</a><br><a href="http://www.zolertia.com/" target="_blank">http://www.zolertia.com</a><br><a href="http://zolertia.sourceforge.net" target="_blank">http://zolertia.sourceforge.net</a><br><a href="http://webshop.zolertia.com" target="_blank">http://webshop.zolertia.com</a><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div> 		 	   		  </div></div>
Bello Kontagora | 24 Jan 13:54 2015
Picon

counting the duration of a pulse

Hi everyone, please can anyone help me out? I want to get the duration of an echo pulse through gpio/input pin. I interfaced PING ultrasonic range finder with XM1000(TelosB) through GPIO pin. the sensor requires a pulse of 5micro seconds to trigger it, it then returns an echo whose duration I needed. below is my code section: thank you in advance.

      (PingingP.nc)
module PingingP <at> safe() {
    uses {
                interface Boot;
                interface Leds;
                interface HplMsp430GeneralIO as samplePin;
                interface BusyWait<TMicro, uint16_t> as delay;
                interface Timer<TMilli> as Timer;
    }
}
    implementation {
        uint16_t Time;
    event void Boot.booted() {
        call Timer.startPeriodic(2000);
}

    event void Timer.fired () {
        call Leds.led1Toggle();
        call samplePin.makeOutput(); //make the pin an output
        call samplePin.set(); //start ranging
        call delay.wait (5); //for 5 micro seconds
        call samplePin.makeInput(); // make the pin an input
        Time = call samplePin.get(); //this is where am confused, how to get the duration of the echo pulse and print it?
        printf("Time is %d\n", Time);
    }
}

        (PingingC.nc)
#include <Timer.h>

configuration BuzzerC {
}
    implementation {
        components MainC, BuzzerP as App, LedsC;
        MainC.Boot <- App;
        App.indication3 -> HplMsp430GeneralIOC.Port26; //pin4 of the 6 pins expansion
        App.Leds -> LedsC;
        components HplMsp430GeneralIOC;
        components BusyWaitMicroC;
        App.delay -> BusyWaitMicroC;
        components SerialPrintfC;
       
        components new TimerMilliC() as Timer;
        App.Timer -> Timer;

}
<div><div dir="ltr">
<div dir="ltr">
<div>Hi everyone, please can 
anyone help me out? I want to get the duration of an echo pulse through 
gpio/input pin. I interfaced PING ultrasonic range finder with 
XM1000(TelosB) through GPIO pin. the sensor requires a pulse of 5micro 
seconds to trigger it, it then returns an echo whose duration I needed. 
below is my code section: thank you in advance.<br><br>
</div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (PingingP.nc)<br><div>module PingingP  <at> safe() {<br>&nbsp;&nbsp;&nbsp; uses {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; interface Boot;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; interface Leds;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; interface HplMsp430GeneralIO as samplePin;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; interface BusyWait&lt;TMicro, uint16_t&gt; as delay;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; interface Timer&lt;TMilli&gt; as Timer;<br>&nbsp;&nbsp;&nbsp; }<br>}<br>&nbsp;&nbsp;&nbsp; implementation {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; uint16_t Time;<br>&nbsp;&nbsp;&nbsp; event void Boot.booted() {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call Timer.startPeriodic(2000);<br>}<br><br>&nbsp;&nbsp;&nbsp; event void Timer.fired () {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call Leds.led1Toggle();<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call samplePin.makeOutput(); //make the pin an output<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call samplePin.set(); //start ranging<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call delay.wait (5); //for 5 micro seconds<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; call samplePin.makeInput(); // make the pin an input<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Time = call samplePin.get(); //this is where am confused, how to get the duration of the echo pulse and print it?<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; printf("Time is %d\n", Time);<br>&nbsp;&nbsp;&nbsp; }<br>}<br><br>
</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (PingingC.nc)<br>#include &lt;Timer.h&gt;<br><br>configuration BuzzerC {<br>}<br>&nbsp;&nbsp;&nbsp; implementation {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; components MainC, BuzzerP as App, LedsC;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; MainC.Boot &lt;- App;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; App.indication3 -&gt; HplMsp430GeneralIOC.Port26; //pin4 of the 6 pins expansion<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; App.Leds -&gt; LedsC;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; components HplMsp430GeneralIOC;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; components BusyWaitMicroC;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; App.delay -&gt; BusyWaitMicroC;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; components SerialPrintfC;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; components new TimerMilliC() as Timer;<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; App.Timer -&gt; Timer;<br><br>}<br>
</div>
</div>
</div></div>
Robert Clove | 23 Jan 08:10 2015
Picon

Compiling C application on TinyOs

Hi,

I have an c application,how can i compile it on Tiny Os.
My application compiles very well on Linux.

Regards


<div><div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">Hi,<div><br></div>
<div>I have an c application,how can i compile it on Tiny Os.</div>
<div>My application compiles very well on Linux.</div>
<div><br></div>
<div>Regards</div>
<div><br></div>
</div>
</div>
<br>
</div></div>
Elisabetta Biondi | 20 Jan 17:04 2015
Picon

CFP: IEEE WoWMoM 2015 Workshop on Autonomic and Opportunistic Communications (IEEE AOC 2015)

--------------------------------------------------------------------
Our apologies if you receive multiple copies of this CFP

Abstract submission deadline:   March 7,  2015 
Full manuscript due:            March 14, 2015
Acceptance notification:        April 20, 2015
---------------------------------------------------------------------

                          CALL FOR PAPERS

               The Ninth IEEE International Workshop on
              Autonomic and Opportunistic Communications
                             (AOC 2015)

                   http://cnd.iit.cnr.it/aoc2015

                           sponsored by
                       IEEE Computer Society,
                        EU FP7 MOTO Project                           

                  June 14-17 2015, Boston, MA, USA

The diffusion of lightweight, powerful portable devices, also enriched with a
variety of sensing capabilities, is enabling new ways for users' communication,
and laying the foundation for realizing the ubiquitous networking idea. Acting
either as the main communication mode or as complement to existing mobile
network infrastructures, opportunistic networking can leverage the mobility of
end users and enhance their communication capabilities. The opportunistic
exploitation of extemporary contacts among the users of the network paves the
way to a number of applications but also poses new and challenging problems to
the networking research community. The AOC 2015 workshop aims at serving as a
meeting point for people working in the area and a forum for exchanging ideas,
discussing solutions, and sharing experiences among researchers, professionals,
and application developers, both from industry and academia.  As with the
previous eight editions of the AOC workshop series, the scope of this year's
workshop will remain on general issues related to opportunistic networking and
computing. Yet, AOC 2015 will have a primary interest in new directions of
opportunistic communications, such as mobile social networking, autonomous
solutions for smart cities, big data for autonomic and opportunistic systems
service composition techniques, scenarios of co-existence with infrastructure
networks, and insights to their operation coming from other disciplines such as
game theory and cognitive psychology. The workshop will solicit original papers
addressing theoretical and practical aspects of autonomic and opportunistic
communications but also papers describing prototype implementations and
deployments.

Topics of interest for AOC 2015 include, but are not limited to: 

- Techniques for data dissemination and replication
- Context and social awareness mechanisms and algorithms
- Autonomous and self-adaptive systems for smart cities
- Autonomous solutions for IoT and cyber-physical systems
- Big data for autonomic and opportunistic systems
- Mobile social networking algorithms and applications
- Co-existence of opportunistic networks with infrastructure mobile wireless
  networks
- Mobility models and statistical analysis of mobility traces
- Service composition in autonomic and opportunistic networks
- Cognition-driven information processing and decision making
- Performance modelling, scaling laws, and fundamental limits for autonomic and
  opportunistic communications
- Participatory and urban sensing in autonomic and opportunistic networks
- Game-theoretic insights to the operation of autonomic and opportunistic
  networks
- Trust, security, and reputation
- Autonomic and opportunistic communication testbeds and prototypes, measurement
  data from real experiments
- Socio-economic models for autonomic and opportunistic communications
- Autonomic and opportunistic solutions for mobile cloud applications
- Applications and middleware support
- Routing, transport, and reliability issues

PAPER SUBMISSION AND PUBLICATION
------------------------------------------------------------------------
All submissions must describe original research, not published or
currently under review for another workshop, conference, or journal.
Papers must be submitted electronically through EDAS. You can find
detailed submission instructions at:
http://cnd.iit.cnr.it/aoc2015/submission.html

IEEE AOC 2015 is using the EDAS Conference Management Software. 
Paper submission is possible via this link:
http://edas.info/N19275

Manuscripts are limited to 6 pages, single spacing, double column, and must strictly adhere to the IEEE
conference template format. Guidelines on paper submission and formatting are available at http://cnd.iit.cnr.it/aoc2015/submission.html

********************************************************************************
Submission implies the willingness of at least one author to attend the workshop 
and present the paper. Accepted papers will be included in the proceedings of 
IEEE WoWMoM 2015 and published in the IEEE Digital Library. Workshop organizers 
reserve the right to exclude a paper from distribution after the workshop 
(e.g., removal from IEEE Xplore) if the paper is not presented at the conference.

There will be no separate registration for workshop, but one single registration 
will cover both conference and workshops participation. At least one author of 
each accepted paper is required and present his/her work at the workshop.
********************************************************************************

EDITORIAL FOLLOW-UP
------------------------------------------------------------------------
Extended versions of workshop selected papers will be considered for possible
fast track publication on the Computer Communications Journal (Elsevier). 

IMPORTANT DATES (EXTENDED DEADLINES)
------------------------------------------------------------------------
- Abstract submission deadline:   	March 7,  2015 
- Full manuscript due:                  March 14, 2015 
- Acceptance notification:              April 20, 2015
- Camera Ready:                         May 7,    2015

CONTACTS
------------------------------------------------------------------------
For further information, please visit the conference website at 
http://cnd.iit.cnr.it/aoc2015, or contact the PC Chairs:
aoc2015 <at> iit.cnr.it

ORGANIZING COMMITTEE
------------------------------------------------------------------------
WORKSHOP Co-Chairs
Lorenzo Valerio, IIT-CNR, Italy 
Matteo Mordacchini, IIT-CNR, Italy

STEERING Committee
Marco Conti, IIT-CNR, Italy 
Silvia Giordano, SUPSI, Switzerland 
Ioannis Stavrakakis, University of Athens, Greece

PUBLICITY Chair
Elisabetta Biondi, IIT-CNR, Italy

PROGRAM Committee
Andreea Picu, ETH Zurich, Switzerland
Anna Forster, SUPSI, Switzerland
Chiara Boldrini, IIT-CNR, Italy
Christian Rohner, Uppsala University, Sweden
Daniele Miorandi, Create-net, Italy
Daniele Puccinelli, SUPSI, Switzerland
Eiko Yoneki, University of Cambridge, UK
Elena Pagani, University of Milano, Italy
Eleonora Borgia, IIT-CNR, Italy
Franck Legendre, ETH Zurich, Switzerland
Franco Zambonelli, University of Modena and Reggio Emilia, Italy
Gunnar Karlsson, KTH, Sweden
Hongyi Wu, University of Louisiana at Lafayette, USA
Jian-Nong Cao, Hong Kong Polytechnic University, HK
Jorg Ott, Aalto University, Finland
Katia Obraczka, University of California Santa Cruz, USA 
Konstantinos Oikonomou, Ionian University, Greece
Kyunghan Lee, North Carolina State University, USA
Michela Papandrea, SUSPSI, Switzerland
Melek Onen, EURECOM, France
Nils Aschenbruck, University of Osnabruck, Germany
Roger Whitaker, Cardiff University, UK
Sebastian Zander, Swinbourne University of Technology, Australia
Serge Fdida, UPMC Sorbonne Universites, France
Tristan Henderson, University of St Andrews, United Kingdom
Valerio Arnaboldi, IIT-CNR, Italy
Valtteri Niemi, University of Turku, Finland
Vania Conan, Thales Communication and Security, France
András Bíró | 15 Jan 18:29 2015

BLIP 2.0 working on RF230/RFA1

Hi everyone,

I managed to port BLIP 2.0 on RF230 based motes (e.g. iris) and RFA1 based motes (e.g. ucmini), including 64 bit addressing:

The only limitation I know is that it is only capable of using the lower byte of the PAN id, because it uses the ActiveMessageAddress interface to set it.

The big RAM/ROM of the RFA1 makes it capable of running the PppRouter app, which I think recently became problematic on the old msp430 of the telosb.

However, since I have very limited experience with blip/6lowpan or even ipv6, I only run basic tests: I did the tutorial with static addressing, and checked the RPL dodag messages and NDP messages with a sniffer. But there might be still a lot of bugs in it, so please test it, and report bugs on github.

The modification itself should be easy enough to port on any rfxlink radios which have HwAck (and address matching) driver layer.

Best,
András Bíró
<div><div dir="ltr">Hi everyone,<div><br></div>
<div>I managed to port BLIP 2.0 on RF230 based motes (e.g. iris) and RFA1 based motes (e.g. ucmini), including 64 bit addressing:</div>
<div>
<a href="https://github.com/tinyos/tinyos-main/commit/8a2e30a423afb2f1c254a486ae6879ac0a993f29">https://github.com/tinyos/tinyos-main/commit/8a2e30a423afb2f1c254a486ae6879ac0a993f29</a><br>
</div>
<div><br></div>
<div>The only limitation I know is that it is only capable of using the lower byte of the PAN id, because it uses the ActiveMessageAddress interface to set it.</div>
<div><br></div>
<div>The big RAM/ROM of the RFA1 makes it capable of running the PppRouter app, which I think recently became problematic on the old msp430 of the telosb.</div>
<div><br></div>
<div>However, since I have very limited experience with blip/6lowpan or even ipv6, I only run basic tests: I did the tutorial with static addressing, and checked the RPL dodag messages and NDP messages with a sniffer. But there might be still a lot of bugs in it, so please test it, and report bugs on github.</div>
<div><br></div>
<div>The modification itself should be easy enough to port on any rfxlink radios which have HwAck (and address matching) driver layer.</div>
<div><br></div>
<div>Best,</div>
<div>Andr&aacute;s B&iacute;r&oacute;</div>
</div></div>
Vandana Bhasin | 12 Jan 09:57 2015
Picon

Does assembly language instruction execute when compiled with TOSSIM?

I installed ubuntu and am using TOSSIM as simulator. Rest of programs are compiling properly and running. But when the below #define directive for assembly gets added as a preprocessor directive to file HPLAt45dbIOP.nc for micaz; The assembly code is not recognised. I am trying to use micaz as the platform on TOSSIM.

#define BITINIT \

uint8_t clrClkAndData = PORTD & ~0x28

#define BIT(n) \

PORTD = clrClkAndData; \ asm __volatile__ \ ( "sbrc %2," #n "\n" \ "\tsbi 18,3\n" \ "\tsbi 18,5\n" \ "\tsbic 16,2\n" \ "\tori %0,1<<" #n "\n" \ : "=d" (spiIn) : "0" (spiIn), "r" (spiOut))
I get errors like /opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:

Assembler messages: /opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:150: Error: no such instruction: sbrc %cl,7' /opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:151: Error: no such instruction:sbi 18,3' /opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:152: Error: no such instruction: sbi 18,5' /opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:153: Error: no such instruction:sbic 16,2' /opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:154: Error: no such instruction: `ori %dl,1<<7'


I have an Intel machine.  Is TOSSIM unable to run assembly language instructions? Please help this is becoming frustrating.


Thanks

Vandana

<div><div>
<div dir="ltr" class="" itemprop="text">

        <h1 class="">I installed ubuntu and am using TOSSIM as simulator. Rest of programs are compiling properly and running. But when the below #define directive for assembly gets added as a preprocessor directive to file HPLAt45dbIOP.nc for micaz; The assembly code is not recognised. I am trying to use micaz as the platform on 
TOSSIM. <br>
</h1>
<h1 class="">#define BITINIT \</h1>

<div class="">uint8_t clrClkAndData = PORTD &amp; ~0x28</div>

<h1 class="">#define BIT(n) \</h1>

PORTD = clrClkAndData; \
asm __volatile__ \
    (  "sbrc %2," #n "\n" \
 "\tsbi 18,3\n" \
 "\tsbi 18,5\n" \
 "\tsbic 16,2\n" \
 "\tori %0,1&lt;&lt;" #n "\n" \
 : "=d" (spiIn) : "0" (spiIn), "r" (spiOut))
<div>I get errors like
 /opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc: <br>
</div>
<div><br></div>
<div class="">Assembler messages:
/opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:150: Error: no such instruction: sbrc %cl,7'
/opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:151: Error: no such instruction:sbi 18,3'
/opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:152: Error: no such instruction: sbi 18,5'
/opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:153: Error: no such instruction:sbic 16,2'
/opt/tinyos-2.1.2/tos/platforms/micaz/chips/at45db/HplAt45dbIOP.nc:154: Error: no such instruction: `ori %dl,1&lt;&lt;7'</div>
<div class=""><br></div>
<div class=""><br></div>

<div dir="ltr" class="">I have an Intel machine.&nbsp; Is TOSSIM unable to run assembly language instructions? Please help this is becoming frustrating.</div>
<div dir="ltr" class=""><br></div>
<div dir="ltr" class=""><br></div>
<div dir="ltr" class="">Thanks <br>
</div>
<div dir="ltr" class=""><br></div>
<div dir="ltr" class="">Vandana<br>
</div>

    </div>
<div class="" dir="ltr"><br class=""></div>
</div></div>
Jana-Christina Nissen | 9 Jan 19:04 2015
Picon

Tymo routing protocol

Hi everyone!

I am using MIB520 with IRIS motes. I wanted to implement the Tymo  
multi-hop routing protocol. Therefore I wanted to test with TestTymo  
in apps/tests/ with renamed volumes-at45db.xml. Compiling and  
installing works fine. But there are no messages send between my motes  
(leds do not blink). That is why I started to debug with the leds and  
modified the TestM.nc as follows:

   event void Boot.booted(){
     call Leds.led2On(); //Modification
     call SplitControl.start();
   }

   event void SplitControl.startDone(error_t e){
     if(call MHPacket.address() == ORIGIN){
     	call Leds.led1On(); //Modification
       call Timer.startPeriodic(2048);
     } else { //Modification
     	call Leds.led0On(); //Modification
     }
   }

After installing it on the mote only led2 is lighted. For this reason  
I think that something went wrong after booting.
Does someone knows what I'm doing wrong?

Any help would be greatly appreciated. Thanks!

Xueguang Wu | 8 Jan 11:01 2015
Picon

About tinyos-0.6.1

Hi,
I am now working on collecting embedded C programs. However, after 
TinyOS-0.6.1 the OS has been changed to nesC. I want to download the
old version of TinyOS, but the link in sourceforge is broken:
http://sourceforge.net/projects/tinyos/files/OldFiles/tinyos/0.6.1/
Can you give me a new link or send me that version of TinyOS.
Thanks a lot.

Best Regards,
Xueguang

Gmane