Visible to Intel only — GUID: pyu1697418585210
Ixiasoft
1. About the RiscFree* IDE
2. Installation and Setup
3. Getting Started with RiscFree* IDE
4. Debug Setup for Nios® V Processor System
5. Debug Setup for Arm* Hard Processor System
6. Debugging with RiscFree* IDE
7. Debugging with Command-Line Interface
8. Ashling RiscFree* Integrated Development Environment (IDE) for Intel® FPGAs User Guide Archives
9. Document Revision History for the Ashling RiscFree* Integrated Development Environment (IDE) for Intel® FPGAs User Guide
A. Appendix
6.1. Debug Features in RiscFree* IDE
6.2. Processor System Debug
6.3. Heterogeneous Multicore Debug
6.4. Debugging µC/OS-II Application
6.5. Debugging FreeRTOS Application
6.6. Debugging Zephyr Application
6.7. Arm* HPS On-Chip Trace
6.8. Debugging the Arm* Linux Kernel
6.9. Debugging Target Software in an Intel® Simics Simulator Session
Visible to Intel only — GUID: pyu1697418585210
Ixiasoft
6.8.1. Preparing Linux for Kernel Debugging
To allow kernel and module debugging, you must enable the CONFIG_DEBUG_INFO and CONFIG_GDB_SCRIPTS configurations during the Linux kernel's build process. Use the following commands to enable the configuration parameters on top of the default kernel configuration.
make defconfig ./scripts/config --set-val CONFIG_DEBUG_INFO y ./scripts/config --set-val CONFIG_GDB_SCRIPTS y make oldconfig
You can also change these options using the make menuconfig command.
Note: Newer kernel versions define the CONFIG_DEBUG_INFO automatically based on other debugging options in the kernel. Refer to your kernel documentation for more details if the above command does not successfully set CONFIG_DEBUG_INFO=y in the resulting kernel .config file.