Re: [AVaRICE-user] AVR Dragon not working with atxmega16d4

[Element G. <el...@el...>]

Hello Joerg,

On Tue, Oct 20, 2015 at 9:49 AM, Element Green <el...@el...>
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.  Anything longer might cause
>> troubles.
>>
>
>
> I had that thought as well about the cable length after reading something
> to that effect on a forum post.  My guess is that that is the issue now
> that you mention it again, though I got sidetracked by the thought that it
> was a version incompatibility.  The cable I have came with a ZeptoProg II
> programmer and is probably about 10 inches long.  I'll get some shorter
> ones and see if that makes a difference.  Perhaps the 0xAE code can be used
> to identify cable length issues.  Guess I will see.
>
>

So I shortened the cable by removing the connector, cut it to about 4
inches and then put the connector back on.  It still was getting the same
error code with my custom PCB, but it goes through a motherboard
interconnect plus a few extra inches.  So I then tried it on the little
development board I have and it came back with a device ID which is
currently unsupported (the xmega128d4) which it was not doing with a longer
cable.  So it seems like it would likely work if the interconnect was not
there.  I cut the cable to 2 inches and still same 0xAE error code.

I'm thinking of getting an MKII clone like this one since they seem to be
available for under $43 online:
http://www.wvshare.com/product/USB-AVR-JTAGICE-XPII.htm

Any idea if those will work OK with debugging or if it might work better
than the Dragon in regards to cable length?  Guess the easiest thing to do
is just try it.



>
>
>> --
>> cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL
>>
>>
>

Cheers.

Element