Re: [Openocd-development] how to add a new target: avr32 AP7000

2009-02-17 Thread Rick Altherr
On Feb 17, 2009, at 7:57 AM, Holger Schurig wrote: On Tuesday 17 February 2009 14:34:02 Holger Schurig wrote: jtag newtap $_CHIPNAME cpu \ -irlen 5 \ -ircapture 0x1 \ -irmask 0xf \ -expected-id $_CPUTAPID I found the bsdl file: http://www.avr32.ru/AP7000.bsdl In this file I find

Re: [Openocd-development] how to add a new target: avr32 AP7000

2009-02-17 Thread Holger Schurig
On Tuesday 17 February 2009 14:34:02 Holger Schurig wrote: > jtag newtap $_CHIPNAME cpu \ >    -irlen 5 \ >    -ircapture 0x1 \ >    -irmask 0xf \ >    -expected-id $_CPUTAPID I found the bsdl file: http://www.avr32.ru/AP7000.bsdl In this file I find "attribute INSTRUCTION_LENGTH of AP7000: enti

Re: [Openocd-development] how to add a new target: avr32 AP7000

2009-02-17 Thread Holger Schurig
> Info : JTAG tap: avr32ap7000.cpu tap/device found: 0x21e8203f > (Manufacturer: 0x01f, Part: 0x1e82, Version: 0x2) > Info : JTAG Tap/device matched > Warn : Unexpected idcode after end of chain! 384 0x807f > Warn : Unexpected idcode after end of chain! 416 0x00ff > Warn : Unexpected idcode

[Openocd-development] how to add a new target: avr32 AP7000

2009-02-17 Thread Holger Schurig
I've an ICnova / Grasshopper board that I'd like to get supported via OpenOCD. As I'm willing to contribute this back, I'm using OpenOCD from subversion, currently 1370. My JTAG device is an Olimex USB-JTAG-TINY. I've started with a bogus "target/avr32ap7000.cfg" file which basically contains