Yes, I have avr-objcopy and avr-gcc installed. They¹re located in the /usr/local/bin directory. TOSDIR=/Users/greg/Documents/Sources/tinyos-1.x/tos TOSROOT=/users/greg/Documents/Sources/tinyos-1.x
These are correct, as far as I can tell. Inside the TOSDIR path are the folders ³interfaces²,²lib²,²platform²,²sensorboards²,²system², and ³types². TOSROOT just points to my tinyos directory, like yours does. MIB520=/dev/tty.usbserial-XBPSJ9TXA MOTECOM=/dev/tty.usbserial-XBPSJ9TXB I¹m using the USB version (MIB520), and so I think that part¹s correct. It¹s just supposed to point to where the serial port is, correct? What about MOTECOM? What does this mean as far as not being able to find ³Timer²,²Leds², etc.? Thanks, Greg Turnipseed From: Sarfraz Nawaz <[EMAIL PROTECTED]> Date: Tue, 17 Apr 2007 11:21:01 +1000 To: Michael Schippling <[EMAIL PROTECTED]> Cc: Greg Turnipseed <[EMAIL PROTECTED]>, tinyos-help <[email protected]> Subject: ***SPAM*** Re: [Tinyos-help] Complete Novice Question: Installing TinyOS and Compiling on MacOSX 10.4 for MICA Greg, avr-objcopy is a part of avr-binutils. Did you install the avr-binutils and avr-gcc? If yes, can you find out where it lives in your filesystem. You should also carefully check your environment variables and see if they are setup properly and are pointing to correct places. On 4/17/07, Michael Schippling <[EMAIL PROTECTED]> wrote: > now it's gettin weird again... > those interface defs are in tos/interfaces > > Perhaps you do not have the pointers to the tos code setup correctly. > I have these two env vars: > > TOSDIR=/cygdrive/C/cygwin/opt/tinyos- 1.1.7/tos > TOSROOT=C:/cygwin/opt/tinyos-1.1.7 > > At least one is the result of cygwin trying to help us poor Widows > abusers by imitating (sort of almost kinda) the UNIX file structure. > Perhaps both should be set to point to your installation... > > And just to be forward looking I have these two vars for downloading > and talking to the MIB510 that I use. I don't know what you will use > for downloading, but it'll probably be another struggle: > > MIB510=COM3 > [EMAIL PROTECTED]:mica2 > > > MS > > Greg Turnipseed wrote: >> > It started with me trying to use "make mica", and it gives me the error >> that >> > there's no rule to make target 'mica.' This, along with a host of other >> > errors (including not being able to correctly read the Makerules file in >> > tinyos-1.x/apps), led me to find another way of compiling the code. After >> > browsing the Internet for hours, I learned the ncc command. Then that had >> > its own problems, and I ended up needing to reinstall nescc (and thanks to >> > you guys' help), change ncc to point to the right place. Now I'm able to >> > make ncc work...kind of. I can see that it's calling nescc, but now >> nescc's >> > having problems. You were right (I think) about the board. I changed it >> to >> > micaz, and now it gives me compilation errors. Lots of complaining about >> > undeclared variables and such, but the most troublesome things are as >> > follows: >> > >> > Blink.nc:44 <http://Blink.nc:44> : cannot find `StdControl' >> > Blink.nc:45 <http://Blink.nc:45> : cannot find `Timer' >> > Blink.nc:46 <http://Blink.nc:46> : cannot find `Leds' >> > >> > Since the latter two are built-in functions, I wonder if I'm supposed to >> > have compiled something else before running ncc? >> > >> > Thanks again. >> > -Greg Turnipseed >> > >> > >>> >> From: Michael Schippling <[EMAIL PROTECTED]> >>> >> Date: Mon, 16 Apr 2007 13:48:35 -0600 >>> >> To: Greg Turnipseed < [EMAIL PROTECTED]> >>> >> Cc: Sarfraz Nawaz <[EMAIL PROTECTED]>, tinyos-help >>> >> < [email protected]> >>> >> Subject: Re: [Tinyos-help] Complete Novice Question: Installing TinyOS >>> and >>> >> Compiling on MacOSX 10.4 for MICA >>> >> >>> >> hmm...I'll bet ya a dollar you don't have a "mica" board... >>> >> So you want probably mica2 or micaz as in "make mica2". >>> >> >>> >> But: Yay! you are getting someplace. Why it was trying to exec >>> >> stuff in (I assume) your own directory tree is a mystery that >>> >> may re-bite you someplace else. But: Onward. >>> >> >>> >> In general ncc will put the results in build/[platform] >>> >> so your main.exe ought to be there with app.c (which is the >>> >> nescc 'preprocessor' output -- all the TOS and app source >>> >> munged together in one file to be compiled to object code). >>> >> >>> >> What you want finally is the .srec file to be downloaded to >>> >> the micaX card. There is another step in-between that puts >>> >> the moteID into the .srec...all of these things _should_ >>> >> be executed from the makefile in the right order. I think >>> >> that's where this all started though, right? >>> >> >>> >> MS >>> >>
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
