Explore the VS Code Extension#

Silabs Quick Access#

This view provides quick access to main extension functionalities from the default VS Code Explorer view.

1. Silabs quick access view.

2. Shortcut to extension walkthrough on how to get started with the extension.

3. Refresh view.

4. Show more options.

   

Show more actions:

1. Welcome content, which is the same as the Walkthrough.

2. Shortcut to extension's settings.

3. Show external links to docs.silabs.com.

   

After opening a compatible project folder. (Simplicity Studio generated project is considered compatible, if its generator list contains "Visual Studio Code").

1. Opened project.

2. Build.

   • If multiple build configurations are present for a given project, before building, you will be asked to select one build configuration. If a build is a success, and binary files were generated, the configuration will be displayed under the project.

3. Shortcut to Build Configurator. For more information, check the corresponding section of this document.

   

Successfully built configuration under the project.

1. Expand the configuration.

2. Flash.

   1. Before Flash is executed, you will be asked to choose a binary file to flash. This can be: .hex, .bin, or .rsp. For binaries that do not contain address information, for example .bin, you should add a starting memory address as well.

   2. In case multiple compatible devices [see settings: Board display] are connected, choose one.

3. Debug.

   1. If multiple compatible devices [see settings: Board display] are connected, choose one.

   2. Successful start of the debug section will navigate you to the "Run and Debug" view.

   3. When Debug is launched, a "launch.json" file will be created/updated in the ".vscode" folder with information about the Silabs debug session. If you have your own launch.json file and want to keep it, the corresponding setting should be turned off [Overwrite launch file].

   

Status Bar#

Once a file from opened project is selected in VS Code explorer, shortcuts to build, flash and debug are displayed in the status bar. With the project name that contains the selected file.

1. File selected in Explorer.

2. Shortcuts to build, flash and debug.

   • These can be initiated by one or more additional input steps depending on the number of opened projects and the number of connected devices.

     

Workspace#

The following describes the Silicon Labs Workspace within VS Code.

1. Silicon Labs view.

2. Shortcut to extension walkthrough on how to get started with the extension.

3. Refresh workspace.

4. Connect to Simplicity Studio Workspace.

5. Shortcut to extension's settings.

   

Connecting and selecting previous workspaces:

1. Connect to Simplicity Studio Workspace.

2. Previously connected workspaces.

   1. Selecting one will automatically load the folder content into the workspace view.

   2. List can be edited under settings [V5 workspaces].

   3. Important: Only projects and solution generated with "Visual Studio Code" generator will be displayed.

3. Browse button to browse folders for a new workspace.

   • Selecting one will automatically load the folder content into the workspace view

     

Workspace details:

1. Badge in the left rail.

   1. Number shows how many "notifications" are waiting.

   2. These are listed in the tooltip when you hover over the Si icon.

2. Tooltip displaying if the workspace had changes.

3. Refresh to update the Workspace content.

For a displayed project, the following actions are available:

1. Build.

   • If multiple build configurations are present for a given project, before building, you will be asked to select one build configuration.

2. Flash.

   1. Before Flash is executed, you will be asked to choose a binary file to flash. This can be: .hex, .bin, or .rsp. For binaries that do not contain address information, for example .bin, you should add a starting memory address as well.

   2. In case multiple compatible devices [see settings: Board display] are connected, you should choose one.

3. Debug.

   1. In case multiple compatible devices [see settings: Board display] are connected, you should choose one.

   2. Successful start of the debug section will navigate you to the Run and Debug view.

   3. When Debug is launched, a launch.json file is created/updated in the .vscode folder with information about the Silicon Labs debug session. If you have your own launch.json file and want to keep it, the corresponding setting should be turned off [Overwrite launch file].

   4. Shortcut to 04-Build-Configurator#build-configurator. For more information, check the corresponding section of this document.

      

For a displayed solution the following actions are available:

1. Build.

   • In this version only, one build configuration is available for solution.

2. Flash.

   1. Before Flash is executed, you will be asked to choose a binary file to flash.

   2. In case multiple compatible devices [see settings: Board display] are connected, you should choose one.

3. Debug.

   1. In case multiple compatible devices [see settings: Board display] are connected, you should choose one.

   2. Successful start of the debug section will navigate you to the Run and Debug view.

   3. When Debug is launched, a launch.json file is be created/updated in the .vscode folder with information about the Silicon Labs debug session. If you have your own launch.json file and want to keep it, the corresponding setting should be turned off [Overwrite launch file].

      

Right click on folder brings up a context menu with the following actions:

1. Add new file or folder to the selected folder.

   1. When you choose this, an additional input dialog is displayed.

   2. If text input contains a file extension, a file will be created; otherwise a folder will be added.

   3. Folder or file cannot be added to the top level folder of a solution

2. Rename selected folder.

   1. Projects and solutions cannot be renamed only in Simplicity Studio.

   2. Sub-projects of a solutions can only be renamed in Simplicity Studio.

   3. Renaming a Simplicity Studio generated folder may cause the project to malfunction.

3. Delete selected folder.

   1. Projects and solutions can only be deleted in Simplicity Studio.

   2. Sub-projects of a solutions can only be deleted in Simplicity Studio.

   3. Deleting a Simplicity Studio generated folder may cause the project to malfunction.

      

Right click a file to open a context menu with the following actions:

1. Rename selected file.

   • Renaming a Simplicity Studio generated file may cause the project to malfunction.

2. Delete selected file.

   • Deleting a Simplicity Studio generated file may cause the project to malfunction.

3. Some configuration files that have a configurator in Simplicity Studio have this optional action. Selecting this action will open the selected configuration file in its own configurator.

4. Show the selected file in VSC Explorer by moving the focus to the selected file in the VSC Explorer view.