Vitis debugger doesn't find microblaze v core

Support
1

I am trying to instantiate a microblaze V core to test some IP we are working on. After building the platform and application in vitis, when I try to launch the debugger, I get an error message:“No targets found with name = Hart*”. In the console, I can connect. The target list includes the ARM9s and the microblaze debug core, but no microblaze processor. All I want to do is be able to instantiate a simple soft core which will be run from a debugger. This is the latest vivado release 2024.1 with a pynq Z2 board. At this time, I also have no need for the web interface - am I forced to use it?

2

Hi @Ian_Board,

Welcome to the PYNQ community.

You may better off asking this question in the Xilinx forums.

Mario

3

@Ian_Board were you able to find a solution?

I stumbled upon this issue me too on the Pynq Z2 when I choose a simple RV32IMC Microblaze-V configuration. I thought maybe the RTL is buggy or something, so I switched to RV32IMAFC, and then Vitis started seeing the core and was able to upload my SW app (you just need to untick the PS7 init and post-init check marks in the launch parameters. Once the app is uploaded, I see the output in my UART console. However, the core just loops indefinitely and starts execution from the beginning (even an infinite while loop doesn’t hold execution, the CPU restarts from the beginning). Debugging on it is impossible, for some reason the debugger doesn’t attach. And even when I use my custom xsdb TCL script with GDB, I’m not able to halt the processor.
I had no problems on my Arty A7 100T though. I was able to upload, run and debug apps using both Vitis IDE and custom xsdb scripts w/ GDB.