Re: [AVaRICE-user] Fwd: Debugging AVR XMEGA with the Dragon

[Joerg W. <j...@ur...>]

As Omar Choudary wrote:

> and after a bit of looking through the manpage I've added the "--xmega"
> flag but got a similar error.
> This is the output:
> AVaRICE version 2.10, Feb  8 2010 07:22:54
...
> Reported JTAG device ID: 0x9842
> No configuration available for device ID: 9842

OK, that looks much better than your first attempt.

Well, AVaRICE is meanwhile at version 2.13 :), yours is 2.10.

If you look into the current src/devdescr.cc, you'll notice that an
entry with device ID 0x9842 does exist now.  So I'd really recommend
an upgrade.

> c) In the avarice manpage says that the atxmega128a1 is only supported
> through the JTAG ICE mkII device. Will this device work for the xmegas?

I'm not sure if you could force an ATxmega128A1 in place of your 256
KiB device.  It might work to some degree, but I'd really ask you to
upgrade instead.  There are many bugfixes now, too.

There's one other thing to keep in mind: for all AVR Dragon (and
JTAGICEmkII) firmware versions *prior* to 7.x, AVaRICE has no chance
to set breakpoints for Xmega devices.  The Xmega breakpoint handling
in these earlier firmware revisions was completely undocumented, and
has never been reverse-engineered.  Starting with firmware 7.x, the
Xmega breakpoint handling is still undocumented but could reasonably
be reverse-engineered, so AVaRICE can handle them now.  However, this
*requires* AVaRICE with at least version 2.12, and you have to find a
Windows machine with Atmel Studio 6 installed in order to have them
upgrade your Dragon's firmware.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)