(solved) Did you manage to debug a Microblaze RISC-V with Vitis Unified IDE (2024.1) ?

I've made a Vivado 2024.1 design with a Microblaze RISC-V. With debug functionality. I have done similar activities in the past, With Vivado 2022.1.
I exported the hardware design, started a Vitis project, and created a simple microblaze Hello application.

Vitis knows the Microblaze is there. The application builds in Vitis without issues. I also can load the bitstream file to the FPGA, over JTAG.

But when I want to program the MicroBlaze, or debug it, the debugger doesn't find the core. It finds the two ARM cores inside the Zinq, but not the MB I designed in fabric.

I have this working in Viado / Vitis 2022.1, where they aren't using the Unified IDE yet.

Vitis can load the bitfile without issues, over JTAG:

But when starting the programmer or debugger, it doesn't find the MicroBlaze in the JTAG chain.

Error:

no targets found with "name =~ "Hart*"". available targets: 1* APU 2 ARM Cortex-A9 MPCore #0 (Running) 3 ARM Cortex-A9 MPCore #1 (Running) 4 xc7z020

I found same errors on google, but no solutions that worked ...

Top Replies

bidrohini 1 month ago

The debug functionality for MicroBlaze should be correctly set up in your Vivado block design. Verify that the MicroBlaze core has the necessary debug configuration enabled (like JTAG interface) in the hardware design.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
Jan Cumps 1 month ago

I was able to get it working:

What did I do different:

Initially, I loaded the bitfile to the FPGA via Vitis menu Vitis -> Program device. And then, when debugging, I got the behaviour as described in my original post.

I have now changed the debug setup (click on the cog wheel next to the debug command), and added loading of the bit file to the launch setup:

That did the trick. I don't know yet if this is a workaround because something in my VHDL design is missing (did I implement the reset logic wrong?). Or if this is how it's supposed to be done.

Anyways, I'm ready for debugging the MicroBlaze
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
Jan Cumps 1 month ago in reply to bidrohini

Thank you. It had the setup - but uncertain if I did all correctly.
See comment : how I got it working).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Jan Cumps 1 month ago

turns out that I don't have to load the bitfile, when the FPGA is already programmed. With the settings below, I can program and debug the microblaze, without reloading the bit file or resetting the ARM processor.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Jan Cumps 1 month ago

Debug example:

I'm toggling Y11 (arduino A0).

Debugger in action:

And the is driven high when executing this command:

XGpio_DiscreteWrite(&Gpio, LED_CHANNEL, LED);

And when connected to the LED array instead of the Arduino A0-A5:
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel