MCU Peripheral Viewer

Standalone SVD Viewer extension extracted from cortex-debug but now work with any debugger that supports the Microsoft Debug Protocol

Specifying SVD Files

The SVD Viewer extension uses System View Description (SVD) files to display information about the selected part, including the Cortex Peripherals view.

Choose one of the following methods to specify your SVD file in your launch.json configuration(s):

Use the CMSIS pack asset service

Set the svdPath configuration variable to a qualified pack reference in the form <vendor>::<device family pack>@<version> e.g.:

{
    ...
    "svdPath": "NXP::K32L3A60_DFP@15.0.0"
    ...
}

If the pack supports multiple devices and/or processors, you will be prompted to select these. Alternatively, set them in your configuration using the optional deviceName and processorName variables:

{
    ...
    "svdPath": "NXP::K32L3A60_DFP@15.0.0",
    "deviceName": "K32L3A60VPJ1A",
    "processorName": "cm4"
    ...
}

TIP: The pack reference and device name can be automatically derived if you use the Arm Device Manager extension in VS Code using these commands:

{
    ...
    "svdPath": "${command:device-manager.getDevicePack}",
    "deviceName": "${command:device-manager.getDeviceName}"
    ...
}

Install a Cortex Debug Support Pack

Find a Cortex Debug Support Pack for your device and install it. You can then specify just the deviceName variable in your launch configuration:

{
    ...
    "deviceName": "STM32F439BI"
    ...
}

Specify the path to your SVD file

You can obtain an SVD file from a CMSIS pack or from your device manufacturer. For example use these instructions for ST devices.

Other vendors may ship SVD files when you install their software or device packs or you could write your own custom SVD file.

Once you have the SVD file, specify the location of it in your launch.json using the svdPath variable:

{
    ...
    "svdPath": "${workspaceFolder}/STM32F103.svd"
    ...
}

Settings

All variable key names used to extract data from debug launch configurations can be modified. This allows variable name clashes to be avoided as well as the need to duplicate configuration entries.

The following list outlines the setting names and default values: