debug_attributes.md

There are many User/Workspace Settings to control things globally. You can find these in the VSCode Settings UI. launch.json can override some of those settings. There is a lot of functionality that is available via Settings and some may be useful in a team environment and/or can be used across all bmp-debug sessions

The following attributes (properties) can be used in your launch.json to control various aspects of debugging. Also IntelliSense is an invaluable aid while editing launch.json. With IntelliSense, you can hover over an attribute to get more information and/or help you find attributes (just start typing a double-quote, use Tab key) and provide defaults/options.

If the type is marked as {...} it means that it is a complex item can have multiple types. Possibly consult our Wiki

Attribute	Type	Launch/ Attach	Description
BMPGDBSerialPort	string	Both	Deprecated: use 'port' instead. The serial port for the Black Magic Probe GDB Server.
armToolchainPath	string	Both	This setting can be used to override the armToolchainPath user setting for a particular launch configuration. This should be the path where arm-none-eabi-gdb, arm-none-eabi-objdump and arm-none-eabi-nm are located.
breakAfterReset	boolean	Both	Applies to Restart/Reset/Launch, halt debugger after a reset. Ignored if runToEntryPoint is used.
chainedConfigurations	object	Both	An object describing how additional configurations should be launched
chainedConfigurations .delayMs	number	Both	Default delay in milliseconds for a certain amount of milliseconds to begin launch. Inherited by children
chainedConfigurations .detached	boolean	Both	Related or independent server sessions. Set to true for servers like 'JLink'. Inherited by children
chainedConfigurations .enabled	boolean	Both	Enable/Disable entire set of chained configurations
chainedConfigurations .inherits	string[]	Both	List of properties to inherit from parent. Sorry, no IntelliSense
chainedConfigurations .launches	object[]	Both	undefined
chainedConfigurations .lifecycleManagedByParent	boolean	Both	Are Restart/Reset/Stop/Disconnect shared? All life-cycle management done as a group by parent/root. Inherited by children
chainedConfigurations .overrides	object	Both	Values to override/set in this child configuration. A set of name/value pairs. Set value to 'null' (no quotes) to delete. Sorry, no IntelliSense
chainedConfigurations .waitOnEvent	string	Both	Event to wait for. 'postStart' means wait for gdb-server connecting, 'postInit' is after init commands are completed by gdb. Inherited by children
cpu	string	Both	CPU Type Selection - used for QEMU server type
cwd	string	Both	Directory to run commands from
debuggerArgs	array	Both	Additional arguments to pass to GDB command line
device	string	Both	Target Device Identifier
executable	string	Both	Path of executable for symbols and program information. See also loadFiles, symbolFiles
gdbInterruptMode	string	Both	Whether GDB shall be interrupted using "exec-interrupt" (default) or by signaling "SIGINT"
gdbPath	string	Both	This setting can be used to override the GDB path user/workspace setting for a particular launch configuration. This should be the full pathname to the executable (or name of the executable if it is in your PATH). Note that other toolchain executables with the configured prefix must still be available.
gdbTarget	string	Both	For externally (servertype = "external") controlled GDB Servers you must specify the GDB target to connect to. This can either be a "hostname:port" combination or path to a serial port
graphConfig	{object}	Both	Description of how graphing can be done. See our Wiki for details
hardwareBreakpoints	object	Both	WARNING: Force only HW breakpoints to be used. By default GDB will use HW or SW breakpoints depending on memory type. Use this only in rare circumstances to work around issues in your gdb-server or hardware. This setting is NOT recommended for general use.
hardwareBreakpoints .limit	number	Both	If limit > 0, enforce a limit on the number of hardware breakpoints that can be used
hardwareBreakpoints .require	boolean	Both	If true, forces the use of hardware breakpoints
hardwareWatchpoints	object	Both	WARNING: Force only HW watchpoints to be used. By default GDB will use HW or SW watchpoints depending on memory type. Use this only in rare circumstances
hardwareWatchpoints .limit	number	Both	If limit > 0, enforce a limit on the number of hardware watchpoints that can be used
hardwareWatchpoints .require	boolean	Both	If true, forces the use of hardware watchpoints
interface	string	Both	Debug Interface type to use for connections (defaults to SWD) - Used for BMP probes.
liveWatch	object	Both	An object with parameters for Live Watch
liveWatch .enabled	boolean	Both	Enable/Disable Live Watch. Only applies to OpenOCD
liveWatch .samplesPerSecond	number	Both	Maximum number of samples per second. Different from GUI refresh-rate, which is a user/workspace setting
loadFiles	string[]	Launch	List of files (hex/bin/elf files) to load/program instead of the executable file. Symbols are not loaded (see symbolFiles). Can be an empty list to specify none. If this property does not exist, then the executable is used to program the device
machine	string	Both	Machine Type Selection - used for QEMU server type
numberOfProcessors	number	Both	Number of processors/cores in the target device.
objdumpPath	string	Both	This setting can be used to override the objdump (used to find globals/statics) path user/workspace setting for a particular launch configuration. This should be the full pathname to the executable (or name of the executable if it is in your PATH). Note that other toolchain executables with the configured prefix must still be available. The program 'nm' is also expected alongside
overrideAttachCommands	string[]	Attach	Override the commands that are normally executed as part of attaching to a running target. In most cases it is preferable to use preAttachCommands and postAttachCommands to customize the GDB attach sequence.
overrideGDBServerStartedRegex	string	Both	You can supply a regular expression (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions) in the configuration property to override the output from the GDB Server that is looked for to determine if the GDB Server has started. Under most circumstances this will not be necessary - but could be needed as a result of a change in the output of a GDB Server making it incompatible with bmp-debug. This property has no effect for bmp or external GDB Server types.
overrideLaunchCommands	string[]	Launch	Override the commands that are normally executed as part of flashing and launching the target. In most cases it is preferable to use preLaunchCommands and postLaunchCommands to customize the GDB launch sequence.
overridePreEndSessionCommands	string[]	Both	Override the commands that are normally executed at the start of ending a debug session (e.g. when stopping debugging).
overrideResetCommands	string[]	Both	Override the commands that are normally executed as part of reset-ing the target. When undefined the deprecated overrideRestartCommands is used if it exists.
port	string	Both	The serial port for the Black Magic Probe GDB Server. On Windows this will be "COM", on Linux this will be something similar to /dev/ttyACM0, on OS X something like /dev/cu.usbmodemE2C0C4C6 (do not use tty versions on OS X)
postAttachCommands	string[]	Attach	Additional GDB Commands to be executed after the main attach sequence has finished.
postLaunchCommands	string[]	Launch	Additional GDB Commands to be executed after the main launch sequence has finished.
postResetCommands	string[]	Both	Additional GDB Commands to be executed at the end of the reset sequence. When undefined the deprecated postRestartCommands is used.
postResetSessionCommands	string[]	Launch	Additional GDB Commands to be executed at the end of the reset sequence
postStartSessionCommands	string[]	Both	Additional GDB Commands to be executed at the end of the start sequence, after a debug session has already started and runToEntryPoint is not specified.
powerOverBMP	string	Both	Power up the board over Black Magic Probe. "powerOverBMP" : "enable" or "powerOverBMP" : "disable". If not set it will use the last power state.
preAttachCommands	string[]	Attach	Additional GDB Commands to be executed at the start of the main attach sequence (immediately after attaching to target).
preLaunchCommands	string[]	Launch	Additional GDB Commands to be executed at the start of the main launch sequence (immediately after attaching to target).
preResetCommands	string[]	Both	Additional GDB Commands to be executed at the start of the reset sequence. When undefined the deprecated preRestartCommands is used.
rtos	string	Both	RTOS being used. Currently only "zephyr" is supported. When set to "zephyr", the extension will automatically source zephyr_gdb.py and enable MI command overrides for RTOS thread awareness.
rttConfig	object	Both	SEGGER's Real Time Trace (RTT) and supported by JLink, OpenOCD and perhaps others in the future
rttConfig .address	string	Both	Address to start searching for the RTT control block. Use "auto" for BMP-Debug to use the address from elf file
rttConfig .clearSearch	boolean	Both	When true, clears the search-string. Only applicable when address is "auto"
rttConfig .decoders	{object}	Both	SWO Decoder Configuration
rttConfig .enabled	boolean	Both	Enable/Disable RTT
rttConfig .polling_interval	number	Both	number of milliseconds (> 0) to wait for check for data on out channels. Only for OpenOCD
rttConfig .rtt_start_retry	number	Both	Keep trying to start RTT for OpenOCD until it succeeds with given internal in milliseconds. <= 0 means do not retry. Only for OpenOCD
rttConfig .searchId	string	Both	A string to search for to find the RTT control block. If 'address' is 'auto', use ONLY if you have a custom RTT implementation
rttConfig .searchSize	number	Both	Number of bytes to search for the RTT control block. If 'address' is 'auto', use ONLY if you have a custom RTT implementation
rttEnabled	boolean	Both	Enable RTT (Real-Time Transfer) on the Black Magic Probe. When true, 'monitor rtt enable' is automatically sent before attach/launch.
runToEntryPoint	string	Both	Applies to Launch/Restart/Reset, ignored for Attach. If enabled the debugger will run until the start of the given function.
serverArgs	string[]	Both	Additional arguments to pass to GDB Server command line
serverpath	string	Both	This setting can be used to override the GDB Server path user/workspace setting for a particular launch configuration. It is the full pathname to the executable or name of executable if it is in your PATH
servertype	string	Both	GDB Server type - supported types are bmp, qemu, and external.
showDevDebugOutput	string	Both	Used to debug this extension. Prints all GDB responses to the console. 'raw' prints gdb responses, 'parsed' prints results after parsing, 'both' prints both. 'vscode' shows raw and VSCode interactions
showDevDebugTimestamps	boolean	Both	Show timestamps when 'showDevDebugOutput' is enabled
svdFile	string	Both	This is for 'XPERIPHERALS' window provided by 'mcu-debug.peripheral-viewer'. It can be a simple file name or more based on a CMSIS pack or deviceName. See 'mcu-debug.peripheral-viewer' for format
svdPath	string	Both	This is for 'XPERIPHERALS' window provided by 'mcu-debug.peripheral-viewer' and 'Embedded Tools' Extension from Microsoft. It can be a simple file name. For 'mcu-debug.peripheral-viewer' or more based on a CMSIS pack or deviceName. See 'mcu-debug.peripheral-viewer' for format
swoConfig	object	Both	Description of SWO can be configured. Also see our Wiki for details
swoConfig .cpuFrequency	number	Both	Target CPU frequency in Hz.
swoConfig .decoders	{object}	Both	SWO Decoder Configuration
swoConfig .enabled	boolean	Both	Enable SWO decoding.
swoConfig .source	string	Both	Source for SWO data. Can either be "probe" to get directly from debug probe, or a serial port device to use a serial port external to the debug probe.
swoConfig .swoEncoding	string	Both	BMP only: SWO encoding data used at the line level. Depends on the probe hardware, native (the original one) supports only Manchester (self-clocked, but slower rates) while most other platforms (e.g. ST-LINK with BMP firmware) support only UART (frequency/baud rate has to match to within ~2%).
swoConfig .swoFrequency	number	Both	SWO frequency in Hz.
swoConfig .swoPath	string	Both	Path name when source is "file" or "serial", device name regex match when source is "probe" for BMP. Typically a /path-name or a serial-port-name
swoConfig .swoPort	string	Both	When server is "external" && source is "socket", port to connect to. Format [host:]port. For BMP, specifies the regex match of the USB interface contianing raw SWO data.
symbolFiles	object[]	Both	Array of ELF files to load symbols from instead of the executable file. Each item in the array cab be a string or an object. Program information is ignored (see loadFiles). Can be an empty list to specify none. If this property does not exist, then the executable is used for symbols
targetId	string | number	Both	On BMP this is the ID number that should be passed to the attach command (defaults to 1).
targetProcessor	number	Both	The processor you want to debug. Zero based integer index. Must be less than 'numberOfProcessors'
toolchainPrefix	string	Both	This setting can be used to override the toolchainPrefix user setting for a particular launch configuration. Default = "arm-none-eabi"