Error jtag scan chain interrogation failed all ones

JTAG scan chain interrogation failed: all ones (OCD-300) #131

I’ve been trying to program the ESP32-WROOM-32E and ESP-DevKitC-v4 (based on 32E) modules over JTAG (both on MacOS 10.15.4 and Windows 10) for the past two days and every single try has failed following the same error. It’s worth mentioning that I erased the flash memories of these modules entirely before any attempt to program them over JTAG. This eliminates the possibility that the JTAG pins might be reconfigured for other purposes by the existing firmware.

I’ve used both SEGGER JLink and ESP-Prog during my tests using the standard JTAG pins, i.e. TMS, TDO, TDI, TCK, GND and Vref. After running this command:

As stated in the ESP-IDF JTAG Debugging page, such an error is most probably referring to a problem in pin connections.
However, I have checked them multiple times and I have no clue where this error originates from. I have gone through similar issues, but none has really been helpful for my case.

An interesting thing is, when I hold the EN button on the DevKit and run the command above, the error changes from Error: JTAG scan chain interrogation failed: all ones to Error: JTAG scan chain interrogation failed: all zeros . This also happens when I ground the TDO.

I get the exact same behavior no matter which debugger, JLink or ESP-Prog, I use. I’d be grateful if anyone has any advice.

The text was updated successfully, but these errors were encountered:

Источник

JTAG scan chain interrogation failed: all ones (on previously functional setup) #113

I’ve decided to try and debug my ESP32 chip once again, only to be welcomed by this:

I’m using ESP-32-WROOM chip on devkit and CJMCU-232H (FT232H) adapter.

I’ve tried disconnecting all connected devices from ESP32 and flashing hello_world example just to be sure to no avail. Moreover, some time ago I had no problems using this adapter and board with older version of openocd (sadly can’t say which one, but I had to build it separately back then).

The text was updated successfully, but these errors were encountered:

I am working on an FT4232HL board and got it working on Windows 10. I stumbled across the same error. My solution was to revert the WinUSB drivers back to the FTDI drivers (using Windows Device Manager), then again back to WinUSB with Zadig. At some point I also uninstalled the FTDI drivers and reinstalled «from scratch».

Check if your JTAG interface is ok by connecting the TDO input to ground. You should get the same error, but with «all zeroes». If that is the case, the interface should be OK.

This year we re-structured board and chip config files and now you should run it as smth like openocd -f board/esp32-wrover-kit-3.3v.cfg .

Tying GPIO 15 to ground suppresses the messages sent out to the serial port by the ROM bootloader (link).

It also causes the exact same issue shown above.

The fix is as easy as: Don’t do that — Remove the jumper from GPIO 15 to ground and try it again.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Error: JTAG scan chain interrogation failed: all ones (OCD-183) #83

So I have that error since severals weeks and tried many solutions but no one worked.

Hardware

• Esp32 devkit v1
• Wroom32 With Jtag port (those 6 little dots)
• jtag interface: ftdi ft2232H

Problem
I type:

binopenocd -s shareopenocdscripts -f interfaceftdiesp32_devkitj_v1.cfg -f boardesp-wroom-32.cfg

adapter speed: 20000 kHz
esp32 interrupt mask on
Info : ftdi: if you experience problems at higher adapter clocks, try the command «ftdi_tdo_sample_edge falling»
Info : clock speed 20000 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: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors

Here is what I tried:

• checked the wire
• checked the jtag connections (esp32 side and ftdi side)
• changed the wire
• checked the supply voltage
• checked ALL the pins if they where low/high/floating
• changed the usb drivers with zadig
• changed the chip (i got the same error with esp32 dev kit or wroom32)
• reseted with the EN pin
• forced boot mode (gpio0= 0 and gpio2=0)
• forced spi mode (gpio0= 1 and gpio2=

)

But something strange occured
I flashed a blink program in the esp32 devkit via USB. Then the error «All one» vanished and from here, I could use jtag connexion.
But I can’t do the same with the Wroom32, it only has jtag port.

