search

SpinalHDL / openocd_riscv

Spen's Official OpenOCD Mirror
Other
45 stars 33 forks source link

openocd error #14

Open ombhilare999 opened 3 years ago

ombhilare999 commented 3 years ago

I was trying this: https://github.com/SpinalHDL/VexRiscv#interactive-debug-of-the-simulated-cpu-via-gdb-openocd-and-verilator But got the following error, I tried Some way to solve it but it didn't work. Kindly help here.

This is the log I got:

  src/openocd -c "set VEXRISCV_YAML PATH_TO_THE_GENERATED_CPU0_YAML_FILE" -f tcl/target/vexriscv_sim.cfg
  Open On-Chip Debugger 0.10.0+dev-01231-gf8c1c8a-dirty (2021-03-28-01:05)
  Licensed under GNU GPL v2
  For bug reports, read
      http://openocd.org/doc/doxygen/bugs.html
  PATH_TO_THE_GENERATED_CPU0_YAML_FILE
  DEPRECATED! use 'adapter driver' not 'interface'
  Error: The specified debug interface was not found (dummy)
  The following debug adapters are available:
  1: jtag_tcp
  2: ftdi
  3: usb_blaster
  4: ft232r
  5: jlink
  6: vsllink
  7: ulink
  8: hla
  9: osbdm
  10: opendous
  11: aice
  12: xds110
  13: st-link

image

Dolu1990 commented 3 years ago

Hi,

PATH_TO_THE_GENERATED_CPU0_YAML_FILE is intended to be a file path ^^ The generation of VexRiscv create a cpu0.yaml file.This has to be pointed.

ombhilare999 commented 3 years ago

Huh My bad I didn't see that I need to put the path command. Just copy pasted directly, Will correct it.

Dolu1990 commented 3 years ago

<3

ombhilare999 commented 3 years ago

I have added a path in the command but still it gives same error.

omkar@omkar:~/VJTI/openocd_riscv$ src/openocd -c "set VEXRISCV_YAML /home/omkar/VJTI/VexRiscv/cpu0.yaml" -f tcl/target/vexriscv_sim.cfg
Open On-Chip Debugger 0.10.0+dev-01231-gf8c1c8a-dirty (2021-03-28-01:05)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
/home/omkar/VJTI/VexRiscv/cpu0.yaml
DEPRECATED! use 'adapter driver' not 'interface'
Error: The specified debug interface was not found (dummy)
The following debug adapters are available:
1: jtag_tcp
2: ftdi
3: usb_blaster
4: ft232r
5: jlink
6: vsllink
7: ulink
8: hla
9: osbdm
10: opendous
11: aice
12: xds110
13: st-link
Dolu1990 commented 3 years ago

While compiling, did you removed the dummy interface ? (./configure --enable-ftdi --enable-dummy)

sreenivasa-0623 commented 3 years ago

But I am still not able to do anything after I have added the path and done the building in the same way mentioned This was done and the error given is shown below prabath@prabath-VirtualBox:~/esp/openocd-esp32$ src/openocd -c "set VEXRISCV_YAML /home/verilator/Vexriscv/cpu0.yaml" -f tcl/target/vexriscv_sim.cfg Open On-Chip Debugger v0.10.0-esp32-20210401-48-g041b08f6 (2021-06-24-22:33) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html /home/verilator/Vexriscv/cpu0.yaml Info : only one transport option; autoselect 'jtag' tcl/target/vexriscv_sim.cfg:20: Error: Unknown target type vexriscv, try one of arm7tdmi, arm9tdmi, arm920t, arm720t, arm966e, arm946e, arm926ejs, fa526, feroceon, dragonite, xscale, cortex_m, cortex_a, cortex_r4, arm11, ls1_sap, mips_m4k, avr, dsp563xx, dsp5680xx, testee, avr32_ap7k, hla_target, nds32_v2, nds32_v3, nds32_v3m, esp32, esp32s2, esp32s3, esp32c3, or1k, quark_x10xx, quark_d20xx, stm8, riscv, mem_ap, esirisc, or aarch64 in procedure 'script' at file "embedded:startup.tcl", line 26 at file "tcl/target/vexriscv_sim.cfg", line 20 WHAT SHOULD BE DONE???????

Dolu1990 commented 3 years ago

Did you :

git clone https://github.com/SpinalHDL/openocd_riscv.git cd openocd_riscv ./bootstrap ./configure --enable-ftdi --enable-dummy make -j$(nproc)

?

sreenivasa-0623 commented 3 years ago

Yes but I will try again

sreenivasa-0623 commented 3 years ago

Now I am getting this wht should I do prabath@prabath-VirtualBox:~/openocd_riscv$ src/openocd -c "set VEXRISCV_YAML /home/verilator/Vexriscv/cpu0.yaml" -f tcl/target/vexriscv_sim.cfg Open On-Chip Debugger 0.10.0+dev-01236-gc974c1b7-dirty (2021-06-25-19:56) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html /home/verilator/Vexriscv/cpu0.yaml DEPRECATED! use 'adapter driver' not 'interface' Info : only one transport option; autoselect 'jtag' DEPRECATED! use 'adapter speed' not 'adapter_khz' DEPRECATED! use 'adapter srst delay' not 'adapter_nsrst_delay' Info : set servers polling period to 50ms Error: cpuConfigFile /home/verilator/Vexriscv/cpu0.yaml not found Error: target 'fpga_spinal.cpu0' init failed

sreenivasa-0623 commented 3 years ago

The yaml file is there in the mentioned location only

sreenivasa-0623 commented 3 years ago

Hi Sir in reply to the previous one what should be done in order to proceed to next step: Now I am getting this wht should I do prabath@prabath-VirtualBox:~/openocd_riscv$ src/openocd -c "set VEXRISCV_YAML /home/verilator/Vexriscv/cpu0.yaml" -f tcl/target/vexriscv_sim.cfg Open On-Chip Debugger 0.10.0+dev-01236-gc974c1b7-dirty (2021-06-25-19:56) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html /home/verilator/Vexriscv/cpu0.yaml DEPRECATED! use 'adapter driver' not 'interface' Info : only one transport option; autoselect 'jtag' DEPRECATED! use 'adapter speed' not 'adapter_khz' DEPRECATED! use 'adapter srst delay' not 'adapter_nsrst_delay' Info : set servers polling period to 50ms Error: cpuConfigFile /home/verilator/Vexriscv/cpu0.yaml not found Error: target 'fpga_spinal.cpu0' init failed

Dolu1990 commented 3 years ago

Very weird, And ls /home/verilator/Vexriscv/cpu0.yaml is happy ?