Sergey: Have you been able to resolve this yet? I have a similar problem trying to obtain TinyOS support for an ATmega1281 processor. I have TinyOS applications successfully running on a 165P and 325 processor, and wasn't expecting to have to upgrade my tool chain to support the 1281!
I chose to update to the latest stable versions: binutils 2.17, gcc 4.1.1, and avr-libc 1.4.5. I'm compiling for a TinyOS 1.1 cygwin environment with the "TinyOS 1.2" tool chain. I'm configuring and installing the gcc tools into a new directory, and have the new 'bin' directory in my path as recommended in this excellent write up: http://www.nongnu.org/avr-libc/user-manual/install_tools.html However, I am also finding that my avr-libc configuration step does not detect the presence of the 'new' AVR MCUs. On a related note, any idea if the binutils 2.16 TinyOS patch will work for the 2.17 release? (I knew there was something else I'd forgotten to do!) - Tom -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ?????? ?????? Sent: Wednesday, September 27, 2006 8:42 AM To: David Gay Cc: TinyOS-Help list Subject: [Tinyos-help] ?????: David! Please help with nesC Hello, David! I have removed binutils and checked Binutils2.16's files - it wasnt patched! I was very surprized :). So, I reinstall it with my patch, reinstall gcc, libc. Then I've tryed to compile Blink with mica2 - it's works!!! Great! :-D But mica2 using ATmega128, and I need ATmega168. When I tryed to compile Blink for my platform, where mmcu=atmega168, I have got error that MCU name "atmega168" is unknown, then I've saw list of supported MCU - it was the exact copy of old AVRtools' list. Nothing was changed - as though, as if I didnt install new versions. :-/ I've typed in console "avr-gcc --target-help" and have saw this: -mmcu=[avr-name] select microcontroller variant [avr-name] can be: avr1 - AT90S1200, ATtiny1x, ATtiny28 avr2 - AT90S2xxx, AT90S4xxx, AT90S8xxx, ATtiny22 avr3 - ATmega103, ATmega603 avr4 - ATmega83, ATmega85 avr5 - ATmega161, ATmega163, ATmega32, AT94K Known MCU names: avr1 avr2 avr3 avr4 avr5 at90s1200 attiny10 attiny11 attiny12 attiny15 attiny28 at90s2313 at90s2323 at90s2333 at90s2343 attiny22 attiny26 at90s4433 at90s4414 at90s4434 at90s8515 at90s8535 at90c8534 at86rf401 attiny13 attiny2313 atmega603 atmega103 at43usb320 at43usb355 at76c711 atmega48 atmega8 atmega83 atmega85 atmega88 atmega8515 atmega8535 atmega16 atmega161 atmega162 atmega163 atmega165 atmega168 atmega169 atmega32 atmega323 atmega325 atmega3250 atmega64 atmega128 atmega645 atmega6450 at90can128 at94k That is, compiler knows my MCU! But cant using - libraries havent installed! Then, I've checked usr/avr/lib, but didnt saw object files for new MCUs. So, I tryed to reinstall Libc. In Libc tree: "./configure --build=`./config.guess` --host=avr" Configuring process showed me this: checking if avr-gcc has support for atmega48... no checking if avr-gcc has support for atmega88... no .......................................................................... checking if avr-gcc has support for atmega168... no In every line where script is checking support for new MCU, was word "no". And so, IMHO, libraries for new MCU werent installed, only old. It is very strange. The old version of avr-gcc (3.4.4) was removed. How it's checking MCU support and where? As you see, installed avr-gcc HAS support for new MCU, but the script isnt see it. Whats's wrong? Best regards Sergey _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
