@arm-software/vscode-cmsis-csolution - npm Package Versions

Updates:

• The Create Solution dialog is reading board, device and example information from installed packs using the csolution rpc daemon. Now information is also read from CMSIS Packs that are registered via the local_repository.pidx. The CMSIS-Core-Tools have been fully replaced and are therefore no longer distributed as part of the extension.
• Using the CMSIS View [+] button quick pick Add From Component Code Template now shows component instance index specific code templates.

Solved issues:

• Loading a CMSIS solution specifying a target-set without a corresponding *.cbuild-set.yml file present, now displays Software Components and enables the action buttons for Load & Run appliction and Load & Debug application in the CMSIS-View #306 .

Known issues:

• Updating launch.json and tasks.json files does not preserve comments.

Solved issues:

• The CMSIS Context status bar hangs at Loading Solution... during Solution load if a default target-set is not specified and no cbuild-set.yml with a context-set is present. #304

Known issues:

• Updating launch.json and tasks.json files does not preserve comments.

New features:

• CMSIS-View adds PLM status indicators for component configuration files (X)= mandatory file update, (!) = recommended file update and (?) = suggested file update. These indicators are propagated upwards from the configuration file to the project displaying the most severe status. The tooltips to the status indicators provide additional information. When hovering over or selecting a configuration file that needs updating, a merge icon is displayed that can be clicked to open the VSCode 3-way merge editor. When closing the editor the merged file becomes the active configuration file.

Solved issues:

