Re: [Openocd-development] ST32-PerformanceStick

[Rick Altherr]

The error messages indicate that we are talking to the interface, but the JTAG signals don't appear to be valid. I don't know anything about the ST32-PerformanceStick, but I'd check pinout and voltage rails. OpenOCD is trying to talk to the JTAG tap and is just getting bogus data. That is almost always a hardware problem.

Rick


On Mar 9, 2009, at 7:23 AM, Michael Jäntsch wrote:

A run with -d 3 or 'debug_level 3' would clarify exactly where in OpenOCD we get a failure, but it looks a lot like the JTAG chain validation failed which is the first thing we do. It is also possible that the JTAG clock speed is wrong (it appears to be set to 500kHz, but you don't set it explicitly).

Hello,


chip but still not to the ST32-PerformanceStick.

My openocd.cfg:
source [find target/stm32stick.cfg]

# ftdi interface
interface ft2232

ft2232_device_desc "STM32-PerformanceStick A"
ft2232_layout stm32stick
ft2232_vid_pid 0x0640 0x002d

gdb_port 4789

and I get the following
Open On-Chip Debugger 1.0 (2009-03-09-14:42) svn:1405


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $
500 kHz
Error: JTAG communication failure, check connection, JTAG interface,
target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned
0x7FFF. tap=stm32_hitex.cpu pos=0 expected 0x1 got 3
Warn : Could not validate JTAG chain, continuing anyway...
Warn : Invalid ACK in SWJDP transaction
Warn : Invalid ACK in SWJDP transaction
Warn : Invalid ACK in SWJDP transaction
Warn : Invalid ACK in SWJDP transaction
Warn : Block read error address 0xe000ed00, count 0x1
Warn : no telnet port specified, using default port 4444
Warn : no tcl port specified, using default port 6666
Warn : Invalid ACK in SWJDP transaction

Any ideas?

Thanks
Michael


Holger Schurig schrieb:

I obviously had both problems. I needed to set the vid/pid in the config file plus the permission problem. I fixed this and got one step further. But it is still not working. Openocd is obviously talking to the ft2232

Error: 30 161 ft2232.c:1506 ft2232_init_ftd2xx(): unable to
open ftdi device: 2

You might also have a permission problem in your /proc/bus/usb
(or the new location somewhere in /sys). In this
case, "strace -oa -efile ./openocd" and a careful reading of the
generated "a" file will show this.

Then add a proper /etc/udev/rules.d/XXX file to solve this.

--
Technische Universität München
Michael Jäntsch
Fakultät für Informatik
Robotics and Embedded Systems
Boltzmannstr. 3
85748 Garching bei München
michael.jaent...@in.tum.de
www6.in.tum.de


_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

--
Rick Altherr
kc8...@kc8apf.net


 -- Unsigned

"He said he hadn't had a byte in three days. I had a short, so I split it with him."

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development