Showing results for 
Show  only  | Search instead for 
Did you mean: 
Registered: ‎04-23-2020

Not able to debug multiprocessors design using Vitis (microblaze)


I have a weird problem where I cannot debug multiple microblaze processor on my Basys3 board (using a Artix7). I put this in Vitis but I also had the same problem while using Vivado 2017 with the SDK tool. I switch to the newest version in hope that would solve the issue but it did not. I do though prefer Vitis interface :).

Here is some context:

1. My Vivado design is like this: I have my top level in SystemVerilog that instanciates my 3 block design + my clock wizard to split my input clock for my 2 microblaze. My SV is attached.


2. My 2 MicroBlaze are identical

  • UART
  • GPIO with 2 channel (1 input channel 1, 1 output channel 2)


3. I created a separate block design for the Microblaze Debug Module (MDM) in order to connect my 2 microblaze together.


4. That's so far goes well and the entire project go through Synthesis, implementation and bitstreams.

Now the root problem. Once I get into Vitis,

1. I first create my Plateform project and include my 2 domains for my 2 microblaze.

2. Then I create an Application Project and System and I add my 2 microprocessor project


3. Then, I followed the steps for multiprocessor debug with this link:


4. My resulting debugging configuration looks like this:





5. Once I launch the debug, it gives my this error:



If I debug them alone it works fine but as soon as I put both, I get this error.


I did a lot of trials and searches on the net but now I'm out of ideas.


Is anybody was able to have a similar design to work?

Thank you very much in advance for the help!


Important note though, I created a new project where I put my 2 processors in the same block design with the MDM also in the same block design. By doing it like that, it was working fine. It seems it is an issue with multiple processor on different design blocks while connecting them with a MDM external to their block design.




0 Kudos
0 Replies