Tips and Tricks#

This section provides useful information when working with Simplicity Studio 6. This includes:

Reporting an Issue
Placing a Simplicity Studio 6 Project Under Source Control
Gitignore Example
Useful Paths

Reporting an Issue#

Depending on your account type on silabs.com, you can either create a support case or post on the Community Forum to report an issue.

Before posting on the Community Forum, do the following:

Review recent threads.
Search to see if the issue has already been reported.
If the issue has been addressed, any available workarounds will be described in the thread—saving you time.

When creating a new Support Case or Forum Thread, do the following:

Describe the issue clearly.
Include the full text or screenshots of any error messages.
Depending on the type of error, attach relevant log files as described in following sections.
If you're unsure which files to include, include all of them.

Log Files#

This section describes how to find logs and the conditions under which each type is useful.

Use the following table to identify the default home directory on each platform.
Replace the ~ character in the log paths with the appropriate home directory path for your platform.


Platform	Default Home Directory
Windows	`C:\Users\USERNAME`
macOS	`/Users/USERNAME`
Ubuntu	`/home/USERNAME`

Simplicity Installer (SLT) Logs#

Attach the following log files for install / uninstall related issues.

~\.silabs\slt\daemon\daemon.log
~\.silabs\slt\slt.log
~\.silabs\slt\installs\conan\sltconan.log

Simplicity Studio 6 Logs#

Attach the following log files for issues with Simplicity Studio or the configuration or analysis tools.

~\SimplicityStudio\v6_workspace_BUILD_NUMBER\.metadata\log.txt

For example:

~\SimplicityStudio\v6_workspace_130\.metadata\log.txt

~\.silabs\slt\installs\archive\v6-base-VERSION_NUMBER-BUILD_NUMBER\SimplicityStudio-6\configuration\log.txt

For example:

~\.silabs\slt\installs\archive\v6-base-v6.0.0-130\SimplicityStudio-6\configuration\log.txt

Simplicity Device Manager (SDM) Logs#

Attach the following log files for issues detecting parts or otherwise working with debug adapters:

~\.silabs\sdm\sdm.log

~\.silabs\sdm\sdm-service.log*

Hardware Database Logs#

Attach the following log files for issues with parts not found or if the device filtering properties in Studio 6 are incorrect:

~\.silabs\hw-db-service\log.txt ~\.silabs\hw-db-service\sql.txt

VS Code Extension Logs#

Attach the following log file for any issues using the VS Code extension to edit, build, flash, or debug a project.

The VS Code extension log file location can be set with the Silabs: Logging Folder Path setting:

Windows: ~\AppData\Local\Temp\silabs_extension\vscode.log
macOS: Find the path to vscode.log from the VS Code setting mentioned above.
Linux: /tmp/silabs_extension/vscode.log

Placing a Simplicity Studio 6 Project under Source Control#

The following table outlines the various files in a Studio 6 project and indicates whether each should be placed under source control.


File / Folder	Purpose	Place under source control?	Comments
`.slcp`, `.slps`, `.slpb`, `.slcw`, and `.pintool`	Main project metadata configuration files.	Yes
`.projectlinkstore`	Contains shortcuts to highlighted source files or configuration tools.	No	The file will be recreated, and the available shortcuts are tailored to the individual user.
`Config` folder	Contains configuration header files for the installed software components and subfolders for the Advanced Configurator (AC) files. For example, Bluetooth projects may include a `btconf` subfolder with the `gatt_configuration.btconf` and possibly `in_place_ota_dfu.xml` file.	Yes	These files cannot be regenerated; their contents are not stored in the project configuration files (e.g., `slcp`).
`autogen` folder	Contains files generated by the Project Configurator based on the installed software components and the files in the `config` folder. Required to build the project. Recreated during project generation.	Depends on team workflow. If CI builds are performed without Simplicity Studio or slc, these files should be source controlled.
simplicity_sdk_x.y.z	Necessary SDK source files created by the Project Configurator based on the installed components. Recreated during project generation.	Same as `autogen` folder	Files can either be links to actual files in the SDK or copies of the files from the SDK, depending on the import mode of the project.
`vscode.conf` and `vscsolution.conf`	VS Code extension integration files. Provide VS Code with tool version and basic project configuration information. Recreated during project generation.	Same as `autogen` folder
`.vscode` folder, `c_cpp_properties.json`, `settings.json`, and `launch.json`	Files generated by the VS Code extension during a build. The `launch.json` file is created when a debug session starts.	No
`cmake_gcc` folder, `PROJECTNAME.cmake`, `CMakeLists.txt`, `CMakePresets.json`, and `toolchain.cmake`	Folder and files created during Project Configurator generation.	Most files are regenerated and should not be modified.	The `CMakeLists.txt` file is special in that the user can and should make additions to this file for source files, symbols, and settings they add to the project and if that is done then the file should be under source control.
Build output folders under the `cmake_gcc` folder ('build', or a custom build configuration name)	Created when the project is built.	No (unless binary files are required for production).
`artifact`	Files created by the post-build generator	No (unless binary files are required for production).
`README.md`, `*.png`	Project documentation files	No	These files can be updated to share project information. Updated versions should be source controlled.
`trashed_modified_files` folder	Contains configuration files that were modified from default values before the component was removed by user action or an SDK upgrade.	No (unless the user wants to be able to roll back changes independently of source control).

Gitignore example#

A .gitignore file might have this content:

autogen/
simplicity_sdk*/
.projectlinkstore
cmake_gcc/build/
*.cmake
CMakePresets.json
*.conf
.vscode/
artifact/
trashed_modified_files/
*.md
*.png

Useful Paths#

Use the Simplicity Installer Package Manager to view installed packages and to update or uninstall them.

Packages are installed in the user's .silabs folder. They are categorized as either:

Archive packages – ZIP files used for Silicon Labs–produced tools.
Conan packages – Managed by the Conan package manager, typically used for third-party tools such as the GNU ARM toolchain, SDKs, and SDK extensions.

Archive packages are stored in the installs/archive folder, while Conan packages are stored in the installs/conan folder.

Use the following table to identify the default home directory on each platform.
In later sections of this document, replace the ~ character with the appropriate home directory path for your platform.


Platform	Default Home Directory
Windows	`C:\Users\USERNAME`
macOS	`/Users/USERNAME`
Ubuntu	`/home/USERNAME`

Windows#

The following paths are useful when working in the Windows environment:

Root install path for Simplicity Studio 6 and standalone tools:
~\.silabs
Installed packages:
~\.silabs\slt\installs\archive
~\.silabs\slt\installs\conan
Simplicity Installer:
~\AppData\Local\Programs\SimplicityInstaller
Command line installer (slt.exe) installed with Simplicity Installer:
~\AppData\Local\Programs\SimplicityInstaller\resources
Simplicity Commander
“~\.silabs\slt\installs\archive\Simplicity Commander\commander.exe”
Default workspace:
~\SimplicityStudio\v6_workspace
Visual Studio Code “Simplicity Studio for VS Code”
The VS Code extension should be installed and uninstalled through the VS Code Marketplace, the path to it is provided as a convenience.
~\.vscode\extensions\silabs.siliconlabssupportextension-VERSION

MacOS#

The following paths are useful when working in the macOS environment:

Root install path for Simplicity Studio 6 and standalone tools
~/.silabs
Installed packages:
~/.silabs/slt/installs/archive
~/.silabs/slt/installs/conan
Simplicity Installer:
/Applications/SimplicityInstaller/app
Command line installer (slt.exe) installed with Simplicity Installer:
/Applications/SimplicityInstaller/app/Contents/Resources/slt
Simplicity Commander
~/.silabs/slt/installs/archive/Commander.app
Command line version of Simplicity Commander:
~/.silabs/slt/installs/archive/Commander.app/Contents/MacOS/commander
Default workspace:
~\SimplicityStudio\v6_workspace
Visual Studio Code “Simplicity Studio for VS Code”
The VS Code extension should be installed and uninstalled through the VS Code Marketplace, the path to it is provided as a convenience.
~/.vscode/extensions/silabs.siliconlabssupportextension-VERSION

Linux#

The following paths are useful when working in the Linux environment:

Root install path for Simplicity Studio 6 and standalone tools:
~/.silabs
Installed packages:
~/.silabs/slt/installs/archive
~/.silabs/slt/installs/conan
Simplicity Installer:
Located in the directory where the ZIP file was extracted.
Command-line installer (slt.exe) installed with Simplicity Installer:
SimplicityInstaller/Resources/slt
Simplicity Commander
~/.silabs/slt/installs/archive/commander/commander
Default workspace:
~\SimplicityStudio\v6_workspace
Visual Studio Code “Simplicity Studio for VS Code”
The VS Code extension should be installed and uninstalled through the VS Code Marketplace, the path to it is provided as a convenience.
~/.vscode/extensions/silabs.siliconlabssupportextension-VERSION

Conan Packages#

Conan packages are used for SDKs, SDK extensions, and third-party build tools such as gcc and cmake:

Conan Package Names

The previous figure shows the following packages:

AI/ML SDK extension
CMake
GCC toolchain
Matter SDK extension
Ninja
Amazon Sidewalk SDK extension
Simplicity SDK
WiSeConnect SDK extension