Yaml file not found even existed

[sreenivasa-0623]

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

What to do even if the yaml file exists in the given location

[Dolu1990]

Very weird,

What give
ls /home/verilator/Vexriscv/cpu0.yaml
?

[sreenivasa-0623]

The cpu0 file was there in the mentioned loc but I am getting an error that indicates that it is not there

…

On Mon, Jun 28, 2021, 18:06 Dolu1990 ***@***.***> wrote: Very weird, What give ls /home/verilator/Vexriscv/cpu0.yaml ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AT2COTG2Z77HLGY6GRYNN43TVBUERANCNFSM47LQGWIQ> .

[Dolu1990]

So basicay, there is where things goes wrong :
https://github.com/SpinalHDL/openocd_riscv/blob/riscv_spinal/src/target/vexriscv.c#L507

I can't reproduce the issue myself.

[sreenivasa-0623]

So what to do should I quote those lines?

…

On Tue, Jun 29, 2021, 13:18 Dolu1990 ***@***.***> wrote: So basicay, there is where things goes wrong : https://github.com/SpinalHDL/openocd_riscv/blob/riscv_spinal/src/target/vexriscv.c#L507 I can't reproduce the issue myself. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AT2COTCYZU6INTYSULDSBQDTVF3DZANCNFSM47LQGWIQ> .

[Dolu1990]

Shouldn't quote them, but that's a starting point to start debug

[sreenivasa-0623]

I am sorry I didn't get it can u pls explain in detail

…

On Tue, Jun 29, 2021, 17:58 Dolu1990 ***@***.***> wrote: Shouldn't quote them, but that's a starting point to start debug — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AT2COTHZ5IXFTAUU24BDJWDTVG373ANCNFSM47LQGWIQ> .

[Dolu1990]

That fopen fail on your environnement, which is realy weird.
You may try to hardcode some path there, to see if you can read a file.

[sreenivasa-0623]

Ok but I don't know how to do it and can u pls help me how to do that

…

On Tue, Jun 29, 2021, 20:30 Dolu1990 ***@***.***> wrote: That fopen fail on your environnement, which is realy weird. You may try to hardcode some path there, to see if you can read a file. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AT2COTGCND67HNIOFS6SMI3TVHN2XANCNFSM47LQGWIQ> .

[Dolu1990]

You can try to tweek the source code i pointer, to try understanding what is happing, prinf is your friend ^^