"avrxmega6" does not work either :(
############################################################ ajay@ajay-HP-15-Notebook-PC:~$ avr-gcc -mmcu=avrxmega6 ledblink.c -o ledblink.o In file included from ledblink.c:2:0: /usr/lib/avr/include/avr/io.h:428:6: warning: #warning "device type not defined" [-Wcpp] # warning "device type not defined" ^ In file included from ledblink.c:3:0: /usr/lib/avr/include/util/delay.h:90:3: warning: #warning "F_CPU not defined for <util/delay.h>" [-Wcpp] # warning "F_CPU not defined for <util/delay.h>" ^ /usr/lib/avr/include/util/delay.h:95:3: warning: #warning "Compiler optimizations disabled; functions from <util/delay.h> won't work as designed" [-Wcpp] # warning "Compiler optimizations disabled; functions from <util/delay.h> won't work as designed" ^ ledblink.c: In function ‘main’: ledblink.c:16:9: error: ‘DDRC’ undeclared (first use in this function) DDRC |=1<<PC2; /* PC2 will now be the output pin */ ^ ledblink.c:16:9: note: each undeclared identifier is reported only once for each function it appears in ledblink.c:16:19: error: ‘PC2’ undeclared (first use in this function) DDRC |=1<<PC2; /* PC2 will now be the output pin */ ^ ledblink.c:19:17: error: ‘PORTC’ undeclared (first use in this function) PORTC &= ~(1<<PC2);/* PC2 LOW */ ############################################################ On Fri, Nov 20, 2015 at 8:23 AM, Adisak Anusornsrirung <adi...@fitel.co.th> wrote: > Did you try > -mmcu=avrxmega6 > > > avrxmega6 “XMEGA” devices with more than 128 KiB of program memory. > mcu = atxmega128a3, atxmega128a3u, atxmega128b1, atxmega128b3, > atxmega128c3, atxmega128d3, atxmega128d4, atxmega192a3, atxmega192a3u, > atxmega192c3, atxmega192d3, atxmega256a3, atxmega256a3b, *atxmega256a3bu*, > atxmega256a3u, atxmega256c3, atxmega256d3, atxmega384c3, atxmega384d3. > avrxmega7 “XMEGA” devices with more than 128 KiB of program memory and > more than 64 KiB of RAM. > mcu = atxmega128a1, atxmega128a1u, atxmega128a4u. > > > Credits: https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html > > > > > > *From:* Ajay Garg <ajaygargn...@gmail.com> > *Sent:* Friday, November 20, 2015 8:19 AM > *To:* Shawn Rich <rich.sh...@gmail.com> > *Cc:* avr-gcc-list@nongnu.org > *Subject:* Re: [avr-gcc-list] avrxmega7 device-not-found > > Same response Shawn :: > > > ############################################################ > ajay@ajay-HP-15-Notebook-PC:~$ avr-gcc -mmcu=atxmega256a3bu ledblink.c -o > ledblink.o | grep 256 > In file included from ledblink.c:2:0: > /usr/lib/avr/include/avr/io.h:428:6: warning: #warning "device type not > defined" [-Wcpp] > # warning "device type not defined" > ^ > In file included from ledblink.c:3:0: > /usr/lib/avr/include/util/delay.h:90:3: warning: #warning "F_CPU not > defined for <util/delay.h>" [-Wcpp] > # warning "F_CPU not defined for <util/delay.h>" > ^ > /usr/lib/avr/include/util/delay.h:95:3: warning: #warning "Compiler > optimizations disabled; functions from <util/delay.h> won't work as > designed" [-Wcpp] > # warning "Compiler optimizations disabled; functions from <util/delay.h> > won't work as designed" > ^ > ledblink.c: In function ‘main’: > ledblink.c:16:9: error: ‘DDRC’ undeclared (first use in this function) > DDRC |=1<<PC2; /* PC2 will now be the output pin */ > ^ > ledblink.c:16:9: note: each undeclared identifier is reported only once > for each function it appears in > ledblink.c:16:19: error: ‘PC2’ undeclared (first use in this function) > DDRC |=1<<PC2; /* PC2 will now be the output pin */ > ^ > ledblink.c:19:17: error: ‘PORTC’ undeclared (first use in this function) > PORTC &= ~(1<<PC2);/* PC2 LOW */ > ############################################################ > > > Clearly either I am missing something, or something is really screwed up > :-\ > > > > On Fri, Nov 20, 2015 at 2:38 AM, Shawn Rich <rich.sh...@gmail.com> wrote: > >> The avr libc user manual shows that part under supported devices. Have >> you tried it? >> >> http://www.nongnu.org/avr-libc/user-manual/index.html >> >> >> shawn >> >> On Thu, Nov 19, 2015 at 3:56 PM, Ajay Garg <ajaygargn...@gmail.com> >> wrote: >> >>> Senthil, >>> >>> (I am just a newest newbie, but,) Assuming your hypothesis is correct, >>> what should I pass to compile the code on >>> http://www.atmel.com/tools/XMEGA-A3BUXPLAINED.aspx, using *Atmel >>> ATxmega256A3BU microcontroller*? >>> >>> >>> _______________________________________________ >>> AVR-GCC-list mailing list >>> AVR-GCC-list@nongnu.org >>> https://lists.nongnu.org/mailman/listinfo/avr-gcc-list >>> >>> >> >> >> -- >> >> ~/shawn >> > > > > -- > Regards, > Ajay > > ------------------------------ > _______________________________________________ > AVR-GCC-list mailing list > AVR-GCC-list@nongnu.org > https://lists.nongnu.org/mailman/listinfo/avr-gcc-list > > -- Regards, Ajay
_______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-gcc-list