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

2013-01-15 Thread Joerg Wunsch
As Omar Choudary wrote: > I should have updated avarice before starting the discussion, sorry > about that. No problem, glad it works now! I've got plans to also implement watchpoints (data breakpoints) for the Xmega. They are currently still missing. -- cheers, J"org .-.-. --.

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

2013-01-15 Thread Omar Choudary
Thanks for the details Joerg. After the update it works fine. I should have updated avarice before starting the discussion, sorry about that. Cheers, Omar On Tue, Jan 15, 2013 at 9:11 PM, Joerg Wunsch wrote: > As Omar Choudary wrote: > > > and after a bit of looking through the manpage I've

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

2013-01-15 Thread Joerg Wunsch
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 look

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

2013-01-15 Thread Omar Choudary
Hello, I am in a situation where it would be extremely helpful to be able to use my dragon to debug an xmega256A3U. Unfortunately, after running my avarice script (which used to work for the AT90USB1287), I got the following error: No configuration available for device ID: 4c0 Then I found this