If anyone has a little idea on what the heck is happening I would be glad to hear it.

The text was updated successfully, but these errors were encountered:

Источник

Receiving JTAG scan chain interrogation failed: all ones (OCD-144) #35

I’ve set up Ubuntu 16.04LTS on a Windows Surface Pro (2017) I7-256GB-8GB tablet using Oracle Virtual Box. It appears that there is a problem with OpenOCD. Neil Kolban, helped me compare against his hardware, which is identical to mine. His setup works, mine doesn’t, despite the fact that we’re running the exact same code (esp-idf-template example). The output below gives the output from openocd when it is executed. Neil’s running Ubuntu 17 (not sure of sub version) on an i7 tower computer.

The device I’m trying to use JTag with is the Epressif ESP32-DevKit-WRover v3. For JTAG, I have only the TDO, TDI, TMS, and TCK pins jumpered. I also have the TXD and RXD for the UART jumpered. I’m using the epsressif example of esp-idf-templ. The only thing changed in the profile via menuconfig was the clock speed (240MHz instead of 160MHz) and the /dev/ttyUSB0 was changed to /dev/ttyUSB1.

$ dmesg | grep -i tty
[ 0.004000] console [tty0] enabled
[ 0.817177] 00:02: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200) is a 16550A
[ 22.224208] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 22.228595] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB1
gnorkus@gnorkus-VirtualBox:

$ cd esp
gnorkus@gnorkus-VirtualBox:

/esp$ cd openocd-esp32
gnorkus@gnorkus-VirtualBox:

/esp/openocd-esp32$ id
uid=1000(gnorkus) gid=1000(gnorkus) groups=1000(gnorkus),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare)
gnorkus@gnorkus-VirtualBox:

/esp/openocd-esp32$ ls -l /dev/ttyUSB*
crw-rw—- 1 root dialout 188, 0 Apr 4 19:02 /dev/ttyUSB0
crw-rw—- 1 root dialout 188, 1 Apr 4 19:02 /dev/ttyUSB1
gnorkus@gnorkus-VirtualBox:

/esp/openocd-esp32$ sudo bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp32-wrover.cfg
[sudo] password for gnorkus:
Open On-Chip Debugger 0.10.0-dev-g07baed8 (2018-02-23-08:56)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
esp32 interrupt mask on
force hard breakpoints
Info : ftdi: if you experience problems at higher adapter clocks, try the command «ftdi_tdo_sample_edge falling»
Info : clock speed 20000 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: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : esp32: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
Info : esp32: Core was reset (pwrstat=0xFF, after clear 0xFF).
Error: cpu0: esp32_fetch_all_regs (line 165): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 165): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 165): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: cpu0: esp32_fetch_all_regs (line 192): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 192): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 192): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: Exception reading pc!

Info : active_cpu: 0, changed to 1, reson = 0xffffffff
Info : Target halted. PRO_CPU: PC=0x00000000 APP_CPU: PC=0x00000000 (active)
Error: cpu0: xtensa_write_memory (line 698): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 698): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 698): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 4 bytes at address 0x3FF5F064, data — a1, 3a, d8, 50, a1, 3a, d8, 50
embedded:startup.tcl:21: Error:
in procedure ‘init’
in procedure ‘ocd_bouncer’
in procedure ‘esp_smp_break_config’
in procedure ‘esp32’ called at file «share/openocd/scripts/target/esp32.cfg», line 54
in procedure ‘ocd_bouncer’
in procedure ‘esp_core_halt’
in procedure ‘esp32’ called at file «share/openocd/scripts/target/esp32.cfg», line 44
in procedure ‘ocd_bouncer’
at file «embedded:startup.tcl», line 21

