Re: [avr-gcc-list] programming the at90can128

[Graham Davies]

Well, maybe it's not so off-topic after all, then.  I can certainly post the
JTAG ID, which I recall AVaRICE prints right out.  The "config params" would
mean snooping the serial communication between AVR Studio and the JTAG
interface, right?  I don't have a good way of doing that.

I'm sending an AVR ICE-Cube to Brian Dean for him to look at, but I don't
suppose that matters as he has an Atmel JTAG ICE already, I think.

Maybe the XML Part Description Files included with AVR Studio contain the
necessary information.  For example, the ID of the AT90CAN128 is given as
0x0978103F (for the ATmega128, it's 0x0970203F).  After this, there are
strings of bytes in tags such as ucRead, ucWrite, etc.  Perhaps this is what
AVaRICE needs?

Graham.


----- Original Message ----- 
From: "Theodore A. Roth" <address@hidden>
To: "Graham Davies" <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, November 16, 2004 10:15 AM
Subject: Re: [avr-gcc-list] programming the at90can128


> On Tue, 16 Nov 2004, Graham Davies wrote:
<snip>
> > The AVR ICE-Cube works fine (as far as I can tell) with AVaRICE, but the
> > version I have does not support the AT90CAN128 and does not like the
JTAG ID
> > it returns.  Presumably, it's only a matter of time until support is
added.

> If you could post the JTAG ID and possibly a capture of the config
> params that get sent down to the jtagice box by avarice/avrstudio, then
> we could added support for the can128 to avarice rather quickly. I don't
> have a can128 part so I can't really look into that.
>
> [I seem to recall Brian Dean saying that he was working with the can128.
> Maybe he can lend a hand with the data we need to add support in
> avarice. Wink, wink. Nudge, nudge.]
>
> ---
> Ted Roth
> PGP Key ID: 0x18F846E9
> Jabber ID: address@hidden