Arm CMSIS Debugger
The Arm® CMSIS Debugger extension is an extension pack for Visual Studio Code® that demonstrates how to combine technologies from various open source projects to create a comprehensive debug platform for Arm-based IoT solutions.
Related open source projects are
- Open-CMSIS-Pack of which this extension is part of.
- Eclipse® CDT.cloud™, an open-source project that hosts a number of components and best practices for building customizable web-based C/C++ tools.
- pyOCD, a Python based tool and API for debugging, programming, and exploring Arm Cortex® microcontrollers.
- GDB, the debugger of the GNU Project.
The Arm CMSIS Debugger Extension Pack
The Arm CMSIS Debugger extension is an extension pack. It allows to install multiple separate extensions together.
Included Extensions
The following extensions are included in this extension pack:
- CDT™ GDB Debug Adapter Extension, an Eclipse CDT.cloud extension that supports debugging using GDB and any other debuggers that supports the MI protocol.
- Memory Inspector, an Eclipse CDT.cloud extension that provides a powerful and configurable memory viewer that works with debug adapters.
- Peripheral Inspector, an Eclipse CDT.cloud extension that provides a CMSIS SVD viewer and works with debug adapters.
Recommended Extensions
We recommend to install the following extensions to simplify the user experience:
- Arm Tools Environment Manager, an extension that allows to download, install, and manage software development tools using Microsoft® Vcpkg artifacts. Use this extension to for example install the
GCC compiler for ARM CPUs which comes with a GDB variant for Arm CPUs.
- Arm CMSIS Solution, an extension that is a graphical user interface for csolution projects that use the CMSIS-Toolbox. Use this extension to build your csolution projects, to generate
*.cbuild-run.yml debug configuration files, and to make use of contributed commands in your debug launch configurations.
Debug Setup
The debug setup requires a GDB installation supporting the GDB remote protocol and that can connect to a GDB server like pyOCD.
We recommend to install the Arm GNU Toolchain using the Arm Tools Environment Manager extension. It comes with arm-none-eabi-gdb which is used in the Arm CMSIS Debugger default debug configurations.
pyOCD Debug Setup
This extension includes a pyOCD distribution which is used by default.
If you wish to use a different pyOCD installation, enter the full path to the executable (including the file name) in the target>server setting.
SEGGER® J-LINK® Debug Setup
Install the latest J-LINK Software and Documentation Pack from SEGGER. Ensure all required drivers and host platform specific settings are done.
The extension expects the installation folder to be on your system PATH environment variable. Alternatively, update your debug configuration's target>server setting to contain the full path to the J-LINK GDB server executable (including the file name).
Extension Functionality
This extension contributes additional functionality to work seamlessly with other extensions.
- The pseudo debugger types
cmsis-debug-pyocd and cmsis-debug-jlink. These types allow a more seamless integration into your IDE. However, these are not full debug adapters but generate debug configurations of type gdbtarget which comes with the CDT GDB Debug Adapter Extension.
- A debug configuration provider for the type
gdbtarget which comes with the CDT GDB Debug Adapter Extension. This provider automatically fills in default values for known remote GDB servers when launching a debug session.
- CMSIS specific launch configuration items for the
* debugger type, i.e. visible for all debugger types. It depends on the actually used debug adapter type if this information is known and utilized.
Pseudo Debugger Types
This section describes the contributed pseudo debugger types and their support through the contributed debug configuration provider for type gdbtarget.
CMSIS Debugger (pyOCD) - cmsis-debug-pyocd
The cmsis-debug-pyocd debugger type is used to add a debug configuration in the launch.json file for debugging with GDB and pyOCD.
This configuration uses the gdbtarget debugger type registered by the CDT GDB Debug Adapter Extension.
Additionaly, the extension contributes a debug configuration resolver which automatically fills the following gaps during debug launch:
- If option
target>server is set to pyocd, then it expands to the absolute path of the built-in pyOCD distribution.
- Extends the
target>serverParameters list of pyocd command line arguments:
- Prepends
gdbserver if not present.
- Appends
--port <gdbserver_port> if the target>port setting is set, where <gdbserver_port> gets that port setting's value.
- Appends
--cbuild-run and the corresponding cbuildRunFile path if cmsis>cbuildRunFile is set.
Note: The built-in version of pyOCD supports the command line option --cbuild-run which isn't available in releases outside this extension.
CMSIS Debugger (J-LINK) - cmsis-debug-jlink
The cmsis-debug-jlink debugger type is used to add a debug configuration in the launch.json file for debug with GDB and the SEGGER J-LINK GDB server.
This configuration uses the gdbtarget debugger type registered by the CDT GDB Debug Adapter Extension.
Note: The generated default debug configuration uses the value JLinkGDBServer as target>server setting. This executable has differing behavior on supported host platform:
- Linux and macOS: A GUI-less version of the GDB server is launched.
- Windows®: A GDB server with GUI is launched. Update
target>server to JLinkGDBServerCL to launch a GUI-less version on Windows, too.
Additionaly, the extension contributes a debug configuration resolver which automatically fills the following gaps during debug launch:
- Extends the
target>serverParameters list of JLinkGDBServer/JLinkGDBServerCL command line arguments:
- Appends
--port <gdbserver_port> if the target>port setting is set, where <gdbserver_port> gets that port setting's value.
Known Limitations and Workarounds
pyOCD fails to load *.cbuild-run.yml in the default configuration
When I use the default debug configuration for pyOCD, I get errors that pyOCD cannot find the solutions *.cbuild-run.yml file.
Possible Reasons:
- The application's CMSIS solution was initially built with a CMSIS-Toolbox version prior to v2.8.0 which is the first version to generate
*.cbuild-run.yml files.
- You are using an Arm CMSIS Solution extension prior to v1.52.0 which is the first version to fully support the
${command:cmsis-csolution.getCbuildRunFile} command.
Workarounds/Solutions:
- Update the CMSIS-Toolbox to the latest version. Additionally, you may have to run
cbuild setup --update-rte in a terminal for a first-time generation of *.cbuild-run.yml file in an existing workspace.
- Update to Arm CMSIS Solution extension v1.52.0. Alternatively, replace
${command:cmsis-csolution.getCbuildRunFile} with the path to the *.cbuild-run.yml in your workspace (cmsis>cbuildRunFile debug configuration setting).
When I download an AXF file built with Arm Compiler 6, I see the following warning and my application does not execute correctly. This happens regardless of the selected GDB server.
warning: Loadable section "RW_RAM0" outside of ELF segments
in /path/to/my/application.axf
Possible Reason: arm-none-eabi-gdb does not correctly load ELF program segments due to the way that Arm Compiler 6 generates section and program header information when scatterloading is used.
Workaround: You can generate a HEX file for the program download, and the ELF file for debug purposes only. The following steps are required if you build a CSolution-based application with the CMSIS-Toolbox:
- Edit the
*.cproject.yml file(s) of your application.
- Modify the
output:type: node to generate both an elf and a hex file:
output:
type:
- elf
- hex
- Build the solution.
- Keep the default configuration's
program setting as is.
"program": "${command:cmsis-csolution.getBinaryFile}",
- Modify the default debug configuration's
initCommands list, so that the load command gets the relative path to the generated HEX file.
"initCommands": [
"load ./relative/path/to/my/application.hex",
"break main"
],
This instructs the debugger to load the debug information from the ELF file and to use the HEX file for program download.
arm-none-eabi-gdb generates the following warnings when I debug ELF files with DWARF debug information of standard version 4 and earlier. And the debug illusion seems to be broken in many places.
warning: (Internal error: pc 0x8006a18 in read in CU, but not in symtab.)
Possible Reason: arm-none-eabi-gdb works best with DWARF debug information of standard version 5.
Solution: Make sure to build your application ELF file with DWARF version 5 debug information. Please refer to your toolchain's user reference manual. This may require updates to all build tools like compiler and assembler. For example use -gdwarf-5 for armclang.
Trademarks
Arm and Cortex are registered trademarks of Arm Limited (or its subsidiaries or affiliates) in the US and/or elsewhere.
Windows, Visual Studio Code, VS Code, and the Visual Studio Code icon are trademarks of Microsoft Corporation. All rights reserved.
Mac and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions.
Eclipse, CDT, and CDT.cloud are trademarks of Eclipse Foundation, Inc.
SEGGER and J-LINK are registered trademarks of SEGGER Microcontroller GmbH.
Node.js is a registered trademark of the OpenJS Foundation.
GDB and GCC are part of the GNU Project and are maintained by the Free Software Foundation.
