Hi Joerg,
Yes, I've finally found the Atmel place where they keep their modified
tarballs and build script. A pity that they don't contribute the
patches... I'm thinking in working the patches out by myself (at least
for binutils and gcc), so that I can use gcc-4.8.2 rather than 4.8.1...
Also, on avarice, playing with the options, I discover that --detach is
the one that causes that timeout behaviour, otherwise I can connect
running avr-gdb in another process (xterm window). I'll indicate that to
the avarice list, see if somebody finds out what could be wrong.
Seems that there is a script in avarice that creates io reg definitions
for gdb out of a header file in avr-libc. That and copying an existing
device description in avarice sources, then modifying it by hand seems
to do the trick for the time being.
Thanks anyway for the context.
Regards
David
----------------------------------------------------------------------
Message: 1
Date: Fri, 14 Feb 2014 09:04:25 +0100 (MET)
From:j...@uriah.heep.sax.de (Joerg Wunsch)
To:avr-gcc-list@nongnu.org
Subject: Re: [avr-gcc-list] avr-libc does not have support for
ATxmega16a4u or ATxmega32a4u
Message-ID:<20140214080425.8238...@uriah.heep.sax.de>
Content-Type: text/plain; charset=us-ascii
David Fernandez<dfernan...@solarflare.com> wrote:
Anybody knows if there is a script to create the io files for these two
processors? or if there is some procedure to create them?
Should be possible, but it's more than the IO header files. Some #ifdefs
need to be extended, too.
Alas, since the day when Anitha Boyapati has left the Atmel team that
handles the AVR tools, there has not been much contribution back from
Atmel to avr-libc. Instead, they maintain their own set of patches
(until it will eventually become unmaintainable ...).
I seem to have problems with avarice, connecting avr-gdb to target and
it might be that I have to generate the right stuff out of the right
libc io file using one of the avarice scripts...
I don't think that's going to help much. I've seen your message to
the AVaRICE list, but didn't have the time to analyze your traces.
Ping me again in case I might forget about it. (Independently, it
might make sense to file an official bug report.)
-- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ Never trust an operating system you don't have
sources for.
_______________________________________________
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
