07-04-2016 12:20 AM
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...
07-04-2016 12:38 AM
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"
07-04-2016 02:34 AM
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
07-04-2016 04:26 AM
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?
07-26-2016 02:05 AM
11-15-2016 11:37 AM
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.
06-15-2017 02:15 PM
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....
08-18-2017 12:47 PM
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?