cpu0: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
cpu1: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
`

The text was updated successfully, but these errors were encountered:

Источник

Openocd error jtag scan chain interrogation failed all ones

Post by manorin » Fri Dec 18, 2020 2:55 pm

I’ve been trying to program the ESP32-WROOM-32E and ESP-DevKitC-v4 (based on 32E) modules over JTAG (both on MacOS 10.15.4 and Windows 10) for the past two days and every single try has failed following the same error. It’s worth mentioning that I erased the flash memories of these modules entirely before any attempt to program them over JTAG. This eliminates the possibility that the JTAG pins might be reconfigured for other purposes by the existing firmware.

I’ve used both SEGGER JLink and ESP-Prog during my tests using the standard JTAG pins, i.e. TMS, TDO, TDI, TCK, GND and Vref. After running this command:

As stated in the ESP-IDF JTAG Debugging page, such an error is most probably referring to a problem in pin connections.
However, I have checked them multiple times and I have no clue where this error originates from. I have gone through similar issues, but none has really been helpful for my case.

An interesting thing is, when I hold the EN button on the DevKit and run the command above, the error changes from

This also happens when I ground the TDO.

I get the exact same behavior no matter which debugger, JLink or ESP-Prog, I use. I’d be grateful if anyone has any advice.

Re: Error: JTAG scan chain interrogation failed: all ones

Post by mikemoy » Fri Dec 18, 2020 6:49 pm

Re: Error: JTAG scan chain interrogation failed: all ones

Post by manorin » Fri Dec 18, 2020 7:15 pm

Thanks @mikemoy for your reply.

2×5 JTAG header pin number ——> ESP32 Module IO number
————————————————————————-
1 -> Module’s 3v3
2 -> IO 14
3 -> Module’s GND
4 -> IO 13
6 -> IO 15
8 -> IO 12

Re: Error: JTAG scan chain interrogation failed: all ones

Post by manorin » Mon Dec 21, 2020 8:29 am

I’ve realized that my case is the same as the one described in this post https://www.esp32.com/viewtopic.php?t=12600. The module is pre-programmed with the AT firmware which interferes with the JTAG pins.

Does this mean that we have no choice other than using a USB to serial programmer? Isn’t there a way to erase this stock firmware by JTAG?

Thank you for your help.

Re: Error: JTAG scan chain interrogation failed: all ones

Post by Timo Engelmann » Tue Jan 26, 2021 10:38 pm

I had the same problem with a ESP32 adapter board.

And this was the soultion for my problem.
Maybe it is helpful for other users.

Источник

I’ve been trying to program the ESP32-WROOM-32E and ESP-DevKitC-v4 (based on 32E) modules over JTAG (both on MacOS 10.15.4 and Windows 10) for the past two days and every single try has failed following the same error. It’s worth mentioning that I erased the flash memories of these modules entirely before any attempt to program them over JTAG. This eliminates the possibility that the JTAG pins might be reconfigured for other purposes by the existing firmware.

I’ve used both SEGGER JLink and ESP-Prog during my tests using the standard JTAG pins, i.e. TMS, TDO, TDI, TCK, GND and Vref. After running this command:

openocd -f board/esp32-wrover-kit-3.3v.cfg

I get:

Open On-Chip Debugger  v0.10.0-esp32-20201202 (2020-12-02-17:38)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : FreeRTOS creation
Info : FreeRTOS creation
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : J-Link V10 compiled Apr 23 2020 16:49:14
Info : Hardware version: 10.10
Info : VTarget = 3.339 V
Info : clock speed 1000 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: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Listening on port 3333 for gdb connections

As stated in the ESP-IDF JTAG Debugging page, such an error is most probably referring to a problem in pin connections.
However, I have checked them multiple times and I have no clue where this error originates from. I have gone through similar issues, but none has really been helpful for my case.

An interesting thing is, when I hold the EN button on the DevKit and run the command above, the error changes from

Error: JTAG scan chain interrogation failed: all ones

to

Error: JTAG scan chain interrogation failed: all zeros

This also happens when I ground the TDO.

I get the exact same behavior no matter which debugger, JLink or ESP-Prog, I use. I’d be grateful if anyone has any advice.

Thanks.

Hi,

I’ve set up Ubuntu 16.04LTS on a Windows Surface Pro (2017) I7-256GB-8GB tablet using Oracle Virtual Box. It appears that there is a problem with OpenOCD. Neil Kolban, helped me compare against his hardware, which is identical to mine. His setup works, mine doesn’t, despite the fact that we’re running the exact same code (esp-idf-template example). The output below gives the output from openocd when it is executed. Neil’s running Ubuntu 17 (not sure of sub version) on an i7 tower computer.

The device I’m trying to use JTag with is the Epressif ESP32-DevKit-WRover v3. For JTAG, I have only the TDO, TDI, TMS, and TCK pins jumpered. I also have the TXD and RXD for the UART jumpered. I’m using the epsressif example of esp-idf-templ. The only thing changed in the profile via menuconfig was the clock speed (240MHz instead of 160MHz) and the /dev/ttyUSB0 was changed to /dev/ttyUSB1.

`
gnorkus@gnorkus-VirtualBox:~$ dmesg | grep -i tty
[ 0.004000] console [tty0] enabled
[ 0.817177] 00:02: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200) is a 16550A
[ 22.224208] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 22.228595] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB1
gnorkus@gnorkus-VirtualBox:~$ cd esp
gnorkus@gnorkus-VirtualBox:~/esp$ cd openocd-esp32
gnorkus@gnorkus-VirtualBox:~/esp/openocd-esp32$ id
uid=1000(gnorkus) gid=1000(gnorkus) groups=1000(gnorkus),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare)
gnorkus@gnorkus-VirtualBox:~/esp/openocd-esp32$ ls -l /dev/ttyUSB*
crw-rw—- 1 root dialout 188, 0 Apr 4 19:02 /dev/ttyUSB0
crw-rw—- 1 root dialout 188, 1 Apr 4 19:02 /dev/ttyUSB1
gnorkus@gnorkus-VirtualBox:~/esp/openocd-esp32$ sudo bin/openocd -s share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp32-wrover.cfg
[sudo] password for gnorkus:
Open On-Chip Debugger 0.10.0-dev-g07baed8 (2018-02-23-08:56)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
esp32 interrupt mask on
force hard breakpoints
Info : ftdi: if you experience problems at higher adapter clocks, try the command «ftdi_tdo_sample_edge falling»
Info : clock speed 20000 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: esp32.cpu0: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : esp32: Debug controller was reset (pwrstat=0xFF, after clear 0xFF).
Info : esp32: Core was reset (pwrstat=0xFF, after clear 0xFF).
Error: cpu0: esp32_fetch_all_regs (line 165): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 165): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 165): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: cpu0: esp32_fetch_all_regs (line 192): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: esp32_fetch_all_regs (line 192): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: esp32_fetch_all_regs (line 192): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Error: Exception reading pc!

