Hello I tried this and cannot get the JTAGKey2 to work - there are endless errors reported when trying to load code although openocd does initialize and see the jtag chain.
AT this link http://www.zylin.com/zy1000/openocd.pdf which appears to be a manual for OpenOCD 0.3.0 there is mention of a JTAGKey2 layout: "ft2232_layout name ..... jtagkey Amontec JTAGkey and JTAGkey-Tiny (and compatibles) jtagkey2 Amontec JTAGkey2 (and compatibles)" This seems to imply that there is a difference on the PCB. Is that right? Len -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Wookey Sent: 23 October 2009 02:40 PM To: [email protected] Subject: Re: [Openocd-development] jtagkey2 +++ Leonard Heins [2009-10-23 13:45 +0200]: > Hello > > > > We are currently using OpenOCD 0.2.0 on 32bit Windows with JTAGKeys from > Amontec. We have just got a JTAGKey2 so we can run at 30MHz. > > > > Do we need a new USB driver and a new version of OpenOCD (including > jtagkey2.cfg) to use this new debugger? If so, are binaries for 32bit windows > available anywhere for download. The USB manufacturer and prodcut IDs are the same for JTAGKey 1 and 2 (is that right?), so the only thing that changes is the Product string. (I wish they'd either changed both pid _and_ desc, or neither. Just changing one is unhelpful as it requires what seems to be a gratuitous config change. Which means the openocd config changes from : interface ft2232 ft2232_device_desc "Amontec JTAGkey" ft2232_layout jtagkey ft2232_vid_pid 0x0403 0xcff8 to: interface ft2232 ft2232_device_desc "Amontec JTAGkey-2" ft2232_layout jtagkey ft2232_vid_pid 0x0403 0xcff8 Openocd itself shoulnd't need to change at all. Wookey -- Principal hats: iEndian - Balloonboard - Toby Churchill - Emdebian http://wookware.org/ _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
