Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40540 - [avr-binutils] avr toolchain does not recognize --mmcu=atxmega256a3u

Attached to Project: Community Packages
Opened by vincent (altrus) - Sunday, 25 May 2014, 02:02 GMT
Last edited by Anatol Pomozov (anatolik) - Tuesday, 26 January 2016, 14:34 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jakob Gruber (schuay)
Anatol Pomozov (anatolik)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When using avr-gcc for archlinux, specifying the -mmcu=atxmega256a3u device causes avr-gcc to fail with an error message specifying it as an invalid mcu. This is incorrect as sources compiled directly from Atmel binaries, and the man page associated with avr-gcc both specify this as a valid target device.

Moreover, we were able to target this device using avr-gcc 4.8.2.

Upgrading to avr-gcc 4.9.0 prevents us from compiling to our target device, an Atmel Controller AtxMega256a3u.

--- SAMPLE OUTPUT ---

avr-gcc -mmcu=atxmega256a3u -o foo.o foo.c

Known MCU names:
[List of devices]

[Note that atxmega256a3u is not listed as an option]


This task depends upon

Closed by  Anatol Pomozov (anatolik)
Tuesday, 26 January 2016, 14:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  avr-binutils 2.25
Comment by Jakob Gruber (schuay) - Monday, 26 May 2014, 14:20 GMT
I'm a little busy at the moment so it might take a while until I get around to debugging this.
Let me know if you find anything in the meantime.
Comment by Anatol Pomozov (anatolik) - Tuesday, 02 September 2014, 04:20 GMT
The error message comes from avr-as (assembler) that does not know about atxmega256a3u. You can see the same "List of devices" message if you run "avr-as --help".

So the issue really belongs to avr-binutils package. Version 2.24 does not know about atxmega256a3u. I checked binutils history and see that atxmega256a3u support was added upstream recently by commit. Not sure why it worked before.

commit 255d9eec05d83a5bcfad57303f29dc7ba3a2e027
Author: Denis Chertykov <chertykov@gmail.com>
Date: Thu Mar 6 18:59:05 2014 +0400

* gas/tc-avr.c: Add new devices
avr25: ata5272, attiny828
avr35: ata5505, attiny1634
avr4: atmega8a, ata6285, ata6286, atmega48pa
avr5: at90pwm161, ata5790, ata5795, atmega164pa, atmega165pa,
atmega168pa, atmega32a, atmega64rfr2, atmega644rfr2, atmega64a,
atmega16hva2
avr51: atmega128a, atmega1284
avrxmega2: atxmega16a4u, atxmega16c4, atxmega32a4u, atxmega32c4,
atxmega32e5, atxmega16e5, atxmega8e5
avrxmega4: atxmega64a3u, atxmega64a4u, atxmega64b1, atxmega64b3,
atxmega64c3, atxmega64d4
avrxmega6: atxmega128a3u, atxmega128b3, atxmega128c3,
atxmega128d4, atxmega192a3u, atxmega192c3, atxmega256a3u,
atxmega256c3, atxmega384c3, atxmega384d3
avrxmega7: atxmega128a4u
* doc/c-avr.texi: Ditto.
Comment by Anatol Pomozov (anatolik) - Tuesday, 26 January 2016, 14:34 GMT
This has been fixed with avr-binutils 2.25 release

$ avr-gcc -mmcu=atxmega256a3u -o foo.o foo.c
avr-gcc: error: foo.c: No such file or directory
avr-gcc: fatal error: no input files
compilation terminated.

Loading...