- Tue Oct 07, 2014 2:58 am
#175647
Hi Guys,
I'm trying to use openOCD to debug a custom board(NavStik, see http://navstik.org/home/), implementing:
FTDI FT4232H
STM32F407
I've built the newest libusb (with --enable-ftdi) and run ubuntu 14.04(64 bits).
This is the command I give:
sudo openocd -f ~/Downloads/openocd.8.0/tcl/interface/ftdi/openocd-usb-hs.cfg
-f ~/Downloads/openocd-0.8.0/tcl/target/stm32f4x.cfg
I have modified openocd-usb-hs.cfg as follows:
gdb_port 3333
#tcl_port 6666
telnet_port 4444
interface ftdi
#ftdi_device_desc "Dual RS232-HS"
ftdi_vid_pid 0x0403 0x6011
debug_level 2
And this is the response:
debug_level: 2
adapter speed: 3000 kHz
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
Warn : target name is deprecated use: 'cortex_m'
Info : clock speed 3000 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: stm32f4xxx.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : Invalid ACK 0x7 in JTAG-DP transaction
When increasing the debug level to 3, I get (prior to the first error):
Debug: 177 410 command.c:145 script_debug(): command - ocd_jtag ocd_jtag arp_init
Debug: 178 410 core.c:1417 jtag_init_inner(): Init JTAG chain
Debug: 179 410 core.c:323 jtag_call_event_callbacks(): jtag event: TAP reset
Debug: 180 410 core.c:1048 jtag_examine_chain(): DR scan interrogation for IDCODE/BYPASS
Debug: 181 410 core.c:323 jtag_call_event_callbacks(): jtag event: TAP reset
Error: 182 411 core.c:941 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones
I've tried the following:
- using openOCD-0.7.0, which gives me the same, only it keeps trying to poll the CPU.
- adapter speeds 3000KHz and 2000KHz and jtag and adapter delays of 100.
- do a reset in the configure script but to no avail.
(Is there anything else you recommend trying?)
When searching 'the internet', this error seems to indicate a physical problem.
(I'm not sure how much it matters, but is the fact that this chip has 4 COM-ports any complication in this?)
I've already contacted the manufacturer, but before giving up on this board I would like to ask you guys:
Does there happen to be a (known)bug or something in the configuration, openOCD, or should I just assume my hardware is broken(I have no way to really test it here..)?
I'm hoping to hear from you, thanks in advance.
153rd
I'm trying to use openOCD to debug a custom board(NavStik, see http://navstik.org/home/), implementing:
FTDI FT4232H
STM32F407
I've built the newest libusb (with --enable-ftdi) and run ubuntu 14.04(64 bits).
This is the command I give:
sudo openocd -f ~/Downloads/openocd.8.0/tcl/interface/ftdi/openocd-usb-hs.cfg
-f ~/Downloads/openocd-0.8.0/tcl/target/stm32f4x.cfg
I have modified openocd-usb-hs.cfg as follows:
gdb_port 3333
#tcl_port 6666
telnet_port 4444
interface ftdi
#ftdi_device_desc "Dual RS232-HS"
ftdi_vid_pid 0x0403 0x6011
debug_level 2
And this is the response:
debug_level: 2
adapter speed: 3000 kHz
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
Warn : target name is deprecated use: 'cortex_m'
Info : clock speed 3000 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: stm32f4xxx.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : Invalid ACK 0x7 in JTAG-DP transaction
When increasing the debug level to 3, I get (prior to the first error):
Debug: 177 410 command.c:145 script_debug(): command - ocd_jtag ocd_jtag arp_init
Debug: 178 410 core.c:1417 jtag_init_inner(): Init JTAG chain
Debug: 179 410 core.c:323 jtag_call_event_callbacks(): jtag event: TAP reset
Debug: 180 410 core.c:1048 jtag_examine_chain(): DR scan interrogation for IDCODE/BYPASS
Debug: 181 410 core.c:323 jtag_call_event_callbacks(): jtag event: TAP reset
Error: 182 411 core.c:941 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones
I've tried the following:
- using openOCD-0.7.0, which gives me the same, only it keeps trying to poll the CPU.
- adapter speeds 3000KHz and 2000KHz and jtag and adapter delays of 100.
- do a reset in the configure script but to no avail.
(Is there anything else you recommend trying?)
When searching 'the internet', this error seems to indicate a physical problem.
(I'm not sure how much it matters, but is the fact that this chip has 4 COM-ports any complication in this?)
I've already contacted the manufacturer, but before giving up on this board I would like to ask you guys:
Does there happen to be a (known)bug or something in the configuration, openOCD, or should I just assume my hardware is broken(I have no way to really test it here..)?
I'm hoping to hear from you, thanks in advance.
153rd