@@ -10,12 +10,12 @@ Choose one of the following methods to specify your SVD file in your `launch.jso
1010
1111### Use the CMSIS pack asset service
1212
13- Set the ` svdPath ` configuration variable to a qualified pack reference in the form ` <vendor>::<device family pack>@<version> ` e.g.:
13+ Set the ` definitionPath ` configuration variable to a qualified pack reference in the form ` <vendor>::<device family pack>@<version> ` e.g.:
1414
1515``` json
1616{
1717 ...
18- "svdPath " : " NXP::K32L3A60_DFP@15.0.0"
18+ "definitionPath " : " NXP::K32L3A60_DFP@15.0.0"
1919 ...
2020}
2121```
@@ -25,7 +25,7 @@ If the pack supports multiple devices and/or processors, you will be prompted to
2525``` json
2626{
2727 ...
28- "svdPath " : " NXP::K32L3A60_DFP@15.0.0" ,
28+ "definitionPath " : " NXP::K32L3A60_DFP@15.0.0" ,
2929 "deviceName" : " K32L3A60VPJ1A" ,
3030 "processorName" : " cm4"
3131 ...
@@ -37,7 +37,7 @@ __TIP:__ The pack reference and device name can be automatically derived if you
3737``` json
3838{
3939 ...
40- "svdPath " : " ${command:device-manager.getDevicePack}" ,
40+ "definitionPath " : " ${command:device-manager.getDevicePack}" ,
4141 "deviceName" : " ${command:device-manager.getDeviceName}"
4242 ...
4343}
@@ -61,12 +61,12 @@ You can obtain an SVD file from a [CMSIS pack](https://developer.arm.com/tools-a
6161
6262Other vendors may ship SVD files when you install their software or device packs or you could write your own custom SVD file.
6363
64- Once you have the SVD file, specify the location of it in your ` launch.json ` using the ` svdPath ` variable:
64+ Once you have the SVD file, specify the location of it in your ` launch.json ` using the ` definitionPath ` variable:
6565
6666``` json
6767{
6868 ...
69- "svdPath " : " ${workspaceFolder}/STM32F103.svd"
69+ "definitionPath " : " ${workspaceFolder}/STM32F103.svd"
7070 ...
7171}
7272```
@@ -77,6 +77,6 @@ All variable key names used to extract data from debug launch configurations can
7777
7878The following list outlines the setting names and default values:
7979
80- - ` peripheral-inspector.svdPathConfig ` - Debug configuration key to use to get the SVD path (default ` svdPath ` )
80+ - ` peripheral-inspector.definitionPathConfig ` - Debug configuration key to use to get the SVD path (default ` definitionPath ` )
8181- ` peripheral-inspector.deviceConfig ` - Debug configuration key to use to get the device name (default: ` deviceName ` )
8282- ` peripheral-inspector.processorConfig ` - Debug configuration key to use to get the processor name (default: ` processorName ` )
0 commit comments