cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
6,458 Views
Registered: ‎11-11-2011

SDK debugger launch and execute problem in 14.2 and 14.5

Jump to solution

Hi,

    I'm trying to debug Microblaze code inside a K7 fpga. The custom board has 3 xilinx devices on it -

clpa, spartan6 and K7. I'm only using K7. I have problems running the debugger in SDK. Once I started 

"step over", it lost the program counter immediately or after a couple of steps. And the fpga wishbone bus

would report lost of PCIe link. 

 

Anyone has some idea why this is so?  I've been fighting with this issue for a while. Any help is highly appreciated.

Thanks in advance. 

 

My steps are as follows:

1. program K7 using Impact.  The logic and embedded microblaze works as proved by

    some toggling gpio bits controlled by the Microblaze software. 

2. Start SDK. Connect to the MDM in XMD console by command below (note, if I don't specify 

    this way, the MDM would not be found by the SDK debugger):

 

       XMD%  connect mb mdm -debugdevice devicenr 3 cpunr 1

 

3. Launch Debugger on hardware. I tried in the debug config to enable or disable  "load to the memory".

    Both config settings gave same results. The XMD console messages for connecting MDM and after 

    launching SDK debugger:

 

  1. XMD% connect mb mdm -debugdevice devicenr 3 cpunr 1
  2. JTAG chain configuration
  3. --------------------------------------------------
  4. Device ID Code IR Length Part Name
  5. 1 06e5e093 8 XC2C64A
  6. 2 2402e093 6 XC6SLX75T
  7. 3 43651093 6 XC7K325T
  8. MicroBlaze Processor Configuration :
  9. -------------------------------------
  10. Version............................8.40.a
  11. Optimization.......................Performance
  12. Interconnect.......................AXI-LE
  13. MMU Type...........................No_MMU
  14. No of PC Breakpoints...............1
  15. No of Read Addr/Data Watchpoints...0
  16. No of Write Addr/Data Watchpoints..0
  17. Instruction Cache Support..........off
  18. Data Cache Support.................off
  19. Exceptions Support................off
  20. FPU Support.......................on
  21. Hard Divider Support...............on
  22. Hard Multiplier Support............on - (Mul64)
  23. Barrel Shifter Support.............on
  24. MSR clr/set Instruction Support....on
  25. Compare Instruction Support........on
  26. Data Cache Write-back Support......off
  27. Fault Tolerance Support............off
  28. Stack Protection Support...........off
  29. Connected to "mb" target. id = 0
  30. Starting GDB server for "mb" target (id = 0) at TCP port no 1235
  31.  
  32. XMD% targets
  33. ------------------------------------------------
  34. System(2) - Hardware System on FPGA(Device 3) Targets:
  35. ------------------------------------------------
  36. Target(0) - MicroBlaze(1) Debug Target*
  37. XMD% WARNING: Connection Exists
  38. Error: MicroBlaze is not being clocked. Check if the Clock input to MicroBlaze and its Bus Interfaces are connected properly
  39. Software Breakpoint 0 Hit, Processor Stopped at 0x00000268
  40. Error: MicroBlaze is not being clocked. Check if the Clock input to MicroBlaze and its Bus Interfaces are connected properly
  41. Error: MicroBlaze is not being clocked. Check if the Clock input to MicroBlaze and its Bus Interfaces are connected properly
  42. Error: MicroBlaze is not being clocked. Check if the Clock input to MicroBlaze and its Bus Interfaces are connected properly
  43. Error: 
  44. Processor is stalled at FSL access

     

     I don't understand why " Error: MicroBlaze is not being clocked."  Why "Processor is stalled at FSL access"? 

 

 

    

   

 

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Visitor
Visitor
8,503 Views
Registered: ‎11-11-2011

Re: SDK debugger launch and execute problem in 14.2 and 14.5

Jump to solution

The issue has been resolved. The unstable behavior was caused by a faulty JTAG interface on the board, which had data integrity problem.

View solution in original post

0 Kudos
3 Replies
Highlighted
Anonymous
Not applicable
6,443 Views

Re: SDK debugger launch and execute problem in 14.2 and 14.5

Jump to solution

Can you check your MHS file to see if the Microblaze is indeed getting clocked correctly?

Can you then check the UCF file to make sure that this is contrained correctly

 and connected to a valid clock source?

0 Kudos
Highlighted
Visitor
Visitor
6,441 Views
Registered: ‎11-11-2011

Re: SDK debugger launch and execute problem in 14.2 and 14.5

Jump to solution

Stephen, Thank you for your reply. 

 

There should be no problem for the clock, as the microblaze runs fine after FPGA is programmed. 

My problem is I can't start the SDK debugger. After I start debugging the application.elf file on the hardware, 

the program counter indicator doesn't stop at he first line of the main(). If I run "step over", the indicator

gets lost right away or after a few steps. Meanwhile, in XMD console, I see the ERROR message

as I listed in my original post. 

 

I wonder if somehow the Microblaze's clock is lost after I started the SDK deubgger. I just can't 

figure out why. 

 

 

 

 

 

Attached is a snipping of the debugger when first launched. 

0 Kudos
Highlighted
Visitor
Visitor
8,504 Views
Registered: ‎11-11-2011

Re: SDK debugger launch and execute problem in 14.2 and 14.5

Jump to solution

The issue has been resolved. The unstable behavior was caused by a faulty JTAG interface on the board, which had data integrity problem.

View solution in original post

0 Kudos