Info : active_cpu: 0, changed to 1, reson = 0xffffffff
Info : Target halted. PRO_CPU: PC=0x00000000 APP_CPU: PC=0x00000000 (active)
Error: cpu0: xtensa_write_memory (line 698): DSR (FFFFFFFF) indicates target still busy!
Error: cpu0: xtensa_write_memory (line 698): DSR (FFFFFFFF) indicates DIR instruction generated an exception!
Error: cpu0: xtensa_write_memory (line 698): DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
Warn : esp32: Failed writing 4 bytes at address 0x3FF5F064, data — a1, 3a, d8, 50, a1, 3a, d8, 50
embedded:startup.tcl:21: Error:
in procedure ‘init’
in procedure ‘ocd_bouncer’
in procedure ‘esp_smp_break_config’
in procedure ‘esp32’ called at file «share/openocd/scripts/target/esp32.cfg», line 54
in procedure ‘ocd_bouncer’
in procedure ‘esp_core_halt’
in procedure ‘esp32’ called at file «share/openocd/scripts/target/esp32.cfg», line 44
in procedure ‘ocd_bouncer’
at file «embedded:startup.tcl», line 21

cpu0: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
cpu1: Current bits set: BreakIn BreakOut RunStallIn DebugModeOut
`

I am trying to install openWRT on a router using my Raspberry Pi Zero. I am following the exact steps as explained in http://www.alfredklomp.com/technology/experia-v8/
However, for some reason I keep getting the following errors:

Warn : gpio 11 is already exported
Warn : gpio 25 is already exported

Error: JTAG scan chain interrogation failed: all zeroes

Full output:

    Open On-Chip Debugger 0.10.0+dev-01242-g11c5efd2-dirty (2020-05-15-17:51)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
DEPRECATED! use 'adapter srst delay' not 'adapter_nsrst_delay'
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
force hard breakpoints
flash_file
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : SysfsGPIO JTAG/SWD bitbang driver
Info : JTAG and SWD modes enabled
Warn : gpio 11 is already exported
Warn : gpio 25 is already exported
Info : This adapter doesn't support configurable speed
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: vrx200.cpu0: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : starting gdb server for vrx200.cpu1 on 3333
Info : Listening on port 3333 for gdb connections

Does anyone know what is going wrong? I have been searching for ages, but this is my first time doing this and I am not finding anything useful.
Thanks for taking the time to look at my issue! I really appreciate it

I am thinking the connections might be incorrect, but I am doing the exact same as described by him and I used both his schematics plus the image to match his wire placing.

I tried posting this on the OpenOCD forum but received no responses. I probably should have posted it here first.

I’m attempting to communicate with an Olimex STM32-H103 with an Olimex ARM-USB-TINY.

I’m powering the H103 via USB and I’m using OpenOCD version 0.4.0 (2010-06-18-22:40) that I downloaded and compiled. I use this setup for another project, also an STM32 project, without any problems.

I placed all my OpenOCD configurations in a file called stm32.cfg (see below) to simplify debugging. I compiled this configuration file from a number of sources and believe it is correct. In fact using the same programmer and configuration file with the Leaf Maple I have no problems. However whenever I attempt to communicate with the H103 I receive the following error:

$ sudo openocd -d0 -f target/stm32.cfg
Open On-Chip Debugger 0.4.0 (2010-06-18-22:40)
Licensed under GNU GPL v2
For bug reports, read
   http://openocd.berlios.de/doc/doxygen/bugs.html
debug_level: 0
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
1000 kHz
jtag_nsrst_delay: 100
jtag_ntrst_delay: 100
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.

At this point the daemon does run and as such I can connect to it via telnet. However as you can see it acts as though there is no target. Has anyone encountered this problem? Or can anyone help me resolve it?

TIA,
Dustin

#daemon configuration
telnet_port 4444
gdb_port 3333

interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG TINY"
ft2232_layout olimex-jtag
ft2232_vid_pid 0x15ba 0x0004

#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst

# script for stm32
if { [info exists CHIPNAME] } {
   set  _CHIPNAME $CHIPNAME
} else {
   set  _CHIPNAME stm32
}

if { [info exists ENDIAN] } {
   set  _ENDIAN $ENDIAN
} else {
   set  _ENDIAN little
}

# Work-area is a space in RAM used for flash programming
# By default use 16kB
if { [info exists WORKAREASIZE] } {
   set  _WORKAREASIZE $WORKAREASIZE
} else {
   set  _WORKAREASIZE 0x4000
}

# JTAG speed should be <= F_CPU/6. F_CPU after reset is 8MHz, so use F_JTAG = 1MHz
jtag_khz 1000

jtag_nsrst_delay 100
jtag_ntrst_delay 100

#jtag scan chain
if { [info exists CPUTAPID ] } {
   set _CPUTAPID $CPUTAPID
} else {
  # See STM Document RM0008
  # Section 26.6.3
   set _CPUTAPID 0x3ba00477
}
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID

if { [info exists BSTAPID ] } {
   # FIXME this never gets used to override defaults...
   set _BSTAPID $BSTAPID
} else {
  # See STM Document RM0008
  # Section 29.6.2
  # Low density devices, Rev A
  set _BSTAPID1 0x06412041
  # Medium density devices, Rev A
  set _BSTAPID2 0x06410041
  # Medium density devices, Rev B and Rev Z
  set _BSTAPID3 0x16410041
  # High density devices, Rev A
  set _BSTAPID4 0x06414041
  # Connectivity line devices, Rev A and Rev Z
  set _BSTAPID5 0x06418041
}
jtag newtap $_CHIPNAME bs -irlen 5 -ircapture 0x1 -irmask 0x1 -expected-id $_BSTAPID1 
   -expected-id $_BSTAPID2 -expected-id $_BSTAPID3 
   -expected-id $_BSTAPID4 -expected-id $_BSTAPID5

set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME cortex_m3 -endian $_ENDIAN -chain-position $_TARGETNAME

$_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x20000000 -work-area-size $_WORKAREASIZE -work-area-backup 0

set _FLASHNAME $_CHIPNAME.flash
#flash bank $_FLASHNAME stm32x 0 0 0 0 $_TARGETNAME
flash bank $_FLASHNAME stm32x 0x08000000 0x00010000 0 0 $_TARGETNAME

# For more information about the configuration files, take a look at:
# openocd.texi

Last edited by DaemonMaker on Fri Oct 15, 2010 10:49 pm, edited 1 time in total.

Dear all,

I try to follow (https://github.com/dwelch67/raspberrypi … er/armjtag) to use Olimex-usb-ocd for debugging raspberry pi. But even during the hardware connection, I meet lots of problems.

./openocd -f /home/painting/software/openocd-0.7.0/install/share/openocd/scripts/interface/olimex.cfg -f /home/painting/software/openocd-0.7.0/install/share/openocd/scripts/target/raspi.cfg
Open On-Chip Debugger 0.7.0 (2013-11-27-08:05)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 1000 kHz
none separate
raspi.arm
Info : clock speed 1000 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: raspi.arm: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: 'arm11 target' JTAG error SCREG OUT 0x1f
Error: unexpected ARM11 ID code
Polling target raspi.arm failed, GDB will be halted. Polling again in 100ms
Polling target raspi.arm failed, GDB will be halted. Polling again in 300ms
Polling target raspi.arm failed, GDB will be halted. Polling again in 700ms
Polling target raspi.arm failed, GDB will be halted. Polling again in 1500ms

I check again the connection between P1 of raspberry and olimex-arm-usb-ocd as follows,
—————————————
JTAG | raspberry
—————————————
1 | P1-1
—————————————
5 | P1-7
—————————————
7 | P1-13
—————————————
3 | P1-15
—————————————
9 | P1-22
—————————————
13 | P1-18
—————————————
4 | P1-25
—————————————
<raspi.cfg>:

# Broadcom 2835 on Raspberry Pi

telnet_port 4444
#gdb_port 0
#tcl_port 0

#jtag_khz 1000
adapter_khz 1000

#jtag_nsrst_delay 400
#jtag_ntrst_delay 400

if { [info exists CHIPNAME] } {
   set  _CHIPNAME $CHIPNAME
} else {
   set  _CHIPNAME raspi
}

reset_config none

if { [info exists CPU_TAPID ] } {
   set _CPU_TAPID $CPU_TAPID
} else {
   set _CPU_TAPID 0x07b7617F
}
jtag newtap $_CHIPNAME arm -irlen 5 -expected-id $_CPU_TAPID

set _TARGETNAME $_CHIPNAME.arm
target create $_TARGETNAME arm11 -chain-position $_TARGETNAME

<olimex.cfg>:

#interface configuration############################################################
# Olimex ARM-USB-OCD-H
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG"
ft2232_layout olimex-jtag
#ft2232_vid_pid 0x15ba 0x002b
ft2232_vid_pid 0x15ba 0x0003