Hi ... I'm trying to use a self made JTag wiggler cable that on one end
has a DB25 ( parallel port ) interface and on the other a 20-Pin JTag
socket. The main cause of the errors I get when using openocd could be
from a faulty cable issue but I want to discard any possible
configuration problems with the application.
I'm using openocd-0.4 with this configuration file:
telnet_port 4444
gdb_port 3333
tcl_port 6666
source [find interface/parport.cfg]
source [find target/stm32.cfg]
init
reset halt
flash write_image erase /root/TETSCADA.bin 0x8000000 bin
resume
shutdown
logfile
My host is a normal PC running Ubuntu GNU/Linux 10.04 and my target is
an ARM MCU. As you can see in the configuration file I'm using the
parport.cfg config file that comes with openocd:
interface parport
parport_port 0
parport_cable wiggler
When I run my program:
# openocd -f openocd.cfg
I get the following error:
Open On-Chip Debugger 0.4.0 (2010-08-31-15:56)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
parport port = 0x0
1000 kHz
jtag_nsrst_delay: 100
jtag_ntrst_delay: 100
Info : clock speed 500 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Command handler execution failed
Warn : jtag initialization failed; try 'jtag init' again.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
error: -100
Command handler execution failed
I tried searching on the web and on your forums and mailing lists about
"error -100" but couldn't find any info about it. Could someone help ?
Thanks in advance ...
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
