AVR Toolchain bug list

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

A link to the AVR toolchain bug list can be found on the avr-libc home page, or here:

http://www.nongnu.org/avr-libc/b...

This list contains GNU Binutils bugs, and AVR GCC bugs.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The currently open bugs for avr-libc can be found here:

https://savannah.nongnu.org/bugs/?group=avr-libc

AVRDUDE:

https://savannah.nongnu.org/bugs/?group=avrdude

Finally AVaRICE (rather low volume, not many users are submitting
reports there):

http://sourceforge.net/tracker/?atid=425407&group_id=39505&func=browse

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I've updated the master toolchain list to add the links (that Joerg gave above) to the avr-libc, avrdude, and avarice bug lists. I've also added a list of GDB bugs for the AVR target.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This is my first foray into AVR micros. I gave up attempting to use AS6; too many hang-ups. I'm now rebuilding an old ATmega8a system using command-line avr-gcc, avr-as and avr-ld. Learning as I go, I've had to convert the original source directives from IAR to AVR-Gnu.

Presently, I'm stuck trying to generate a viable hex file from C and Assembly objects. Please anyone who's used avr-ld (or GNU ld), I could use your help. Post or send me sample linker scripts, if you have them.

Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

This is my first foray into AVR micros. I gave up attempting to use AS6; too many hang-ups.

This is the second post where you claim this with no details.

I'm not saying that AS6 is without faults, but if you told us about them they might be resolved.

One way to get all the linker scripts would be to install the WinAVR package. Then you would also get the MFile utility, which has a template makefile where you can deduce what commands are needed to generate a valid Inte Hex file.

Personally, I've never actually invoked avr-ld literally, but have always relied on letting the compiler driver do this (i.e. avr-gcc).

In the MFile utility tempate makefile the link stage rule is

%.elf: $(OBJ)
	@echo
	@echo $(MSG_LINKING) $@
	$(CC) $(ALL_CFLAGS) $^ --output $@ $(LDFLAGS)

which might look like mumbo-jumbo, but essentially it does

avr-gcc   --output  

Since the compiler flags will include the -mmcu flag the linker knows which linker script to pull. (I've never needed to tinker with an AVR linker script either).

The Hex file is produced by the avr-objcopy utility (using the ELF file as input).

"He used to carry his guitar in a gunny sack, or sit beneath the tree by the railroad track. Oh the engineers would see him sitting in the shade, Strumming with the rhythm that the drivers made. People passing by, they would stop and say, "Oh, my, what that little country boy could play!" [Chuck Berry]

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Totally agree that you should use Mfile but if you don't want to download the whole of WinAVR get the .zip or tar.gz from here:

http://www.sax.de/~joerg/mfile/

You need tcl/tk to run it. To get a prebuilt copy for Windows go to http://www.tcl.tk/software/tcltk... while for Linux use something like "apt-get install tcl" (Ubuntu).

In fact even without tcl/tk you can simply take the makefile_template file that is included and hand edit it for your own project (the Mfile utility just makes this editing a bit simpler using menu selections).

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

There is also the following list:

http://www.mikrocontroller.net/a...

The list is maintained by hand and mostly about avr-gcc, i.e. the compiler driver and the compiler proper.

avrfreaks does not support Opera. Profile inactive.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Atmel AVR 8-bit Toolchain 3.5.4 (sept 2016 release [newest release as of this post]) - Windows and Linux and Linux 64.... atmega328pb support is broken, missing the nessesary includes and defines... I have submitted a ticket to Atmel support regarding the issue.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Surely this is a consequence of the split recently made between compiler/tools and "device packs". Sounds like your device pack is out of date.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I believe that split was for AS7 only. There does not seem to be any device packs for "Atmel AVR 8-bit Toolchain 3.5.4" that I can find. Only AS7 uses device packs from what I have gathered. All the other devices seem to all work out of the box without any issues, the PDF documentation "avr8-gnu-toolchain-3.5.4.1709-readme.pdf"" implies all the "supported devices" listed in the PDF work out of the box, and they indeed do, except atmega328pb. The atmega328pb has been out since 2015, and the latest device tool chain supposedly added support sometime before the latest sept 2016 release. I believe I can manually add support to the tool chain by creating the necessary port defines and includes etc. But it seems to be a tool chain issue. I suppose it's possible others using the atmega328pb have been using AS7 instead of the standalone toolchain, I know others on the forum initially reported an issue with AS7 and support for the chip, but that issue has since been resolved with the device packs you speak of.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi, this (sticky) thread was not opend to report or diskuss bug, but just _point_ to known lists of bugs and problems.  Thanks.
 

avrfreaks does not support Opera. Profile inactive.