OS Awareness Manual Linux - Lauterbach

1 OS Awareness Manual Linux TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents .. OS Awareness Manuals .. OS Awareness and Run Mode Debugging for Linux .. OS Awareness Manual Linux .. 1. History .. 5. Debugging Modes for Embedded Linux .. 5. Run Mode Debugging with TRACE32 as GDB Front-end 5. Stop Mode Debugging via JTAG 5. Integrated Run & Stop Mode Debugging via JTAG 6. Supported Debugging Modes sorted by Architectures 7. Overview .. 8. Brief Overview of Documents for New Users .. 8. Supported Versions .. 9. Configuration .. 10. Quick Configuration Guide 10. Hooks & Internals in Linux 11. Features .. 12. Display of Kernel Resources 12. Task-Related Breakpoints 12. Task Context Display 13. MU Support 15. Space IDs 15. MMU Declaration 15. Scanning System and Processes 20.

2 Symbol Autoloader 22. SMP Support 23. Dynamic Task Performance Measurement 24. Task Runtime Statistics 24. Process / thread switch support for ARM using context ID register: 25. Task State Analysis 25. Function Runtime Statistics 26. Linux Specific Menu 28. 1989-2018 Lauterbach GmbH. OS Awareness Manual Linux 1. Basics of HW-based Debugging .. 30. Debugging Linux Kernel and User Processes .. 30. Linux Kernel 31. Downloading the Kernel 31. Debugging the Kernel Startup 32. Debugging the Kernel 32. User Processes 33. Debugging the Process 33. Debugging into Shared Libraries 35. Debugging Linux Threads 36. On Demand Paging 36. Kernel Modules 41. Trapping Segmentation Violation 44. Linux Commands .. 45. Check Awareness integrity 45. Display the kernel ring buffer 45.

3 Display tasks 46. Display the device tree blob 47. Display the device tree source 47. Display file system internals 47. Display process maps 48. Scan process MMU space 48. Display kernel modules 48. Set Awareness options 49. Display processes 50. Display ps output 50. Process/Module symbol management 51. Unload process symbols and MMU 51. Unload library symbols 52. Unload module symbols and MMU 52. Load process symbols and MMU 53. Load library symbols 54. Load module symbols and MMU 54. Set symbol management options 55. Mark task state words 58. Display vmalloced areas 58. Watch processes 59. Add process to watch list 59. Remove process from watch list 59. Disable watch system 60. Disable process creation breakpoints 60. Enable watch system 60. Enable process creation breakpoints 61.

4 1989-2018 Lauterbach GmbH. OS Awareness Manual Linux 2. Set watch system options 61. Show watched processes 62. Linux PRACTICE Functions .. 65. () Target architecture 65. () OS Awareness configuration information 65. () Magic or space ID of current task 65. () Awareness error code 66. () Awareness error help ID 66. () Library load address 66. () Library code size 67. () Library target path and name 67. () Code start address of module 67. () Data start of module 68. () Size of module 68. () Magic value of module 68. () Structure address of module 68. () Name of module magic 69. () Address of a specified module's section 69. () Name of a module section with a given number 69. () Address of a module section with a given number 70. () Version of the used Linux OS 70.

5 () Code start address of process 70. () Code size of process 70. () Data start address of process 71. () Data size of process 71. () List of processes 72. () Magic value of process 72. () Space ID of process 73. () Name of process 73. () Trace ID of process 73. () Path and file name of executable on target 73. () Process ID 74. () Magic value of process 74. () Space ID of process 74. () Control structure address of task 74. () Trace ID of process 75. () End address of a process virtual memory area 75. () Start address of a process virtual memory area 75. () Build number of Linux Awareness 76. () Build date of Linux Awareness 76. Error Messages .. 77. Appendix .. 78. 1989-2018 Lauterbach GmbH. OS Awareness Manual Linux 3. Appendix A: insmod patch for Linux 78.

