Microblaze step-over debugging stops at interrupt vector

[a_j_n]

Hi,

I'm experiencing a problem with debugging my (dual) Microblaze design. When I step trough my code (step-over), it always breaks at the interrupt vector (in my case 0x00000010). This is the (recurring) timer interrupt of the xil_kernel.

I only have the problem with the step-over command. The step-into and run (to next breakpoint) give no problems.

Any help on how to avoid this, because it makes debugging very difficult...

[a_j_n]

I'm using SDK 2016.2 with the Xilinx System debugger. The GDB debugger gives an error: "GDB launch is not supported for devices from 8 series device family onwards"

[goran]

Hi,

Use System Debugger instead since GDB is not supported for 8 series.

Göran

[a_j_n]

The problem appears with the System Debugger. So there is no alternative anymore...

[goran]

Hi,

In SDK, do you "launch with System Debugger" or "launch with GDB"?

If you launch with System Debugger and get the GDB error, it seems like a bug

Göran

[a_j_n]

My problem described in the first post. The second post was only to give more information about which debugger I am using.

[pumpkin]

I also ran into the same problem with 2015.4 and system debugger. It is too annoying to step a line of code.

Who can give me a solution?

best regards

Xiang Chao

[pumpkin]

I ran into the same problem. It is too annoying to step the source code.

regards

Xiang Chao

[pumpkin]

I also ran into this problem. Its really annoying to step my code.

Could anybody give any suggestion?

regards

Xiang Chao

[a_j_n]

Is there anyone who has suggestions or work-around for this problem? It makes debugging impossible with SDK 2016.2!!

[sadanan]

Hi,

The problem seems to be due to MDM completion control. Can you check with the attached patch? You need to extract it to $XILINX_SDK, where XILINX_SDK points to your SDK installation (ex. C:\Xilinx\SDK\2016.2)

[Anonymous]

Is there a patch for 2016.3?  I believe we may be experiencing this bug on a Kintex Ultrascale.

[andrew57jm]

Is there a patch for any other versions? A plan for one? This bug is also in 2015.2 and it makes debugging extremely difficult.

[goran]

Hi,

There are two things fixed from Xilinx.

- The MicroBlaze issue is fixed in 2016.3. That should solve the problem the first time you run hw_server.

- The hw_server issue fix will be in 2016.4. Workaround is to restart hw_server every time you relaunch debug.

Göran

[npalmer]

I am seeing this issue (as described in the original post) in XSDK 2016.3.  Was this actually fixed or is there a patch for 2016.3?  johnbartek above also seems to be having the issue in 2016.3.  I have tried restarting hw_server and it does not make a difference.

The single step is useless with this bug....

[legendbb]

I have the same issue in 2017.1. Tried patch for 2016.2, stuck at Auto Connect forever.

Any patch for 2017.*?

Thanks,

[superdude]

We're having the same issue here with 2017.1 and Ultrascale.  If GDB can't be enabled, is there a config option or something which we can set for the System Debugger to allow single-stepping?