Hi All,
I just did an pull on current head of tree and build but I was not able to
attach to my bus blaster probe to mips board running a microAptiv core after
that. Below is the output I received:
Open On-Chip Debugger 0.9.0-dev-00092-g287d6e0-dirty (2014-07-08-14:12)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
adapter speed: 15000 kHz
adapter_nsrst_delay: 100
Error: session's transport is not selected.
Info : session transport was not selected, defaulting to JTAG
jtag_ntrst_delay: 100
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
scan delay: 20000 nsec
running in fast queued mode
mAUC.tcl(updated 20140508)
reb (Setup for an EJTAGBOOT indicated reset via
Sharta-A S8.)
rnb (Setup for a NORNALBOOT indicated reset via
Sharta-A S8.)
fastq <mode> (mode 0/1 disables/enables 'fast queued mode'.)
myload (Example of FASTDATA load, verify, invalidate.)
<CP0RegName> ?<new-value>? (All CP0 registers now accessible by name.)
cp0 (dump all CP0 registers.)
Info : clock speed 15000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: mAUC.cpu: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Reset Detected
Polling target mAUC.cpu failed, GDB will be halted. Polling again in 100ms
Info : Reset Detected
Polling target mAUC.cpu failed, GDB will be halted. Polling again in 300ms
Info : Reset Detected
target state: reset
Polling target mAUC.cpu failed, GDB will be halted. Polling again in 700ms
Info : Reset Detected
target state: reset
Polling target mAUC.cpu failed, GDB will be halted. Polling again in 1500ms
Info : Reset Detected
target state: reset
Polling target mAUC.cpu failed, GDB will be halted. Polling again in 3100ms
Looking back at the check-in's and a little debug, I discover the changes to
ftdi.c (Change-Id: I90123c666e05a1c26f1e164625e82d766a3e3744 - 6/22/2014
1;23PM) was causing the failure. I removed the updates and was able to connect.
The "cfg" file for the bus blaster is:
#
# Bus Blaster
#
# http://dangerousprototypes.com/docs/Bus_Blaster
#
interface ftdi
ftdi_device_desc "Dual RS232-HS"
ftdi_vid_pid 0x0403 0x6010
ftdi_layout_init 0x0c08 0x0f1b
ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
ftdi_layout_signal nSRST -data 0x0200 -noe 0x0800
adapter_khz 15000
So are my question is this a configuration issue or bug?
Kent
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