6 Appendix B: ARM context ID thread patch for Linux and 82. Example patch for an ARM926 82. Example patch for Cortex implementations 83. Frequently-Asked Questions .. 85. 1989-2018 Lauterbach GmbH. OS Awareness Manual Linux 4. OS Awareness Manual Linux Version 16-Nov-2018. History 28-Aug-18 The title of the Manual was changed from RTOS Debugger for <x> to OS Awareness Manual <x> . Debugging Modes for Embedded Linux TRACE32 provides 3 modes for debugging embedded Linux : Run Mode Debugging, Stop Mode Debugging and Integrated Run & Stop Mode Debugging. Run Mode Debugging with TRACE32 as GDB Front-end Pure software debugger, no TRACE32 hardware required. The TRACE32 software is licensed by a USB dongle. Requires a gdbserver/gdbstub running on the target. The TRACE32 GDB Front-end works in so-called Run Mode Debugging: At a breakpoint only the selected process is stopped, while the kernel and all other processes continue to run.

7 The TRACE32 GDB Front End is described in the document TRACE32 as GDB Front-End . ( ). Stop Mode Debugging via JTAG. Stop Mode Debugging requires a TRACE32 JTAG debugger hardware. If debugging is performed via the JTAG interface, TRACE32 works in so-called Stop Mode Debugging. At a breakpoint the CPU and thus the whole target system is stopped. 1989-2018 Lauterbach GmbH. OS Awareness Manual Linux 5. The main advantages of Stop Mode Debugging are: Since the only requirement for Stop Mode Debugging is a functioning JTAG interface, debugging can start at the reset vector. Since TRACE32 provides both Linux and MMU support, debugging of the kernel and beyond process boundaries is possible. Stop Mode Debugging is described in the document OS Awareness Manual Linux ( ).

8 Integrated Run & Stop Mode Debugging via JTAG. Integrated Run & Stop Mode Debugging requires a TRACE32 JTAG debugger hardware. If debugging is performed via the JTAG interface, TRACE32 can be configured: To allow Stop Mode Debugging via JTAG. To allow Run Mode Debugging via the t32server/gdbserver running as debug agent on the target. To allow, if required, to switch between the two debugging modes. TRACE32 communicates with: The gdbserver via ethernet for all supported architectures (see table on next page) or The t32server via DCC (Debug Communications Channel) for the ARM architecture. Since the ARM-JTAG interface provides a DCC, Integrated Run & Stop Mode Debugging can function with JTAG as the only communication interface. 1989-2018 Lauterbach GmbH. OS Awareness Manual Linux 6.

9 Supported Debugging Modes sorted by Architectures Architecture GDB Front-end Stop Mode Integrated Run &. Debugging Stop Mode Debugging ARM Yes, refer to Yes, read this Yes, via DCC, TRACE32 as GDB Manual . refer to Run Mode Front-End Debugging Manual ( ). Linux . ( ). ARM64 Yes, read this . Manual . ColdFire Yes, read this . Manual . x86 / x64 Yes, refer to Yes, read this . TRACE32 as GDB Manual . Front-End . ( ). MIPS / MIPS5 Yes, refer to Yes, read this Yes, via ethernet, TRACE32 as GDB Manual . refer to Run Mode Front-End Debugging Manual ( ). Linux . ( ). PowerPC Yes, refer to Yes, read this Yes. via ethernet, TRACE32 as GDB Manual . refer to Run Mode Front-End Debugging Manual ( ). Linux . ( ). SH4 Yes, refer to Yes, read this Yes. via ethernet, TRACE32 as GDB Manual .

10 Refer to Run Mode Front-End Debugging Manual ( ). Linux . ( ). XScale Yes, refer to Yes, read this . TRACE32 as GDB Manual . Front-End . ( ). 1989-2018 Lauterbach GmbH. OS Awareness Manual Linux 7. Overview The OS Awareness for Linux contains special extensions to the TRACE32 Debugger. This Manual describes the additional features, such as additional commands and statistic evaluations. Linux uses the terms Processes and Tasks . If not otherwise specified, the TRACE32 term Task . corresponds to Linux tasks, which may be executing processes or POSIX threads. Brief Overview of Documents for New Users Architecture-independent information: Debugger Basics - Training ( ): Get familiar with the basic features of a TRACE32 debugger. T32 Start ( ): T32 Start assists you in starting TRACE32 PowerView instances for different configurations of the debugger.