To get started with Simplicity Studio® 5 (SSv5):

  1. Install SSv5 and development software.
  2. Explore the main features of SSv5.
  3. Start a project.

You do not need hardware to install SSv5 and the relevant software packages or, for 32-bit devices, to explore the project configuration interface for a particular SDK. However, having your target hardware connected during installation ensures that your SSv5 installation is configured precisely for your environment.

You should also have an account set up in the Silicon Labs Customer Support Portal. Access to some software packages is controlled by your customer profile.

See Prerequisites for more information.

New Features

Simplicity Studio® 5 version SV5.0.0.0

The initial release of SSv5 includes the following key features:

Known Issues

Simplicity Studio® 5 version SV5.0.0.0

495086If you have the Component Editor open and you change the Gecko SDK Suite to a version that does not contain that component, when you return to the component editor it will not work properly because the component no longer exists.Close the component editor.
498387If a debug session is started using a WSTK and then the Device Console tool is launched, the console tool works correctly. However if the debug session is ended, then the Device Console cannot be made functional again without restarting SSv5.None
499669, 499661The EmberZNet SDK's dynamic multiprotocol (DMP) sample applications rely on the Micrium OS and Bluetooth SDKs also being installed. If those SDKs are not installed, the DMP sample applications are still presented as options. Attempting to create a DMP sample application may fail, or may appear to complete but subsequently fail to generate because of unresolved dependencies on those SDKs. Subsequently installing those SDKs may not resolve the issues in that existing DMP sample application project.Install the Micrium OS and BLE SDKs before creating an EmberZNet DMP sample application project.
501464Pintool is showing errors for pin selections in modules you are not currently configuring, even if, by selecting a different module, you were expecting any pin assignments previously made to no longer matter.Find the 'Selected Module' that has the pin conflict and set the field to 'None' to remove the conflict.
519744When the Energy Profiler is used, the target part debug module TMS/SWDIO pin is set low by the Jlink shared library. Therefore, an extra 80 uA of current runs through the TMS/SWDIO pullup.None
520104The project shows indexer (semantic) errors.Try unchecking the following in Preferences > C/C++ > Indexer: 1) Index source files not included in the build; 2) index unused headers; and 3) Allow heuristic resolution of includes. Click Apply and Close.
522243Building a project when a Proprietary Radio Configuration or a Bluetooth GATT Configuration contains unsaved changes causes a race condition, which leads to a case where the build picks up the old configuration.Save the configuration before building the project or build the project again.
522660If you change the part using the Overview tab's Change Target/SDK function, the part definition in the created <project>.pintool file does not change.1. Exit SSv5. 2. Delete the <project>.pintool file from the project directory. 3. Start SSv5. On the Overview tab, click Force Generation in the Project Details card.
525212If a project has a space in the name, the Project Configurator Overview tab is empty and no components are listed in the Software Components tab.Use project names without spaces.

For Simplicity Studio 4 Users

If you are transitioning from Simplicity Studio 4 (SSv4) to SSv5, you will see many improvements. Some familiar tasks have changed:

See Migrate from SSv4 for additional information about migrating projects developed with different tools and protocols.