Skip to content

Commit 2cf03f3

Browse files
authored
Prepare 0.0.2 Pre-Release (#72)
* changelog * trademarks --------- Signed-off-by: Jens Reinecke <[email protected]>
1 parent 2445970 commit 2cf03f3

File tree

4 files changed

+41
-32
lines changed

4 files changed

+41
-32
lines changed

CHANGELOG.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,10 @@
11
# Change Log
22

33
## Unreleased
4-
- Implemented [#69](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/69): Bring Debug Console to front during connection.
4+
- Removes [Arm Tools Environment Manager](https://marketplace.visualstudio.com/items?itemName=Arm.environment-manager) from extension pack. Instead, README lists it as one of the recommended extensions to use with the Arm CMSIS Debugger.
5+
- Fixes use of `${workspace}` to `${workspaceFolder}` in default debug configurations.
6+
- Reduces and aligns default `initCommands` lists for pseudo debugger types `cmsis-debug-pyocd` and `cmsis-debug-jlink`.
7+
- Implements [#69](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/69): Bring Debug Console to front during connection.
58

69
## 0.0.1
710
- Initial release of extension pack on GitHub.

DEVELOPMENT.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22

33
## Prerequisites
44

5-
- Install **Visual Studio Code**.
6-
- Install **Node.js** on your machine and ensure it is on your path.
5+
- Install **Visual Studio Code®**.
6+
- Install **Node.js®** on your machine and ensure it is on your path.
77
- The currently recommended version is 20.x (LTS).
88
- Install **Yarn** which is used to build and execute scripts in this repository:
99

@@ -18,15 +18,15 @@ packages become platform-specific, i.e. for on `<target>`.
1818

1919
Supported `<target>`s are:
2020

21-
- win32-x64 (Windows, Intel, x86-64)
22-
- win32-arm64 (Windows, Arm, aarch64)
23-
- linux-x64 (Linux, Intel, x86-64)
21+
- win32-x64 (Windows®, x86-64)
22+
- win32-arm64 (Windows, Arm®, aarch64)
23+
- linux-x64 (Linux, x86-64)
2424
- linux-arm64 (Linux, Arm, aarch64)
25-
- darwin-x64 (MacOS, Intel, x86-64)
26-
- darwin-arm64 (MacOS, Arm, aarch64)
25+
- darwin-x64 (macOS, x86-64)
26+
- darwin-arm64 (macOS, Arm, aarch64)
2727

2828
1. Open a terminal and execute the following command to download NPM dependencies and tools, and
29-
to build the Typescript code:
29+
to build the TypeScript code:
3030

3131
```sh
3232
> yarn
@@ -61,7 +61,7 @@ Supported `<target>`s are:
6161
creates a build dedicated for debug. Additionally, it sets up a watch which detects code
6262
changes and rebuilds them incrementally.
6363
64-
2. Switch to the VS Code `Run and Debug` view.
64+
2. Switch to the VS Code® `Run and Debug` view.
6565
6666
3. Select and run `Desktop Extension`. This launches an extension host that runs this extension.
6767

README.md

Lines changed: 23 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,34 @@
11
[![Maintainability](https://api.codeclimate.com/v1/badges/0f12a7e73736f8bbfb9d/maintainability)](https://codeclimate.com/github/Open-CMSIS-Pack/vscode-cmsis-debugger/maintainability)
22
[![Test Coverage](https://api.codeclimate.com/v1/badges/0f12a7e73736f8bbfb9d/test_coverage)](https://codeclimate.com/github/Open-CMSIS-Pack/vscode-cmsis-debugger/test_coverage)
33

4-
# Arm CMSIS Debugger Extension for Visual Studio Code (In Progress)
4+
# Arm CMSIS Debugger
55

6-
The Arm CMSIS Debugger extension for Visual Studio Code is an extension pack demonstrating how to combine technologies from various open source projects to create a comprehensive debug platform for Arm based IoT solutions.
6+
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.
77

88
Related open source projects are
99

1010
- [Open-CMSIS-Pack](https://www.open-cmsis-pack.org/) of which this extension is part of.
11-
- [Eclipse CDT Cloud](https://eclipse.dev/cdt-cloud/), an open-source project that hosts a number of components and best practices for building customizable web-based C/C++ tools.
12-
- [pyOCD](https://pyocd.io/), a Python based tool and API for debugging, programming, and exploring Arm Cortex microcontrollers.
13-
- [GDB](https://www.sourceware.org/gdb/), the GNU Project debugger.
11+
- [Eclipse® CDT.cloud™](https://eclipse.dev/cdt-cloud/), an open-source project that hosts a number of components and best practices for building customizable web-based C/C++ tools.
12+
- [pyOCD](https://pyocd.io/), a Python based tool and API for debugging, programming, and exploring Arm Cortex® microcontrollers.
13+
- [GDB](https://www.sourceware.org/gdb/), the debugger of the GNU Project.
1414

1515
## The Arm CMSIS Debugger Extension Pack
1616

17-
The Arm CMSIS Debugger extension is actually an [extension pack](https://code.visualstudio.com/api/references/extension-manifest#extension-packs). It allows to install multiple separate extensions together.
17+
The Arm CMSIS Debugger extension is an [extension pack](https://code.visualstudio.com/api/references/extension-manifest#extension-packs). It allows to install multiple separate extensions together.
1818

1919
## Included Extensions
2020

2121
The following extensions are included in this extension pack:
2222

23-
- [CDT GDB Debug Adapter Extension](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode), an Eclipse CDT Cloud extension that supports debugging using gdb and any other debuggers that supports the MI protocol.
24-
- [Memory Inspector](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.memory-inspector), an Eclipse CDT Cloud extension that provides a powerful and configurable memory viewer that works with debug adapters.
25-
- [Peripheral Inspector](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.peripheral-inspector), an Eclipse CDT Cloud extension that provides a CMSIS SVD viewer and works with debug adapters.
23+
- [CDT GDB Debug Adapter Extension](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode), an Eclipse CDT.cloud extension that supports debugging using GDB and any other debuggers that supports the MI protocol.
24+
- [Memory Inspector](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.memory-inspector), an Eclipse CDT.cloud extension that provides a powerful and configurable memory viewer that works with debug adapters.
25+
- [Peripheral Inspector](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.peripheral-inspector), an Eclipse CDT.cloud extension that provides a CMSIS SVD viewer and works with debug adapters.
2626

2727
## Recommended Extensions
2828

2929
We recommend to install the following extensions to simplify the user experience:
3030

31-
- [Arm Tools Environment Manager](https://marketplace.visualstudio.com/items?itemName=Arm.environment-manager), an extension that allows to download, install, and manage software development tools using [Microsoft vcpkg](https://vcpkg.io/en/index.html) artifacts. Use this extension to for example install the `GCC compiler for ARM CPUs` which comes with a GDB variant for Arm CPUs.
31+
- [Arm Tools Environment Manager](https://marketplace.visualstudio.com/items?itemName=Arm.environment-manager), an extension that allows to download, install, and manage software development tools using [Microsoft® Vcpkg](https://vcpkg.io/en/index.html) artifacts. Use this extension to for example install the `GCC compiler for ARM CPUs` which comes with a GDB variant for Arm CPUs.
3232
- [Arm CMSIS Solution](https://marketplace.visualstudio.com/items?itemName=Arm.cmsis-csolution), an extension that is a graphical user interface for csolution projects that use the [CMSIS-Toolbox](https://open-cmsis-pack.github.io/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.
3333

3434
## pyOCD Debug Setup
@@ -45,16 +45,16 @@ We recommend to install the following extensions to simplify the user experience
4545
}
4646
```
4747
48-
## Segger J-Link Debug Setup
48+
## SEGGER® J-LINK® Debug Setup
4949
50-
- Install the latest [J-Link Software and Documentation Pack](https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack) from [Segger](https://www.segger.com/). Ensure all required drivers and host platform specific settings are done.
50+
- Install the latest [J-LINK Software and Documentation Pack](https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack) from [SEGGER](https://www.segger.com/). Ensure all required drivers and host platform specific settings are done.
5151
- Ensure the installation folder is added to your system's `PATH` environment variable. Alternatively, you can add an absolute path to your installation in the debug launch configuration.
5252
5353
## Additional Extension Functionality
5454
5555
This extension contributes additional functionality to more seamlessly integrate the included extensions:
5656
57-
- The pseudo debugger types `cmsis-debug-pyocd` and `cmsis-debug-jlink`. These types allow a more seamless integration into the VS Code IDE. However, these are not full debug adapters but generate debug configurations of type `gdbtarget` which comes with the [CDT GDB Debug Adapter Extension](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode).
57+
- 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](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode).
5858
- A [debug configuration provider](https://code.visualstudio.com/api/references/vscode-api#DebugConfigurationProvider) for the type `gdbtarget` which comes with the [CDT GDB Debug Adapter Extension](https://marketplace.visualstudio.com/items?itemName=eclipse-cdt.cdt-gdb-vscode). This provider automatically fills in default values for known remote GDB servers when launching a debug session.
5959
- 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.
6060
@@ -76,11 +76,11 @@ In addition this extension contributes a debug configuration resolver which auto
7676
7777
**Note**: The built-in version of pyOCD supports the command line option `--cbuild-run`. However, this is a new option which isn't contained yet in releases outside this extension.
7878
79-
#### CMSIS Debugger (J-Link) - `cmsis-debug-jlink`
79+
#### CMSIS Debugger (J-LINK) - `cmsis-debug-jlink`
8080
81-
The `cmsis-debug-jlink` debugger type allows to add default debug configurations to the workspace's `launch.json` file to debug via GDB and the Segger J-Link GDB server. The actually used debugger type is `gdbtarget`.
81+
The `cmsis-debug-jlink` debugger type allows to add default debug configurations to the workspace's `launch.json` file to debug via GDB and the SEGGER J-LINK GDB server. The actually used debugger type is `gdbtarget`.
8282
83-
**Note**: The generated default debug configuration uses `JLinkGDBServer` as `target`.`server` setting. The executable with this name has slightly differing behavior depending on your host platform. It launches a GUI-less server on Linux and MacOS. Whereas a GDB server with GUI is launched on Windows. Please change the value to `JLinkGDBServerCL` to suppress the GUI on Windows.
83+
**Note**: The generated default debug configuration uses `JLinkGDBServer` as `target`.`server` setting. The executable with this name has slightly differing behavior depending on your host platform. It launches a GUI-less server on Linux and macOS. Whereas a GDB server with GUI is launched on Windows®. Please change the value to `JLinkGDBServerCL` to suppress the GUI on Windows.
8484
8585
In addition this extension contributes a debug configuration resolver which automatically fills the following gaps during debug launch:
8686
@@ -94,4 +94,10 @@ In addition this extension contributes a debug configuration resolver which auto
9494
9595
## Trademarks
9696
97-
Visual Studio is a trademark of the Microsoft group of companies.
97+
Arm and Cortex are registered trademarks of Arm Limited (or its subsidiaries or affiliates) in the US and/or elsewhere.<br>
98+
Windows, Visual Studio Code, VS Code, and the Visual Studio Code icon are trademarks of Microsoft Corporation. All rights reserved.<br>
99+
Mac and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions.<br>
100+
Eclipse, CDT, and CDT.cloud are trademarks of Eclipse Foundation, Inc.<br>
101+
SEGGER and J-LINK are registered trademarks of SEGGER Microcontroller GmbH.<br>
102+
Node.js is a registered trademark of the OpenJS Foundation.<br>
103+
GDB and GCC are part of the GNU Project and are maintained by the Free Software Foundation.<br>

package.json

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -98,10 +98,10 @@
9898
},
9999
{
100100
"type": "cmsis-debug-jlink",
101-
"label": "CMSIS Debugger (J-Link)",
101+
"label": "CMSIS Debugger (J-LINK)",
102102
"initialConfigurations": [
103103
{
104-
"name": "CMSIS Debugger: J-Link",
104+
"name": "CMSIS Debugger: J-LINK",
105105
"type": "gdbtarget",
106106
"request": "launch",
107107
"cwd": "${workspaceFolder}",
@@ -133,10 +133,10 @@
133133
],
134134
"configurationSnippets": [
135135
{
136-
"label": "CMSIS Debugger: J-Link",
137-
"description": "CMSIS Debugger via J-Link GDB adapter.",
136+
"label": "CMSIS Debugger: J-LINK",
137+
"description": "CMSIS Debugger via J-LINK GDB adapter.",
138138
"body": {
139-
"name": "CMSIS Debugger: J-Link",
139+
"name": "CMSIS Debugger: J-LINK",
140140
"type": "gdbtarget",
141141
"request": "launch",
142142
"cwd": "^\"\\${workspaceFolder}\"",

0 commit comments

Comments
 (0)