[Tinyos-help] Installation Error
Hi, When i try to compile the Blink application, I am presented with the following errors: root@TinyOSBeginner:/opt/tinyos-2.1.1/apps/Blink# make telosb mkdir -p build/telosb compiling BlinkAppC to a telosb binary ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"adludla\" -DIDENT_USERHASH=0x391b5347L -DIDENT_TIMESTAMP=0x505c1d46L -DIDENT_UIDHASH=0x22eb5b19L BlinkAppC.nc -lm In file included from /opt/tinyos-2.1.1/tos/chips/msp430/msp430hardware.h:29, from /opt/tinyos-2.1.1/tos/platforms/telosb/hardware.h:4, from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41: /usr/bin/../lib/gcc/msp430/4.5.3/../../../../msp430/include/io.h:1:2: warning: #warning is deprecated, please include In file included from /opt/tinyos-2.1.1/tos/chips/msp430/msp430hardware.h:30, from /opt/tinyos-2.1.1/tos/platforms/telosb/hardware.h:4, from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41: /usr/bin/../lib/gcc/msp430/4.5.3/../../../../msp430/include/signal.h:43:2: warning: #warning msp430-libc deprecated, using In file included from /opt/tinyos-2.1.1/tos/platforms/telosa/PlatformLedsC.nc:38, from /opt/tinyos-2.1.1/tos/system/LedsC.nc:38, from BlinkAppC.nc:45: In component `HplMsp430GeneralIOC': /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:227: syntax error before `;' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:321: cannot find `P30' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:322: cannot find `P31' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:323: cannot find `P31' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:324: cannot find `P32' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:325: cannot find `P33' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:326: cannot find `P33' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:327: cannot find `P34' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:328: cannot find `P35' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:330: cannot find `P50' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:331: cannot find `P51' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:332: cannot find `P52' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:333: cannot find `P53' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:334: cannot find `P36' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:335: cannot find `P37' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:337: cannot find `P60' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:338: cannot find `P61' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:339: cannot find `P62' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:340: cannot find `P63' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:341: cannot find `P64' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:342: cannot find `P65' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:343: cannot find `P66' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:344: cannot find `P67' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:346: cannot find `P66' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:347: cannot find `P67' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:349: cannot find `P67' /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:350: cannot find `P57' In component `PlatformLedsC': /opt/tinyos-2.1.1/tos/platforms/telosa/PlatformLedsC.nc:48: cannot find `Port54' /opt/tinyos-2.1.1/tos/platforms/telosa/PlatformLedsC.nc:51: cannot find `Port55' /opt/tinyos-2.1.1/tos/platforms/telosa/PlatformLedsC.nc:54: cannot find `Port56' make: *** [exe0] Error 1 root@TinyOSBeginner:/opt/tinyos-2.1.1/apps/Blink# make telosb ^C root@TinyOSBeginner:/opt/tinyos-2.1.1/apps/Blink# make telosb mkdir -p build/telosb compiling BlinkAppC to a telosb binary ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"adludla\" -DIDENT_USERHASH=0x391b5347L -DIDENT_TIMESTAMP=0x505c330eL -DIDENT_UIDHASH=0x0d6e8edfL BlinkAppC.nc -lm In file included from /opt/tinyos-2.1.1/tos/chips/msp430/msp430hardware.h:29, from /opt/tinyos-2.1.1/tos/platforms/telosb/hardware.h:4, from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41: /usr/bin/../lib/gcc/msp430/4.5.3/../../../../msp430/include/io.h:1:2:
Re: [Tinyos-help] Installation Error
You are running the old 2.1.1 tree with a newer compiler. 4.5.3 in this case. Bad bad bad. (not you, the situation). First, since you are just starting out, switch to 2.1.2 which has been out for about a month. It is good. Also update to the 4.6.3 toolchain. On Fri, Sep 21, 2012 at 2:34 AM, Gcina Dludla wrote: > Hi, > When i try to compile the Blink application, I am presented with the > following errors: > > > root@TinyOSBeginner:/opt/tinyos-2.1.1/apps/Blink# make telosb > mkdir -p build/telosb > compiling BlinkAppC to a telosb binary > ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -fnesc-separator=__ > -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c > -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\"BlinkAppC\" > -DIDENT_USERNAME=\"root\" -DIDENT_HOSTNAME=\"adludla\" > -DIDENT_USERHASH=0x391b5347L -DIDENT_TIMESTAMP=0x505c1d46L > -DIDENT_UIDHASH=0x22eb5b19L BlinkAppC.nc -lm > In file included from > /opt/tinyos-2.1.1/tos/chips/msp430/msp430hardware.h:29, > from /opt/tinyos-2.1.1/tos/platforms/telosb/hardware.h:4, > from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41: > /usr/bin/../lib/gcc/msp430/4.5.3/../../../../msp430/include/io.h:1:2: > warning: #warning is deprecated, please include > In file included from > /opt/tinyos-2.1.1/tos/chips/msp430/msp430hardware.h:30, > from /opt/tinyos-2.1.1/tos/platforms/telosb/hardware.h:4, > from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41: > /usr/bin/../lib/gcc/msp430/4.5.3/../../../../msp430/include/signal.h:43:2: > warning: #warning msp430-libc deprecated, using > In file included from > /opt/tinyos-2.1.1/tos/platforms/telosa/PlatformLedsC.nc:38, > from /opt/tinyos-2.1.1/tos/system/LedsC.nc:38, > from BlinkAppC.nc:45: > In component `HplMsp430GeneralIOC': > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:227: syntax > error before `;' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:321: cannot > find `P30' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:322: cannot > find `P31' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:323: cannot > find `P31' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:324: cannot > find `P32' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:325: cannot > find `P33' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:326: cannot > find `P33' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:327: cannot > find `P34' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:328: cannot > find `P35' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:330: cannot > find `P50' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:331: cannot > find `P51' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:332: cannot > find `P52' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:333: cannot > find `P53' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:334: cannot > find `P36' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:335: cannot > find `P37' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:337: cannot > find `P60' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:338: cannot > find `P61' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:339: cannot > find `P62' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:340: cannot > find `P63' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:341: cannot > find `P64' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:342: cannot > find `P65' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:343: cannot > find `P66' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:344: cannot > find `P67' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:346: cannot > find `P66' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:347: cannot > find `P67' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:349: cannot > find `P67' > /opt/tinyos-2.1.1/tos/chips/msp430/pins/HplMsp430GeneralIOC.nc:350: cannot > find `P57' > In component `PlatformLedsC': > /opt/tinyos-2.1.1/tos/platforms/telosa/PlatformLedsC.nc:48: cannot find > `Port54' > /opt/tinyos-2.1.1/tos/platforms/telosa/PlatformLedsC.nc:51: cannot find > `Port55' > /opt/tinyos-2.1.1/tos/platforms/telosa/PlatformLedsC.nc:54: cannot find > `Port56' > make: *** [exe0] Error 1 > root@TinyOSBeginner:/opt/tinyos-2.1.1/apps/Blink# make telosb ^C > root@TinyOSBeginner:/opt/tinyos-2.1.1/apps/Blink# make telosb > mkdir -p build/telosb > compiling BlinkAppC to a telosb binary > ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -fnesc-separator=__ > -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c > -
[Tinyos-help] help to configure sensor network in tossim
Hi all, till now whatever i have implemented in tinyos & simulated in tossim, i just created a "topo.txt" file in which i needed to specify nodes between which connection exist & a gain value. but now i need to implement a algorithm in which every node present at the monitoring area need to know their location i.e coordinate, & based upon that they propagate sensed data to a particular direction. but i did not understand how will i define such a topology(based on coordinate) in tossim simulator and also how to calculate the remaining energy of a perticular node after sending message. plz help me. thanks in advance. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] one question about InternalFlash interface
Hi, On micaz mote, is the InternalFlash interface only used for EEPROM, instead of the Program Memory of AVR Atemgal128? If yes, does TinyOS 2.1.1 provide some interface to access the Program Memory of MicaZ? Thanks. Gary ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] sensorboard its400
Hi everyone! I installed tinyos, following the instructions inhttp://graphics.stanford.edu/courses/cs321-07-fall/Project/tinyosInstall.htm and then I installed the ISHMP software http://shm.cs.uiuc.edu/software.html In order to use that software, one must select the sensorboard, that, in this case could be ITS400CA or ITS400CB, but I didn't find any information about how to know which one I have. I tried with both of them.Now, when I try to read the temperature from other imote, I got this BluSH>Remotely executing "ReadTemp" on 1 node(s): 89Reading temperature from remote node(s)...Remote command "ReadTemp" successfully sent to 1 of 1 node(s): 89Remote command "ReadTemp" executed.Temperature (from Sensirion): 615.7 C 615.7C !!!, What could be wrong? Any advice will be really appreciated.Joc ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] one question about InternalFlash interface
Gary, Include avr/pgmspace.h, and use the pgm_read_word macro to access the program memory. There's a nice tutorial on it at the following URL: http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=38003 Janos On Fri, Sep 21, 2012 at 10:47 AM, Gary Lee wrote: > Hi, > > On micaz mote, is the InternalFlash interface only used for EEPROM, instead > of the Program Memory of AVR Atemgal128? > > > If yes, does TinyOS 2.1.1 provide some interface to access the Program > Memory of MicaZ? > > > Thanks. > > > Gary > > > > ___ > Tinyos-help mailing list > Tinyos-help@millennium.berkeley.edu > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Could not find the main class: net.tinyos.nesc.wiring.WiringCheck.
Hi Guys, So what is the real problem? Is the tinyos-tools not correct, or the tinyos package is not compiled with the right java? I have just uploaded tinyos-2.1.2-2.1.2-20120921.noarch.rpm here: http://tinyos.stanford.edu/tinyos/dists/cygwin/ Miklos On Wed, Sep 12, 2012 at 4:18 PM, András Bíró wrote: > > > On Wed, Sep 12, 2012 at 11:15 PM, András Bíró > wrote: >> >> Hi Gary, >> >> On Wed, Sep 12, 2012 at 9:54 PM, Gary Helbig wrote: >>> >>> >>> I'm trying to get TinyOS to work on another computer. This is a Windows7 >>> machine. >> >> >> I'm using Windows 7 Pro x64 as well for cygwin testing. >>> >>> >>> The link to cygwin on the TinyOS install page is dead. The site that it >>> linked to had an antique version of cygwin that does not run on Windows7. >>> >>> I have found four separate repositories for TinyOS with cygwin: >>> http://www.tinyos.net/dist-2.1.0/tinyos/windows/ >>> http://www.tinyos.net/dist-2.1.0/tools/windows/ >>> http://tinyos.stanford.edu/tinyos/dists/cygwin/ >>> http://tinyos.stanford.edu/tinyos-rpms/ >>> >>> There is some overlap, and some confusion about which files are current. >>> It would be nice if that were straightened out. >> >> >> Agreed. But tinyos 2.1.2 just released, the documentation is not updated >> yet - so be patient. If you want the newest version, use this: >> http://tinyos.stanford.edu/tinyos/dists/cygwin/ >> >>> >>> I made a best-guess as to which files to install. There is a problem >>> installing 'tinyos-tools-1.4.2-20120810.cygwin.i686.rpm' on Windows7 - there >>> is a dll (getenv.dll) that Windows will not let you overwrite, even if you >>> run as administrator. >> >> >> This is one of the two JNI libs. You can live without it, only the java >> SDK needs it. You can install it anytime with tos-install-jni, if it still >> doesn't work, check what the script does, and do it manually. >> >>> >>> >>> I wound up installing three copies of TinyOS - tinyos-2.x, tinyos-2.1.2, >>> and tinyos-main. The difference between 2.1.2 and main is unclear, and 2.x >>> is the latest version that installs without complaining. >> >> >> tinyos-2.1.2 - it's the current stable. It's very similar to the current >> svn trunk, becouse we're just after release. >> tinyos-main - I guess you're refering to the tinyos svn. It's the official >> development tree, but usually it's quite stable >> tinyos-2.x - I'm not sure what is this. The problem is you're refering to >> packages with the directory names, which could be the same. For example, I'm >> using a lot of development tree, and just symlink the active to >> /opt/tinyos-2.x >> >> >>> >>> >>> At long last I try a sample build (app/Blink) to see if the install >>> worked. Nope: >>> >>> $ make micaz >>> mkdir -p build/micaz >>> compiling BlinkAppC to a micaz binary >>> ncc -o build/micaz/main.exe -Os -fnesc-separator=__ -Wall -Wshadow >>> -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb >>> -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10 >>> -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"gahelbig\" >>> -DIDENT_HOSTNAME=\"2UA2061DGW\" -DIDENT_USERHASH=0x323af339L >>> -DIDENT_TIMESTAMP=0x5050dfaaL -DIDENT_UIDHASH=0xa406223bL -fnesc-dump=wiring >>> -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, >>> components)' -fnesc-dumpfile=build/micaz/wiring-check.xml BlinkAppC.nc -lm >>> java.lang.UnsupportedClassVersionError: >>> net/tinyos/nesc/wiring/WiringCheck : Unsupported major.minor version 51.0 >>> at java.lang.ClassLoader.defineClass1(Native Method) >>> at java.lang.ClassLoader.defineClassCond(Unknown Source) >>> at java.lang.ClassLoader.defineClass(Unknown Source) >>> at java.security.SecureClassLoader.defineClass(Unknown Source) >>> at java.net.URLClassLoader.defineClass(Unknown Source) >>> at java.net.URLClassLoader.access$000(Unknown Source) >>> at java.net.URLClassLoader$1.run(Unknown Source) >>> at java.security.AccessController.doPrivileged(Native Method) >>> at java.net.URLClassLoader.findClass(Unknown Source) >>> at java.lang.ClassLoader.loadClass(Unknown Source) >&g
Re: [Tinyos-help] WSN testbeds
Hi, You can use our testbed neteye.cs.wayne.edu. On Wed, Sep 19, 2012 at 3:24 AM, wasif masood wrote: > > thanks Roman but I am interested in a testbed of atleast around 50 nodes, > do you have anything else in your mind? > > > On Tue, Sep 18, 2012 at 11:28 PM, Roman Lim wrote: > >> There is for instance FlockLab @ http://www.flocklab.ethz.ch/ >> >> Cheers >> Roman >> >> >> On 09/18/2012 09:58 AM, wasif masood wrote: >> >> >> Hi All, >> >> I am looking for some online testbeds to test run my application on the >> real telosb motes. I know about Indirya and Harvard Motelab, are there any >> other such testbeds available for students that I can use online? >> >> Regards! >> Wasif Masood >> >> >> >> ___ >> Tinyos-help mailing >> listTinyos-help@millennium.berkeley.eduhttps://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> >> >> >> ___ >> Tinyos-help mailing list >> Tinyos-help@millennium.berkeley.edu >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > > > > -- > Wasif Masood > > > ___ > Tinyos-help mailing list > Tinyos-help@millennium.berkeley.edu > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- -Xiaohui Liu ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
