You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-32Lines changed: 10 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -397,32 +397,24 @@ application is run with the `> continue` command.
397
397
398
398
This extension contributes additional functionality to work seamlessly with other extensions.
399
399
400
-
- The pseudo debugger types `cmsis-debug-pyocd` and `cmsis-debug-jlink`. These types allow a more seamless
401
-
integration into your IDE. However, these are not full debug adapters but generate debug configurations of
402
-
type `gdbtarget` which comes with the [CDT GDB Debug Adapter Extension](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode).
403
400
- A [debug configuration provider](https://code.visualstudio.com/api/references/vscode-api#DebugConfigurationProvider)
404
401
for the type `gdbtarget` which comes with the [CDT GDB Debug Adapter Extension](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode).
405
402
This provider automatically fills in default values for known remote GDB servers when launching a debug session.
406
403
- CMSIS specific launch configuration items for the `*` debugger type, i.e. visible for all debugger types.
407
404
It depends on the actually used debug adapter type if this information is known and utilized.
408
405
409
-
### Pseudo Debugger Types
406
+
### Debug Configuration Provider
410
407
411
-
This section describes the contributed pseudo debugger types and their support through the contributed debug
412
-
configuration provider for type `gdbtarget`.
408
+
The extension contributes a debug configuration provider which automatically fills gaps in a `gdbtarget`
409
+
debug launch configuration on debug launch. The exact functionality depends on the used `target`>`server`
410
+
value.
413
411
414
-
#### CMSIS Debugger (pyOCD) - `cmsis-debug-pyocd`
415
-
416
-
The `cmsis-debug-pyocd` debugger type is used to add a debug configuration in the
417
-
`launch.json` file for debugging with GDB and pyOCD.
418
-
This configuration uses the `gdbtarget` debugger type registered by the CDT GDB Debug Adapter Extension.
419
-
420
-
Additionally, the extension contributes a debug configuration resolver which automatically fills
421
-
the following gaps during debug launch:
412
+
#### pyOCD
422
413
423
414
- If option `target`>`server` is set to `pyocd`, then it expands to the absolute path of
424
415
the built-in pyOCD distribution.
425
-
- Extends the `target`>`serverParameters` list of `pyocd` command line arguments:
416
+
- If option `target`>`server` contains `pyocd`, then it extends the `target`>`serverParameters` list
417
+
of `pyocd` command line arguments:
426
418
- Prepends `gdbserver` if not present.
427
419
- Appends `--port <gdbserver_port>` if the `target`>`port` setting is set, where `<gdbserver_port>` gets
428
420
that port setting's value.
@@ -432,24 +424,10 @@ the following gaps during debug launch:
432
424
> The built-in version of pyOCD supports the command line option `--cbuild-run` which isn't available
0 commit comments