New ebuild for dev-embedded. In recent times, GCC added support for the AVR series of microcontrollers. This has been quite the boon for those of us who write embedded applications for processors with "leaner" architectures. Recently, Atmel announced the availability of a JTAG box for the AVR. Until now, there was no way to interface to this device with GDB. AVaRICE runs on a POSIX machine and connects to gdb via a TCP socket and communicates via gdb's "serial debug protocol". This protocol allows gdb to send commands like "set/remove breakpoint" and "read/write memory". AVaRICE translates these commands into the Atmel protocol used to control the AVR JTAG ICE. Connection to the AVR JTAG ICE is via a serial port on the POSIX machine. Because the GDB <---> AVaRICE connection is via a TCP socket, the two programs do not need to run on the same machine. In an office environment, this allows a developer to debug a target in the lab from the comfort of their cube (or even better, their home!)
Created attachment 54470 [details] Proposed ebuild for avarice 2.3
Created attachment 54471 [details] Metadata for avarice
I submitted an ebuild for gdb (Bug #88169) that would allow it to be built for different targets. When that is put into portage I will submit a patch to crossdev so that gdb can also be built with the rest of the avr toolchain.
Well done.
sys-devel/crossdev-0.9.8 supports building avr-gdb, as required by AVaRICE.
Scott: can you review this ebuild ?
the ebuild should be modified to RDEPEND on the new cross-avr/gdb. It seems that no special tool are required in DEPEND, standard system tools should be enough. Maybe DEPEND can be set on sys-devel/gcc.
I am out of town until Sunday. I will check it when I get back. Sorry for the delay. Scott =)
Woops. It seems I dropped the ball here. I will look at this tomorrow. Sorry. Scott =)
The ebuild builds fine on my x86 and amd64 machines. The only thing I had to change was add ~amd64 to the keywords. I don't have a good way to test whether avarice itself works, but it does run. It just complains that it can't find the jtag emulator. Scott =)
thanks, now in portage
