1. This material exempt per Department of Commerce license exception TSU Debugging

2. Debugging 2 Objectives After completing this module, you will be able to: Understand the basic concepts of the Eclipse IDE List Xilinx Software Development Kit (SDK) features Describe GNU Debugger (GDB) functionality Describe Xilinx Microprocessor Debugger (XMD) functionality Describe the integration of XMD and GDB with SDK

3. Debugging 3 Outline Software Development Kit Debugging Tools Debugging Using XPS Debugging Using SDK

4. Debugging 4 Java-based application development environment Based on the open-source effort by the Eclipse Consortium\ Feature-rich C/C++ code editor and compilation environment Project management Application build configuration and automatic Makefile generation Error Navigation Well-integrated environment for seamless debugging of embedded targets Source code version control Xilinx Platform Studio Software Development Kit (SDK)

5. Debugging 5 Xilinx Extensions to Eclipse SDK leverage on Eclipse + CDT – Project Management – Makefile builder – Code editor, Error Navigation – Debug – Search SDK value add to CDT – Debug integration using XMD – Xilinx Custom Compiler settings for PowerPC, MicroBlaze – Profiling Flow and Visualization – Productization Java Virtual Machine Platform Studio SDK Extensions C/C++ Development Perspective Eclipse platform

6. Debugging 6 Eclipse/CDT Frameworks Builder framework – Compiles and Links Source files – Default Build options are specified when application is created: Choice of Debug, Release, Profile configurations – User can custom build options later when developing application – Build types: Standard Make, Managed Make Launch framework – Specifies what action needs to be taken: Run (+ Profile) application or Debug application – In SDK, this is akin to the Target Connection settings Debug framework – Launches debugger (gdb), loads application and begins debug session – Debug views show information about state of debug session – Hides ugliness of debug details Search framework – Helps development of application Help System – Online help system; context-sensitive

7. Debugging 7 SDK Application Development Flow Create software App Project Add sources + Edit Compile + Link Generate Hardware Platform Done? Import ELF file, Download to board Debug / Profile Platform Studio SDK Yes Generate Software Platform libraries, drivers Platform Studio

8. Debugging 8 Workspaces and Perspectives Workspace – Location to store preferences & internal info about Projects – Transparent to SDK users – In SDK, source files not stored under Workspace Views, Editors – Basic User interface element Perspectives – Collection of functionally related views – Layout of views in a perspective can be customized according to user preference

9. Debugging 9 Perspectives

10. Debugging 10 CVS Perspective

11. Debugging 11 Views Eclipse Platform views: Navigator view, Tasks view, Problems view Debug views: Stack view, Variables view C/C++ views: Projects view, Outline view

12. Debugging 12 Opening Perspectives and Views To open a Perspective, use Window  Open Perspective To open a view, use Window  Show View If the view is already present in the current perspective, the view is highlighted

13. Debugging 13 Editors bracket matching syntax coloring content assist refactoring keyboard shortcuts

14. Debugging 14 SDK Workbench C/C++ project outline displays the elements of a project with file decorators (icons) for easy identification C/C++ editor for integrated software creation Code outline displays elements of the software file under development with file decorators (icons) for easy identification Problems, Console, Properties view lists output information associated with the software development flow 1 2 3 4 1 2 3 4

15. Debugging 15 Outline Software Development Kit Debugging Tools Debugging Using XPS Debugging Using SDK

16. Debugging 16 Introduction Debugging is an integral part of embedded systems development The debugging process is defined as testing, stabilizing, localizing, and correcting errors Two methods of debugging – Hardware debugging via a logic probe, logic analyzer, in-circuit emulator, or background debugger – Software debugging via a debugging instrument A software debugging instrument is source code that is added to the program for the purpose of debugging Debugging types – Functional debugging – Performance debugging

17. Debugging 17 Hardware Debugging Support ChipScope™ Pro tool cores are now included for adding to a Xilinx Platform Studio design – PLB IBA (Integrated Bus Analyzer) – OPB IBA – VIO (Virtual I/O) ChipScope Pro tool available thru donation Enables co-debug of software with GNU gdb and hardware with ChipScope Analyzer

18. Debugging 18 Software Debugging Support EDK supports software debugging via: – GNU Debugger (GDB) tools Unified interface for debugging and verifying MicroBlaze  and PowerPC  systems – Xilinx Microprocessor Debugger (XMD) Runs all of the hardware debugging tools and communicates with the hardware – GNU tools communicate with the hardware through XMD

19. GDB Functionality Target Hardware PowerPC System PPC405 Debug Port User Interface (TCP/IP) GDB Remote Protocol Host Software PowerPC-eabi-gdb Host Software Tcl/Terminal Interface XMD PPC Cycle-Accurate Instruction Set Simulator Host (TCP Socket Interface) JTAG

