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: CHANGELOG.md
+22-2Lines changed: 22 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,26 @@
1
1
# Change Log
2
2
3
-
## [Unreleased]
3
+
## 1.55.1
4
+
5
+
- New features:
6
+
7
+
- The [**Software Components**](https://mdk-packs.github.io/vscode-cmsis-solution-docs/manage_components.html) view has been redesigned and uses the csolution tool
8
+
from the CMSIS-Toolbox included in the extension for consistency with the command line.
9
+
- The [**Manage Solution**](https://mdk-packs.github.io/vscode-cmsis-solution-docs/manage_settings.html) view adds the selection of a debug adapter supported by the
- The selection is stored in the active `*.csolution.yml` as default [`target-set`](https://open-cmsis-pack.github.io/cmsis-toolbox/YML-Input-Format/#target-set) for the active `target-type`.
12
+
- If no `debugger:` is specified for the default `target-set` but the selected board specifies an [on-board debug adapter](https://open-cmsis-pack.github.io/Open-CMSIS-Pack-Spec/main/html/pdsc_boards_pg.html#element_board_debugProbe),
13
+
this information is taken from `.cbuild-run.yml`. and a default `target-set` is used.
14
+
- The **Views and More Actions...** menu available from the [**CMSIS-View**](https://mdk-packs.github.io/vscode-cmsis-solution-docs/debug.html#cmsis-view) has now a **Target information** entry.
15
+
Click [**Target information**](https://mdk-packs.github.io/vscode-cmsis-solution-docs/create_app.html#check-target-information) to display information about the connected hardware.
16
+
17
+
- Info:
18
+
19
+
- The location of `*.cbuild-run.yml` and `*.cbuild.yml` files is now consistently retrieved from the `*.cbuild-idx.yml` file for the commands `getCbuildRunFile` and `getBinaryFile(s)` which used hard-coded paths previously.
20
+
21
+
- Known issues:
22
+
23
+
- Updating `launch.json` and `tasks.json` files does not preserve comments.
4
24
5
25
## 1.54.0
6
26
@@ -13,7 +33,7 @@
13
33
- If a debug adapter is specified by the `*.cbuild-run.yml`, configurations are generated in `launch.json` and `tasks.json` based on the debug adapter templates specified in the [debug adapter registry](https://github.com/Open-CMSIS-Pack/debug-adapter-registry).
14
34
-**Manage Solution** no longer supports the configuration of context specific "Run" and "Debug" actions. Corresponding options are deprecated in the user settings of the workspace.
15
35
-[Device configuration files](https://open-cmsis-pack.github.io/cmsis-toolbox/build-overview/#device-configuration) (*.dbgconf) are moved and renamed. The files can be accessed from group "Device: ..." in **CMSIS-View**.
16
-
36
+
17
37
- Solved issues:
18
38
19
39
- The YAML parser for the CMSIS solution input files ensures that all specified numeric, hexadecimal and boolean
Copy file name to clipboardExpand all lines: README.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,24 @@ The **CMSIS** view gives you access to the source code of your application. The
41
41
42
42
Action buttons allow you to build, run, and debug your application, [edit *csolution project files*](#yml-editor-support) or [manage the solution configuration](#manage-solution-view). The [Configuration Wizard](#configuration-wizard) offers a graphical view to configuration file options.
43
43
44
+
## Action buttons
45
+
46
+
The **CMSIS** view displays the name of the current *csolution project* and offers several action buttons.
| Build / Stop |**Build**: Translate the source code into a application image.<br>**Stop**: Terminate the current build process. |
53
+
| Load & Run / Stop |**Load & Run**: Download application image and start execution. Prepare GDB for target connection.<br>**Stop**: Terminate the current run or debug process. |
54
+
| Load & Run / Attach |**Load & Run**: Download application image and start debugging.<br>**Attach**: Connect debugger to a running application. |
55
+
| Open csolution.yml | Open the csolution.yml project file. |
56
+
|[Manage Solution](#manage-solution-view)| Terminate the current program execution and start debugging again using the current run configuration. |
57
+
| Menu | Offers more options such as [create new solution](#create-solution-view), rebuild, or get info about a connected target system. |
58
+
| Clang active | Activates clang information for one `cproject.yml` part in a multi-project application. |
59
+
| Open csolution.yml | Open the cproject.yml file. |
60
+
|[Select components](#software-components-view)| View and modify the software components used for the application. |
Select a [context set](https://open-cmsis-pack.github.io/cmsis-toolbox/build-overview/#working-with-context-set) from this view. For a given target type, a context set combines related projects which you can build for an application. You might need to use different build types for projects, for example in cases where not all parts of an application require extra debug overhead.
93
+
Select a [target set](https://open-cmsis-pack.github.io/cmsis-toolbox/build-overview/#working-with-context-set) from this view. For a given target type, a target set combines related projects and chooses the debug adapter used for the application. You might need to use different build types for projects, for example in cases where not all parts of an application require extra debug overhead. Refer also to [Run and Debug](#run-and-debug) below.
THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
0 commit comments