• [Configuration Wizard] when editing a bitfield through the graphical view, no other bitfield values get incorrectly reset. #296
• Removed unintended duplicates of directories from some examples projects downloaded from the Web (https://Keil.arm.com). #99
• The generation of launch.json and task.json do not rewrite the files unless updates are required. This way comments are preserved when not making changes. #295

Known issues:

• Updating launch.json and tasks.json files does not preserve comments.

New features:

• The Software Components view has been redesigned and uses the csolution tool from the CMSIS-Toolbox included in the extension for consistency with the command line.
• The Manage Solution view adds the selection of a debug adapter supported by the Arm CMSIS Debugger extension.
  • The selection is stored in the active *.csolution.yml as default target-set for the active target-type.
  • If no debugger: is specified for the default target-set but the selected board specifies an on-board debug adapter, this information is taken from .cbuild-run.yml. and a default target-set is used.
• The Views and More Actions... menu available from the CMSIS-View has now a Target information entry. Click Target information to display information about the connected hardware.

Solved issues:

• Drop down box search filter handle matches on categories and items

Info:

• 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.

Known issues:

• Updating launch.json and tasks.json files does not preserve comments.

New features:

• New features require CMSIS-Toolbox v2.9.0 or later. Update your workspace's vcpkg-configuration.json file accordingly.
• The CMSIS Solution extension integrates with the Arm CMSIS Debugger extension adding action buttons and commands required for debugging an application.
  • If a target-type specifies the node target-set: cbuild is launched for the active target-set instead of the context-set specified in *.cbuild-set.yml. In addition the selected contexts from Manage Solution dialog are stored in the target-set of the active target-type.
  • 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.
• 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.
• Device configuration files (*.dbgconf) are moved and renamed. The files can be accessed from group "Device: ..." in CMSIS-View.

Solved issues:

• The YAML parser for the CMSIS solution input files ensures that all specified numeric, hexadecimal and boolean values retain their format in full, no quotes are added on write back.

Known issues:

• Updating launch.json and tasks.json files does not preserve comments.

New features:

• The quick picker from the "Select Active Solution from workspace" menu lists available solutions in alphabetical order.

• The Installation of a pack can be initiated via a URI vscode://arm.cmsis-csolution/installpack?pack=<pack> launching VS Code, using the installed CMSIS Solution extension to run cpackget add -a <pack>.

• Solution outline view improvements:

  • A Manage software components button is now available to open the Software Components view also from Components item.
  • Copy header file buttons are available for header files listed under constructed-files or Components adding #include "<header file>" to the clipboard.
  • Set Clangd Context buttons are available at the project level to activate clangd for a given project context.
  • Local files with extension *.md (Markdown format) are opened in the markdown preview mode.

Solved issues:

• Newly created solutions no longer fail due to missing configuration files from selected components because update-rte is now executed.
• Fixed command:cmsis-csolution.getCbuildRunFile to return the filename following the convention <solution>+<target>.cbuild-run.yml introduced in CMSIS-Toolbox 2.8.0.
• Arm Compiler 6 pre-defines are consistently exported into .clangd configuration files.
• Reduce likelihood of duplicated calls to cbuild setup after converting µVision projects within the active workspace.
• The YAML parser for the CMSIS solution input files ensures that all specified numbers retain their format. Double quotes are added on write back without causing any side effect.

Known issues:

• A *.project.yml that has components with for-context attributes might loose settings. (ARM-software/vscode-cmsis-csolution#211).
• Missing source files in *.cgen.yml after generating code in CubeMX. (ARM-software/vscode-cmsis-csolution#206, Open-CMSIS-Pack/generator-bridge#129).

New features:

• The Configuration Wizard supports Debug Configuration Files (*.dbgconf) which, starting with CMSIS-Toolbox 2.8.0, are treated like component configuration files from a Cclass="Device" component.
• Pop-up notification added when launching a generator failed. The CMSIS Solution output channel displays by default.
• Pop-up notification added if a csolution file is detected in the workspace when launching a µVision to CMSIS Solution conversion. You can choose to overwrite the existing csolution file.
• The extension includes the CMSIS Solution schema files from the latest published CMSIS-Toolbox version (2.8.0).
• The extension includes the latest published µVision to CMSIS Solution converter (1.6.0).

Solved issues:

• When adding a local PDSC file using cpackget the <timestamp> tag in local_repository.pidx must not be empty.
• The deprecated CMSIS Solution Extension API version 1.0 was removed. You must now use Version 2.0.
• A full list of resolved issues is available on GitHub.

Known issues:

• When installing a local software pack with cpackget the pack index is updated unnecessarily.

New features:

• The CMSIS View shows the board and device for the active target.
• The CMSIS View provides access to documentation for the board, device, and components.
• The Views and More Actions... menu available from the CMSIS View has now a Help entry. Click Help to open the CMSIS Solution documentation.
• The context help in the editor has been enhanced for csolution project files. Documentation links are provided when you move your mouse over the different elements.

Solved issues:

• The Create Solution view now presents the correct templates from packs.
• A full list of resolved issues is available on GitHub.

Known issues:

• The layers and templates displayed in the Create Solution view are only taken from installed CMSIS software packs.
• Software components from layers of inactive target types incorrectly display in the Software Components view in addition to the ones from the active target type.
• When installing a local software pack with cpackget, (a) an incorrect empty <timestamp> is created, and (b) the pack index is downloaded.

New features:

• This version of the extension is targeted for use with CMSIS-Toolbox 2.7.
• The CMSIS Solution Extension API version 2.0 is available on npm and gives access to all available boards and devices, their associated examples, and the ability to copy and build a selected example for use by other Visual Studio Code extensions.
• Improvements to the CMSIS Solution outline view include: book icons to open documentation for API header files, count badges on components, Add New Group buttons at the project level, and improved default collapse settings.

Solved issues:

• CMSIS solution projects using a yaml file extension are loaded correctly again.
• To access recently published pack versions, you must run cpackget update-index --sparse: Now the pack index is automatically updated by cpackget once a day.
• If you are using CMSIS-Toolbox for the first time, you must manually initialize the CMSIS-Pack root directory with cpackget init https://www.keil.com/pack/index.pidx: Now the CMSIS-Pack root directory is initialized automatically if it does not exist yet.
• After manually installing a CMSIS software pack, this version of the extension re-reads the package description files of the installed CMSIS software packs every time cpackget has added or removed a pack.

Known issues:

• The layers and templates displayed in the Create Solution view are only taken from installed CMSIS software packs.
• Software components from layers of inactive target types incorrectly display in the Software Components view in addition to the ones from the active target type.
• The pack installer updates the pack index even when installing a local CMSIS software pack file.

New features:

• The CMSIS status bar has been enhanced with a busy indicator and shows error and warning messages from CMSIS-Toolbox.
• When the Use Web Services setting is enabled, the Create new solution view uses the internet database in addition to installed packs to display devices, boards, and examples.
• For components, the CMSIS view now supports access to documentation from packs.

Solved issues:

• Software components from layers or generators display in the Software Components view.
• In the Manage Solution view, the issues occurring when changing the context set configuration have now been solved.
• clangd now supports code completion, compile errors, and go-to-definition for all active contexts.

Known issues:

• When using this extension for the first time in combination with the Arm Environment Manager, development tools are pre-installed. While this is happening, "Loading..." displays, which is misleading. You can check how the download process is progressing in View > Output > Arm Tools category.