20. GDB Functionality GDB is a source-level debugger that helps you debug your program: – Start your program – Set breakpoints (make your program stop on specified conditions) – Examine what has happened, when your program encounters breakpoints Registers Memory Stack Variables Expressions – Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another You can use GDB to debug programs written in C and C++

21. GDB Memory Location Assembly Instructions C Code

22. GDB Functionality Breakpoints can be enabled or disabled To change any memory value, simply double-click in a memory field

23. GDB Functionality Blue represents registers that have changed To change any value, double-click in a field

24. XMD Functionality User Interface Target Hardware (TCP/IP) GDB Remote Protocol JTAG PowerPC System PPC405 Debug Port Host Software PowerPC-eabi-gdb Host Software Tcl/Terminal Interface XMD PPC Cycle-Accurate Instruction Set Simulator Host (TCP Socket Interface)

25. XMD Functionality Xilinx Microprocessor Debug (XMD) engine – A program that facilitates a unified GDB interface – A Tool command language(TCL) interface XMD supports debugging user programs on different targets – Cycle-accurate PowerPC  processor instruction set simulator – PowerPC  system on a hardware board GDB communicates with xmd by using the Remote TCP protocol and control the corresponding targets GDB can connect to xmd on the same computer or on a remote computer on the Internet

26. Debugging 26 Simultaneous HW/SW Debug ChipScope™ Pro PLB & IBA cores in target ChipScope Pro Analyzer on host GDB debugger on host XMD supports simultaneous access over Xilinx parallel cables PLB/OPB IBA instantiation in XPS – Are treated like the peripheral cores IBA MDM Set breakpoint in GDB – when hit → triggers ChipScope Set trigger in ChipScope – when hit → halts CPU and debugger stops Minimal “skid-by” as cross triggering is done on chip between IBA cores and PPC & MicroBlaze debug interfaces

27. Debugging 27 Simultaneous HW/SW Debug XMD Xilinx Parallel Cable Active trigger when addr bus = 0xC200 Trigger out signal from IBA to CPU debug halt signal in

28. Debugging 28 Outline Software Development Kit Debugging Tools Debugging Using XPS Debugging Using SDK

29. Debugging 29 A Debugging Sample This will go through the necessary steps, generate a bitstream file, and download the file Compile with the debugging option 1 Download the bitstream 2

30. Debugging 30 Start XMD Set XMD Debug Options 3 This opens a connection with the hardware, indicating whether the connecting port, caches, DCR, and TLB are enabled or not Start the XMD shell 4 Set connection type and JTAG properties

31. Debugging 31 Start Software Debugger 5 A source code window displays A source code window displays 6 Change the code window display from SOURCE to MIXED to show C and assembly code If there are more than one application in the project then the tools will provide choice to select an application

32. Debugging 32 Software Debugger Connect A window displaying C and assembly code A window displaying C and assembly code 7 Select the target as Remote/TCP: XMD Select the target as Remote/TCP: XMD 8 Enter that port number that was displayed during ppc-connect

33. Debugging 33 Debug Program Set any breakpoints as necessary 9 Click the Run button 10 When a breakpoint is encountered, the debugger will stop 11 View the necessary windows 12 Exit debugger by typing quit in the console window

34. Debugging 34 Outline Software Development Kit Debugging Tools Debugging Using XPS Debugging Using SDK

35. Debugging 35 Debugging Using SDK Eclipse CDT XMD powerpc-eabi-gdb (or) mb-gdb JTAG / XMD protocol Xilinx custom graphical debug interface auto-launched gdb remote protocol

36. Debugging 36 SDK Debug Perspective The stack frame for target threads that you are debugging. Each thread in your program is represented as a node in the tree Variables, Breakpoints, and Registers views allow for viewing and real-time interaction with the view contents for more powerful debugging potential C/C++ editor highlights the location of the execution pointer, along with allowing the setting of breakpoints Code outline and disassembly view provide compiler level insight to what is occurring in the running source Console view lists output information 1 2 3 4 5 5 43 2 1

37. Debugging 37 Debugging in XPS vs SDK Debugging in XPS -Download bitstream from XPS -Launch XMD -Provide Target Connection Options -Launch GDB (Insight GUI) -Set GDB Server connection port in GDB -Download program -Begin Debugging Debugging in SDK -Download bitstream from XPS -Launch XMD -Provide Target Connection Options -Launch GDB (Insight GUI) -Set GDB Server connection port in GDB -Download program -Begin Debugging

38. Debugging 38 Skills Check

39. Debugging 39 Review Questions Into what parts of the design do debuggers provide visibility?

40. Debugging 40 Answers Into what parts of the design do debuggers provide visibility? – Registers – Memory – Stack – Variables – Expressions

41. Where Can I Learn More? Tool documentation – Embedded System Tools Guide  GNU Compiler Tools – Embedded System Tools Guide  GNU Debugger – Embedded System Tools Guide  Xilinx Microprocessor Debugger – Xilinx Platform Studio SDK Online Documentation Support website – EDK Home Page: support.xilinx.com/edk