Am 21. Oktober 2015 21:52:39 MESZ, schrieb "Jörg Wunsch"
:
>You could try fiddling a custom cable with serial terminators (about
>100 ohms) on each driving (tx) side of a line (TDO, TCK, TDI) to reduce
>ringing.
Sorrry, that was related to JTAG which has dedicated
As Element Green wrote:
> Thank you for your reply. I downgraded the firmware to 7.21 (from AVR
> Studio 5).
I just upgraded another Dragon to 7.38 (decimal), and it works without
troubles using AVaRICE (SVN version) on my ATxmega16D4 board.
> I attempted to use the Dragon to connect to 2
Hello Joerg,
On Tue, Oct 20, 2015 at 9:35 AM, Joerg Wunsch wrote:
> As Element Green wrote:
>
> > Thank you for your reply. I downgraded the firmware to 7.21 (from AVR
> > Studio 5).
>
> I just upgraded another Dragon to 7.38 (decimal), and it works without
> troubles
Hello Joerg,
On Tue, Oct 20, 2015 at 9:49 AM, Element Green
wrote:
>
>> How long's your cable? The levelshifters/drivers on the Dragon are
>> known to be fairly weak. In general, the cables that come with an STK500
>> work well, they are about 15 cm long.
: Element Green [mailto:elem...@elementsofsound.org]
Sent: Wednesday, 21 October 2015 12:40 p.m.
To: Joerg Wunsch;
Subject: Re: [AVaRICE-user] AVR Dragon not working with atxmega16d4
Hello Joerg,
On Tue, Oct 20, 2015 at 9:49 AM, Element Green
<elem...@elementsofsound.org<mailt
>
> Arnim
>
>
>
>
>
> *From:* Element Green [mailto:elem...@elementsofsound.org]
> *Sent:* Wednesday, 21 October 2015 12:40 p.m.
> *To:* Joerg Wunsch;
> *Subject:* Re: [AVaRICE-user] AVR Dragon not working with atxmega16d4
>
>
>
> Hello Joerg,
>
>
As Element Green wrote:
> command[0x02, 1]: 02 03 06
> recv: 0x1b
> recv: 0x01
> recv: 0x00
> recv: 0x01
> recv: 0x00
> recv: 0x00
> recv: 0x00
> recv: 0x0e
> sDATA: reading 1 bytes
> read: ae
> recv: 0xb1
> recv: 0x4b
> CRC OK
> Got message seqno 1 (command_sequence == 1)
> response: AE
> set
I've added some debugging output below. For testing purposes I modified
the code to ignore the unknown 0xAE return code being hopeful that it would
work anyways, which it didn't. The return code 0xA4 which occurs with the
next command indicates RSP_ILLEGAL_EMULATOR_MODE, so it would seem there