Help in Debugging the Cortex-M4 core on the Vybrid SoC with OpenOCD

Technical Support
, , , ,
1

Hi

I had followed the steps mentioned in “Antmicro · Debugging the Cortex-M4 core on the Vybrid SoC with OpenOCD” inorder to debug the Cortex-M4 core on the Vybrid SoC with OpenOCD. But after starting the cortex m4 core on u-boot, and typing the command “openocd -f /usr/share/openocd/scripts/interface/olimex-arm-usb-tiny-h.cfg -f /usr/share/openocd/scripts/target/vybrid_vf61_m4.cfg” on linux, I got the following error. Can anyone help me to find the solution? The error log file is given below:

link text

madhav@madhav-HP-15-Notebook-PC:/$ cd usr/share/openocd                                
madhav@madhav-HP-15-Notebook-PC:/usr/share/openocd$ openocd -f /usr/share/openocd/scripts/interface/ftdi/olimex-arm-usb-tiny-h.cfg -f /usr/share/openocd/scripts/target/vybrid_vf61_m4.cfg     
Open On-Chip Debugger 0.9.0 (2018-03-06-12:48)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select '.
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
Info : clock speed 1000 kHz
Info : JTAG tap: vf61.cpu0 tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine

Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
zError: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
xInfo : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
Error: vf61.cpu0 -- clearing lockup after double fault
Polling target vf61.cpu0 failed, trying to reexamine
Info : vf61.cpu0: hardware has 127 breakpoints, 15 watchpoints
^Z
[1]+  Stopped                 openocd -f /usr/share/openocd/scripts/interface/ftdi/olimex-arm-usb-tiny-h.cfg -f /usr/share/openocd/scripts/target/vybrid_vf61_m4.cfg
2

hi sreemadhav

which hardware (with carrier board) and software versions are u using? What is exactly the problem?

3

hi @jaski.tx

I’m using Colibri vf61 V1.2A with linux image V2.6(with Colibri Evaluation Board Rev 3.2). The exact problem is shown above. On linux when typing the command “openocd -f /usr/share/openocd/scripts/interface/olimex-arm-usb-tiny-h.cfg -f /usr/share/openocd/scripts/target/vybrid_vf61_m4.cfg” to link jtag with m4core it shows the error as given below.

link text

4

which jtag hardware are you using? which software is running on the m4 core?

5

Are you trying to connect while A-core is still in uboot?