debugger for pulpino

[ravi kumar]

what is best debugger for pulpino core?

can i use segger for puplino?

[Tommy Murphy]

I thought that the only way to debug Pulpino was via the debug_vpi debug bridge:

https://github.com/pulp-platform/pulpino

Interactive debug
To interactively debug software via gdb, you need the jtag bridge as well as a working version of gdb for the ISA you want to debug. The debug bridge depends on the jtag_dpi package that emulates a JTAG port and provides a TCP socket to which the jtag bridge can connect to.

https://github.com/pulp-platform/debug_bridge/blob/master/README.md

I'm not sure that you can use J-Link or any other JTAG probe for debugging but I may be wrong.

Maybe ask the Pulpino project people?

[Tommy Murphy]

>  via the debug_vpi debug bridge:

Typo - I meant jtag_dpi not debug_vpi! :-) 

[Ken Pettit]

Hey Guys,

At company, IQ-Analog, I hired a SW contract house (actually the one I used to work for) to get OpenOCD with J-Link debugger working.  They have this up and running flawlessly at this point, though I don't have the code yet (they are also working on a NuttX port for me).

I can ask them to make this OpenOCD port available if anyone is interested.

Ken

--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+un...@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/ddfa84dc-5c84-4a88-b32e-32efe8a3bbf1%40groups.riscv.org.

[Tommy Murphy]

On Monday, 24 September 2018 12:21:58 UTC+1, Kenneth Pettit wrote:

Hey Guys,

At company, IQ-Analog, I hired a SW contract house (actually the one I used to work for) to get OpenOCD with J-Link debugger working.  They have this up and running flawlessly at this point, though I don't have the code yet (they are also working on a NuttX port for me).

I can ask them to make this OpenOCD port available if anyone is interested.

I don't understand.

OpenOCD already has support for J-Link via the libjaylink library.

And the JTAG probe/interface has nothing to do with the specific CPU/SoC target (e.g. Cortex-M, RISC-V).

What exactly has been added here that is not in the base openocd project?

Thanks

Tommy

[Ken Pettit]

Sorry for being too vague,

Support for RISC-V debug via the Pulpino's Advanced Debug Interface as borrowed from the OpenRISC / OpenCores project.  You are correct, the JTAG probe has nothing to do with the target, just wanted to identify that this is JTAG debugging vs. SPI debugging.  As far as I know, the Pulpino debug_bridge has only SPI debugging on a real device or JTAG in simulation land.

Ken

--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+un...@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.

To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/768f573a-1643-4303-9b29-76c288fe5115%40groups.riscv.org.