Hello I wrote an application for the Telosb mote that reads the onboard sensors and sends the data to a second Telosb which is running the BaseStation example and connectet to my computer. I can use the "net.tinyos.tools.Listen" and the "net.tinyos.tools.MsgReader" tools to receive the correct data. Now I am trying to see the data just using a simple terminal program like minicom (I am using Ubuntu). I configured the port to 115200/8/N/1, but all that i can see are wrong characters like "ˇˇ ì a_ !"õŸ~~Eˇˇ ". Also I tried to read the data with labview which lead to the same result. I am thankful for any help ! What point am i missing ?
Thank you guys in advance. Am 16.09.2012 um 00:30 schrieb [email protected]: > Send Tinyos-help mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Tinyos-help digest..." > > > Today's Topics: > > 1. Re: iris platform doesn't compile (Aliaksandr Razumkou) > 2. Re: Data Logging with Telosb (Han Bin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 16 Sep 2012 10:40:56 -0400 > From: Aliaksandr Razumkou <[email protected]> > Subject: Re: [Tinyos-help] iris platform doesn't compile > To: Andr?s B?r? <[email protected]> > Cc: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Yes, you're right. That was me on AUR forum. Everything works now :) > Thanks a lot for your help. > > On 09/15/2012 10:19 AM, Andr?s B?r? wrote: >> Hi Guys, >> >> He mentioned in the first mail that he's using Arch linux, I think I >> talked with him in the forum of the arch user repository (aur). >> Just for the record: It turned out that I forget to update the arch >> buildscript for the the new location of the patches in the svn, and >> the script generated an unpatched gcc, which doesn't support atmega1281. >> >> Andris >> >> On Sat, Sep 15, 2012 at 5:18 AM, Eric Decker <[email protected] >> <mailto:[email protected]>> wrote: >> >> >> >> On Sat, Sep 15, 2012 at 7:08 PM, Aliaksandr Razumkou >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hi, >> Thanks for the answer. I have tried to compile Blink from >> /opt/tinyos-2.1.2/, but the same thing happened: micaz >> compiles, but Blink doesn't. Also my environment variables >> set up correctly as far as I can tell >> >> >> That looks wierd to me. What host OS are you running on? >> >> $TOSROOT /opt/tinyos-2.1.2 >> $TOSDIR /opt/tinyos-2.1.2/tos >> $CLASSPATH :/opt/tinyos-2.1.2/support/sdk/java/tinyos.jar >> $MAKERULES /opt/tinyos-2.1.2/support/make/ >> >> >> Here is what mine looks like: Output from "env | sort" with >> interesting ones pulled out... >> >> CLASSPATH=.:/home/cire/mm/t2_cur/tinyos-2.x/support/sdk/java/tinyos.jar >> MAKERULES=/home/cire/mm/t2_cur/tinyos-2.x/support/make/Makerules >> MOTECOM=serial@/dev/ttyUSB1:115200 >> TOSDIR=/home/cire/mm/t2_cur/tinyos-2.x/tos >> TOSMAKE_PATH=/home/cire/mm/t2_mm/support/make >> TOSROOT=/home/cire/mm/t2_cur/tinyos-2.x >> >> >> Now I'm working off the development trunk which is a little bit >> later than 2.1.2 but that shouldn't be an issue. The problem is >> the compiler isn't being told what cpu you are working with. >> >> Have you made any other modifications in your tree (ie. inside of >> /opt/tinyos-2.1.2)? >> >> Where did you get your toolchain? I don't use the avr toolchains >> because I'm working on the msp430 cpus. So you have to tell me >> what toolchain you are using and how to invoke it. >> >> >> >> On 09/14/2012 09:23 PM, Eric Decker wrote: >>> >>> >>> On Fri, Sep 14, 2012 at 6:18 PM, Eric Decker >>> <[email protected] <mailto:[email protected]>> wrote: >>> >>> >>> The clue is... >>> >>> *#warning "device type not defined" >>> * >>> not sure why but something is screwy with your >>> environment variables or with your development tree. >>> >>> I notice you are compiling from ~/Documents/TINYOS/Simple >>> which is clearly outside the tree. >>> >>> Have you tried compiling Blink for the iris? >>> >>> On Sat, Sep 15, 2012 at 6:04 PM, Aliaksandr Razumkou >>> <[email protected] <mailto:[email protected]>> wrote: >>> >>> For some reason I can't compile for iris platform. >>> This works for micaz >>> but not iris. I'm using Arch Linux. Has anybody seen >>> it before? >>> >>> jb@amazing:~/Documents/TINYOS/Simple$ make iris >>> mkdir -p build/iris >>> compiling SimpleAppC to a iris binary >>> ncc -o build/iris/main.exe -Os -fnesc-separator=__ >>> -Wall -Wshadow >>> -Wnesc-all -target=iris -fnesc-cfile=build/iris/app.c >>> -board=micasb >>> -DDEFINED_TOS_AM_GROUP=0x22 --param >>> max-inline-insns-single=100000 >>> -DIDENT_APPNAME=\"SimpleAppC\" -DIDENT_USERNAME=\"jb\" >>> -DIDENT_HOSTNAME=\"amazing\" -DIDENT_USERHASH=0x1b0348deL >>> -DIDENT_TIMESTAMP=0x50552470L -DIDENT_UIDHASH=0x971f40a4L >>> -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' >>> -fnesc-dump='referenced(interfacedefs, components)' >>> -fnesc-dumpfile=build/iris/wiring-check.xml >>> SimpleAppC.nc -lm >>> In file included from >>> /usr/lib/gcc/avr/4.1.2/../../../../avr/include/avr/wdt.h:41, >>> from >>> /opt/tinyos-2.1.2/tos/platforms/iris/platform.h:1, >>> from >>> /opt/tinyos-2.1.2/tos/system/tos.h:43: >>> >>> /usr/lib/gcc/avr/4.1.2/../../../../avr/include/avr/io.h:364:6: >>> warning: >>> #warning "device type not defined" >>> In file included from >>> /opt/tinyos-2.1.2/tos/system/TinySchedulerC.nc:52: >>> In component `McuSleepC': >>> /opt/tinyos-2.1.2/tos/chips/atm1281/McuSleepC.nc:101: >>> `SM0' undeclared >>> here (not in a function) >>> >>> >> >> >> >> >> -- >> Eric B. Decker >> Senior (over 50 :-) Researcher >> >> >> >> _______________________________________________ >> Tinyos-help mailing list >> [email protected] >> <mailto:[email protected]> >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> >> > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120916/9a7ecfb1/attachment-0001.htm > > > ------------------------------ > > Message: 2 > Date: Sat, 15 Sep 2012 09:12:50 -0700 (PDT) > From: Han Bin <[email protected]> > Subject: Re: [Tinyos-help] Data Logging with Telosb > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > > Dear Eric, > Thank for your help. It's very useful for me. I'll follow the guidance as > you suggested. > Have a nice weekend! > > Thanks, > Han Bin > -- > View this message in context: > http://old.nabble.com/Data-Logging-with-Telosb-tp34435696p34436184.html > Sent from the TinyOS - Help mailing list archive at Nabble.com. > > > > ------------------------------ > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > End of Tinyos-help Digest, Vol 113, Issue 31 > ********************************************
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
