Οδηγός χρήστη λογισμικού SILICON LABS Simplicity Studio 5

Περιεχόμενα κρύβω

1 SILICON LABS Simplicity Studio 5 Software

2 Προδιαγραφές

3 Οδηγίες χρήσης προϊόντος

4 Συχνές ερωτήσεις

5 Έγγραφα / Πόροι

5.1 Αναφορές

SILICON LABS Simplicity Studio 5 Software

Προδιαγραφές

Όνομα προϊόντος: Project Configurator
Συστατικά: Editor, Pin Tool, Bluetooth GATT Configurator, Bluetooth Mesh Configurator, Proprietary Radio Configurator, Wi-SUN Configurator, ZCL Advanced Platform Solutions, Memory Editor, Project Retargeting

Οδηγίες χρήσης προϊόντος

Υπερview of Project Configurator
- Project Configurator is a tool that automatically opens an OVERVIEW tab when creating a component-based project (.slcp) in the Simplicity IDE perspective. It provides access to software components, configuration functions, and project-specific tools.
Using the OVERVIEW Αυτί
- Το OVERVIEW tab contains three cards:
  - Target and Tool Settings: Change development target, SDK, and project generators.
  - Λεπτομέρειες έργου: Rename project, change Import mode, force generation.
  - Γρήγοροι σύνδεσμοι: Change generated files for the project.
Target and Tool Settings
- Click on Change Target/SDK/Generators to modify the device, SDK version, and generated files for the project. Remember to save changes for them to apply.
Λεπτομέρειες Έργου
- Edit project name, import mode, generate a project report, or force project generation in this section based on project requirements.
Additional Information on Project Configurator
- You can search for target hardware by part number and select different Gecko SDK Suite versions. The options for generated files include GCC Makefile, Visual Studio Code Compatible Project (Beta), IAR Embedded Workbench Project, and Simplicity IDE project. The available options depend on the selected SDK and toolchain.
- Note that changing the project generator does not alter theproject toolchain. Configure the compiler/toolchain in Project > Build Configurations and the default IDE in Preferences > Simplicity Studio > Preferred IDE.

Συχνές ερωτήσεις

Q: How do I open the Project Configurator for an existing project?

A: Double-click the .slcp file in the Project Explorer view to open the Project Configurator.

Q: Can I change between different SDK protocols within the same GSDK version?

A: No, you can only choose among different GSDK versions if you have multiple SDK protocols installed in the same GSDK version.

“`

View Fullscreen

Developing with Project Configurator
Developing with Project Configurator
Υπερview Project Configurator Component Editor Pin Tool Bluetooth GATT Configurator Bluetooth Mesh Configurator Proprietary Radio Configurator Wi-SUN Configurator ZCL Advanced Platform Solutions Memory Editor Project Retargeting

1/46

Developing with Project Configurator
Developing with Project Configurator
Developing with Project Configurator
Simplicity Studio® 5 (SSv5) introduced new and improved tools for configuring project code, designed to work on the project’s component-based architecture. SSv5 includes project configuration tools that provide an enhanced level of software component discoverability, configurability, and dependency management. These include:
Project Configurator to install and uninstall components, Component Editor to change component parameters, Pin Tool to configure peripherals. Other tools are protocol-specific: For Bluetooth and Bluetooth Mesh projects, use the Bluetooth GATT Configurator to customize the Bluetooth GATT database. For Bluetooth Mesh projects, use the Bluetooth Mesh Configurator to customize a node’s Device Configuration Data (DCD). For Proprietary RAIL projects, use the Radio Configurator to define and manage proprietary radio protocols and channel groups For Wi-SUN projects, use the Wi-SUN Configurator to configure application settings, security, and radio. For Zigbee and Matter projects, use the ZCL Advanced Platform (ZAP) to manage and configure endpoints. Once you have finishing customizing your project, build and flash it and test and debug it. Beginning with Simplicity Studio 5.3, you can combine projects into solutions. Solutions can be built, debugged, and flashed together.

2/46

Project Configurator
Project Configurator
Project Configurator
When you create a component-based project (.slcp), the Project Configurator automatically opens an OVERVIEW tab in the Editor area of the Simplicity IDE perspective. A SOFTWARE COMPONENTS tab provides access to a library of software components and their configuration functions. A CONFIGURATION TOOLS tab allows for quick access to project-specific tools. Open the Project Configurator for an existing project by double-clicking the <project>.slcp file in the Project Explorer view.

Υπερview Αυτί
Το OVERVIEW tab has three cards:
Target and Tool Settings, where you can change your development target, SDK, and project generators. Project Details, where you can rename the project, change the Import mode and, in rare cases, force generation. Quick Links, where you can change the files SSv5 generates for your project.
Target and Tool Settings
Click Change Target/SDK/Generators to change the device for which the project is developed, the SDK version to be used in development, or the files that will be generated for the project. Changes made here do not apply to the project until you save changes.

3/46

Project Configurator
Αναζήτηση για target hardware by part number. If you select a different part, it replaces the part already selected, or you can delete the part and then add a new one. If you have more than one Gecko SDK Suite (GSDK) version installed, you can select it here. If you do not see a version that you expect to see, click Manage SDKs to open the SDK Preferences.

4/46

Project Configurator
Here you can search for SDKs that might be installed outside of SSv5. Note that, if you have more than one SDK protocol installed in the same GSDK version, for example Bluetooth and Zigbee, you cannot change between them. You can only choose among GSDK versions.
The options for the files that are generated by Project Configurator are:
GCC Makefile Visual Studio Code Compatible Project (Beta) IAR Embedded Workbench Project Simplicity IDE project
The options that are available for selection and the default vary depending on the SDK and toolchain you selected when you created the project.
Note that changing the project generator does not change the project toolchain. The compiler / toolchain used by Simplicity IDE is configurable in Project > Build Configurations. The default IDE is configurable in Preferences > Simplicity Studio > Preferred IDE.
Λεπτομέρειες Έργου
Project details include a description of the example on which the project is based, the category of the example, the versions of SDK included in the currently selected GSDK version, and the import mode. Here you can:
Edit the project name Change the import mode Generate a project report (If necessary) Force project generation

Click the pen icon to edit the project name.
The import mode determines what resources are copied into your project and what are linked. If you change the import mode, the change is autosaved and your project files are regenerated.
Link to sources means all project and SDK resources are linked. Only generated files are saved with the project.

5/46

Project Configurator Link SDK and copy project sources (default) means that all the example project sources are copied, but SDK libraries are linked. If you update the SDK and regenerate the project files, the project will change. Copy contents means that all resources are copied with the project. You can update SDK or load an updated example project and your project will not change.
Generate Project Report creates a PDF, available through a link immediately above the control, that provides details on: Target hardware device Target hardware device pin mapping Target SDK Software extensions used in the build Installed application, utility, and platform software components
Force Generation, available through the … menu, is used only in rare cases when autogeneration is not triggered, usually because of some change made outside of SSv5. It will run all available generators (slcp, radio config, gatt, and so on). Note for Simplicity Studio 4/AppBuilder users: Because many project configurator files are autogenerated, Project Configurator does not include a Generate control like the one in AppBuilder. Force Generation is not a replacement for that control.
Γρήγοροι Σύνδεσμοι
Quick links are shortcuts to tools and other information of interest while developing a project of this type. The links available vary based on the protocol and device. For example, a Connect project includes a Radio Configurator quick link.

6/46

Project Configurator
Software Components Tab
Projects are configured by installing and uninstalling components, and configuring installed components. The SOFTWARE COMPONENTS tab displays categories of components on the left, and details about the selected component on the right.

A number of filters as well as a keyword search are available to help you explore the various component categories. Note that components for all installed SDKs are presented. Expand a component categorysubcategory to see individual components. Select a component to see its details. Components that were included in the original project or installed by the user are checked (1), and can be uninstalled. Configurable components are indicated by a gear symbol (2). Configurable components must be installed before their configuration can be changed.

7/46

Project Configurator

For any component you can see see the components on which this component depends, and components dependent on it. You can also link to additional documentation, if available.
When you install a component, the installation process will:
1. Copy the corresponding SDK files from the SDK folder into the project folder. 2. Copy all the dependencies of the given component into the project folder. 3. Add new include directories to the project settings. 4. Copy the configurations files into the /config folder. 5. Modify the corresponding auto-generated files (in the autogen folder) to integrate the component into the application.
Additionally, “init” type software components will implement the initialization code for a given component, utilizing their corresponding configuration file as input. Some software components will fully integrate into the application to perform a specific task without the need of any additional code, while other components provide an API to be used in the application.
Configuration Tools Tab
This tab provides an easy way to open a tool when the tool’s tab is not open. The tab shows configuration tools relevant to the project type. A Bluetooth Mesh project shows a number of tools, while an OpenThread project might only show the Pin Tool. Click Open on the tool’s card to open it in a separate tab.

8/46

Project Configurator

9/46

Component Editor
Component Editor
Component Editor
Click the gear symbol next to an installed configurable component name, or Configure on the component description to open the Component Editor.

The Component Editor opens in a new tab. The changes you can make depend on the component.

10/46

Component Editor
Κλικ View Source to open an editor on the configuration file. If a component has multiple configuration files, the control is View Πηγή Files

11/46

Εργαλείο καρφίτσας
Εργαλείο καρφίτσας
Εργαλείο καρφίτσας
Simplicity Studio® 5 (SSv5) offers a Pin tool that allows you to easily configure new peripherals or change the properties of existing ones. In the Project Configurator, open the CONFIGURATION TOOLS tab and open the Pin Tool. Alternatively, doubleclick the file <project>.pintool in the Project Explorer view. The graphical view differs based on the chip.

For more complex layouts, you can use the zoom controls above the graphic to see detail and the rotate controls to rotate the image.

12/46

Εργαλείο καρφίτσας

Right-click anywhere on the image or click the Additional Functions icon in the upper right of the image to open a menu where you can:
Save Diagram as Picture: Saves the graphic as a .png file Module Configuration Report: Produces an .htm file showing modules with signals assigned to pins. If a module has a signal assigned to a pin, the module and signal/pin assignment appear in the report. Pin Configuration Report: Produces an .htm file showing all the user modifiable pins of the chip and the current signal assignment, if any.
Click a pin on the graphic to select it. The corresponding row is checked in the right pane’s tabbed interface.
The pin, function, and peripheral tabs in the configuration pane provide different modes of access. A search function also provided

13/46

Εργαλείο καρφίτσας

14/46

Εργαλείο καρφίτσας

Modifying Pin Configurations
Use the Pin Tool to modify the pin configuration of the device. Software components control behavior in the project but must be associated with a peripheral, and generally need pin or function assignments. These pin or function assignments are most easily edited in the Component Editor for that component. The Pin Tool allows you to assign functions to pins. On all three dialogs, click EDIT next to a software component to go directly to the Component Editor for that component. Click NEW to go to the Project Configurator’s SOFTWARE COMPONENTS tab, where you can install a component in the project so that it can be selected in the dialog.
When you are finished with the configuration, click APPLY or APPLY AND CLOSE to save changes. Configuration code changes are automatically generated.
The Pins Tab
Click on any pin’s row to open the Edit Pin dialog.
The function assigned to the pin: To apply a function or change a function, drop down the function list and select. The Custom Pin Name (optional): Add or edit the custom pin name. The Software Component: The component associated with the function is shown.

15/46

Εργαλείο καρφίτσας

The Functions Tab
Click on any function’s row to open the Edit Function dialog.
The pin to which the function is assigned: Select a pin, or disable. The Custom Pin Name (optional): Add or edit the custom pin name. The Software Component: The component associated with the function is shown. A pin must be selected.

The Peripherals Tab
Click on any peripheral’s row to open the Edit Peripherals dialog. The Custom Peripheral Name: Add or edit the custom peripheral name. The Software Component: The component associated with the peripheral.
Πνευματικά δικαιώματα © 2025 Silicon Laboratories. Με την επιφύλαξη παντός δικαιώματος.

16/46

Εργαλείο καρφίτσας

17/46

Bluetooth GATT Configurator
Bluetooth GATT Configurator
Bluetooth GATT Configurator
The Simplicity Studio® 5 (SSv5) Bluetooth GATT Configurator is a simple-to-use tool to help build a customized Bluetooth GATT database for Bluetooth projects. It is accessed through the Advanced Configurators software component group on the Project Configurator SOFTWARE COMPONENTS tab, or by double-clicking the project file config > btconf > gatt_configuration.btconf. The Bluetooth GATT Configurator is composed of a Custom GATT editor on the left, showing a list of project Profiles/Services/Characteristics/Descriptors, and a Settings editor on the right. A SIG selector allows you to add standard elements to the profile. An options menu is provided at the top of the Custom GATT editor. The Custom GATT editor is always visible, and the Settings editor opens by default.

The Bluetooth GATT Configurator menu is:
1. Add an item. 2. Duplicate the selected item. 3. Move the selected item up. 4. Move the selected item down. 5. Import a Bluetooth GATT database. 6. Add Predefined (opens the SIG editor). 7. Delete the selected item.
Πνευματικά δικαιώματα © 2025 Silicon Laboratories. Με την επιφύλαξη παντός δικαιώματος.

18/46

Bluetooth GATT Configurator
SIG Selector
Click the Add Predefined menu button (6) to open the SIG selector. The SIG Selector displays a list of predefined Profiles, Services, Characteristics, and Descriptors. These items can be filtered, using the filter pane. Tabs allow you to switch between different lists. As shown in the following figure, the pane on the right side of the list displays textual information about the latest selection. To add an item to the Custom GATT editor, mouse over it and click + on the right. The item can then be edited in the Settings section. The selected SIG service/characteristic/descriptor will be added under the highlighted profile/service/characteristic. Click < BACK to return to the Setting Editor. Click View Manual to see more information about Bluetooth GATT database items.
The GATT Configurator does not automatically save changes. An asterisk next to the configuration file name indicates unsaved changes in the configuration. Database generation happens automatically when the configuration is saved. The generated source files can be found in the autogen directory:

19/46

Bluetooth GATT Configurator
Custom GATT Editor
The Custom GATT Editor in the right pane of the GATT Configurator displays the items present in the current configuration file. This includes a Custom GATT Profile, Services, Characteristics, and Descriptors displayed as a hierarchical list. The order of items shown reflects the order in which they exist in the GATT database. When the Settings Editor is open, you can select an item to see its properties and configuration.

Note: The Generic Attribute Service is not listed in the Custom GATT database structure. This is a special service that is maintained by the stack, and can be added by enabling the Generic Attribute Service slider in the settings of the Custom BLE GATT profile. Once enabled, the service will be part of the database. It still will not appear in the Custom GATT database structure or on iOS devices, as iOS hides this service, but you may see it on Android devices for example.

Some services are listed in the configurator as “contributed items”. This means that their content is defined in other components, and they cannot be edited from this view.
Settings Editor
The Settings editor allows you to configure the properties of items such as Profiles, Services, Characteristics and Descriptors that are present in the Custom GATT editor. Selecting an item populates the relevant configuration options such as the name, ID, properties and capabilities. Any changes made in this section are reflected immediately for the selected item. You can minimize the Custom GATT editor while working in the Settings editor, as shown in the following figure. All Characteristics for a Service are included in the same Settings editor pane.

20/46

Bluetooth GATT Configurator
Πρόσθετες Πληροφορίες
For more information on specific use cases in the GATT Configurator, see UG438: GATT Configurator User’s Guide in Bluetooth SDK 3.x.

21/46

Bluetooth Mesh Configurator
Bluetooth Mesh Configurator
Bluetooth Mesh Configurator
The Bluetooth Mesh Configurator provides access to a Bluetooth Mesh node’s Device Composition Data (DCD). This contains information about the elements it includes and the supported models. DCD exposes the node information to a configuration client so that it knows the potential functionalities the node supports and, based on that, can configure the node. Configuring DCD through the Bluetooth Mesh Configurator is only one part of configuring a Bluetooth Mesh node. For details see UG472: Bluetooth® Mesh Node Configurator User’s Guide for SDK v2.x. When you create a Bluetooth Mesh project in Simplicity Studio 5, three tabs open automatically: the GATT Configurator (gatt_configuration.btconf), .the slcp or Project Configurator <projectname>.slcp, and the Bluetooth Mesh Configurator (dcd_config.btmeshconf). If the example has documentation, the project opens on a readme tab.
Click the dcd_config.btmeshconf tab to open the Bluetooth Mesh Configurator. If the tab is closed, you can open it from the Project Configurator’s CONFIGURATION TOOLS tab. The Device Composition Data is presented in three areas: device information, elements, and models.

Πληροφορίες συσκευής
The device information card contains four fields. Changing the Company changes the next three fields.
Πνευματικά δικαιώματα © 2025 Silicon Laboratories. Με την επιφύλαξη παντός δικαιώματος.

22/46

Bluetooth Mesh Configurator
Device configuration information includes: Company: Selected from a list of company names. Company ID: 16-bit company identifier assigned by the Bluetooth SIG. A list of companies and their identifiers may be found on the Bluetooth SIG site. Product ID: 16-bit vendor-assigned product identifier, vendor-specific. Version Number: 16-bit vendor-assigned product version identifier, vendor-specific.
Στοιχεία
An element is an addressable entity within a node. Each node can have one or more elements, the first called the primary element and the others called secondary elements. Each element is assigned a unicast address during provisioning so that it can be used to identify which node is transmitting or receiving a message. The primary element is addressed using the first unicast address assigned to the node, and the secondary elements are addressed using the subsequent addresses. Both primary and secondary elements have a dedicated card, such as that shown in the following figure, through which they can be configured. Click the green plus symbol to add an element or select an element and click the red X symbol to remove it.

Μοντέλα

23/46

Bluetooth Mesh Configurator
A model defines the basic functionality of a node, and a node may include multiple models. A model defines the required states, the messages that act upon those states, and any associated behaviors.
Models may be defined and adopted by the Bluetooth SIG and may also be defined by vendors. Models defined by the Bluetooth SIG are known as SIG-adopted models, and models defined by vendors are known as vendor models. SIG-adopted models are identified by a 16-bit model identifier and vendor models are identified by a 16-bit vendor identifier and a 16-bit model identifier.
Model specifications are designed to be very small and self-contained. At specification definition time, a model can require other models that must also be instantiated within the same node. This is called extending, which means a model adds functionality on top of other models.
Models that do not extend other models are referred to as root models. Model specifications are immutable. In other words, it is not possible to remove or add behavior to a model, whether the desired behavior is optional behavior or mandatory. Models are not versioned and have no feature bits. If additional behavior is required in a model, then a new extended model is defined that exposes the required behavior and can be implemented alongside the original model.
Therefore, knowledge of the models supported by an element determines the exact behavior exposed by that element.
The Bluetooth Mesh Configurator supports configuring both SIG-adopted models and vendor models through separate editors.
SIG-Adopted Model Editor
If you are using the provided model components that automatically bring in the source/header files, libraries, and configurations to the project, and also contribute the model to the DCD, you cannot edit or delete the model from the DCD manually. The model is greyed out, as shown in the following figure. In this case, all the model implementations will be generated to the project. You can modify the callbacks to adjust the application to your use case.

The drawback to using components is that you cannot edit the DCD and model information, because the models added by components are greyed out. If you want to build the DCD from scratch, for example to add a specific model to an element, uninstall all the model components. Then you can edit the DCD manually.
To delete a model, select it and click the red X symbol. To add a SIG-adopted model, drag the model from the left model pool to the SIG Models table in the correct element. A list of all the SIG-adopted models is displayed, and you can choose the one you want, as shown in the following figure. Note that, although all the SIG-adopted models are listed, not all of them are currently supported by the Bluetooth Mesh SDK. For the information on the supported models, see the SDK release notes.

24/46

Bluetooth Mesh Configurator

Due to the extension mechanism of models mentioned above, attention is needed when adding models to your project. See UG472: Bluetooth® Mesh Node Configurator User’s Guide for SDK v2.x for more information.
Vendor Models Editor
Vendor models give you more flexibility when developing products not covered by the SIG-adopted models. Vendors can define their own specification in these vendor models, including states, messages, and the associated behaviors. The vendor model editor is shown in the following figure. The ID field contains the 32-bit vendor identifier and model identifier. The two least significant bytes of the ID are the vendor ID and the two most significant bytes are the model ID. In the following figure, 0x02FF is the vendor ID for Silicon Labs, and 0x0021 and 0x0022 is the model ID. Click the plus symbol to add a vendor model, or select a model and click the red X symbol to remove it.

25/46

Proprietary Radio Configurator
Proprietary Radio Configurator
Proprietary Radio Configurator
The Simplicity Studio® 5 (SSv5) Radio Configurator is provided as part of the Proprietary SDK. Use the Radio Configurator to create standard or custom radio configurations for your RAIL-based radio applications. The Radio Configurator is accessed through the through the Platform group’s Custom Radio Configuration for simple rail singlephy application component, on the Project Configurator SOFTWARE COMPONENTS tab and can be accessed on the CONFIGURATION TOOLS tab. (For some examples, the Radio Configurator might open on project creation). All radio configurator settings are stored in config/rail/radio_settings.radioconf. Changes made with Radio Configurator are not automatically saved.

All the parameters in the Radio Configurator are arranged in cards, some of which are grouped together. Each card contains entries that logically go together. Different radio profiles (as described under Protocol) offer different views and parameter sets, as a profile is a high-level view of the parameter set valid for and describing a given radio link.

26/46

Proprietary Radio Configurator

A radio configuration has two hierarchical levels: Protocol level and Channel Group level. A radio configuration can contain multiple protocols and a protocol can have multiple channel groups defined.
Πρωτόκολλο
Protocols are complete radio configurations that can be switched using the RAIL_ConfigChannels() API, or can be used in Dynamic Multiprotocol applications. For Channel Group definitions see Channel Groups.
To configure a protocol, first select a predefined PHY configuration, then customize it to meet your needs.
First, look at the General Settings card. Select a radio profile in the Select radio profile drop-down menu. A radio profile may be any supported radio link technology. These technologies can be bound by standards (for example the Sigfox or WMBus protocols) or can be fully customized. The fully customizable profile is called the “Base Profile".
Once the radio profile has been selected, the next step is to select a radio PHY (radio configuration) in the Select a radio PHY dropdown list. Each profile has “built-in” configurations ready to use.
Once the radio profile and radio PHY have been selected, users can review ο επαγγελματίαςfile options. By default, no changes are allowed, fields are grayed out. To enable customization, use the Customized switch on the General Settings card. This allows access to all the parameters defined by the profile.

27/46

Proprietary Radio Configurator

Σημαντικές σημειώσεις:
1. If you select a “built-in” PHY, and then switch to “Customized”, the Radio Configurator retains the property values of the “built-in” PHY. You can edit the values, but can also revert to the defaults.
2. If you switch to <Customized= mode, Silicon Labs recommends unchecking all “Advanced” properties, as those are fine-tuned for the “built-in” PHY, and may not be the optimal choice for the modified PHY. This way those parameters get auto-calculated, and you can experiment with the fine tuning starting with the calculated values. To keep the improved performance achieved by the original optimization, only minor changes should be made. For example, <100 MHz change in carrier frequency, or a different frame length configuration.
3. If you switch customization off, your modifications will be reverted to the property values of the “built-in” PHY. 4. Each menu item in the Navigation pane (on the left) is represented by a card in the main editor panel (on the right). Cards can be
hidden by clicking the corresponding “eye” icon on the Navigation panel.
Based on the selected radio profile, customizable options may be restricted. For example, if a radio profile is selected that is bound by a standard, the profile options only allow users to set the base frequency. All other options are preset according to the standard.
Ομάδες καναλιών
Each protocol configuration includes one or more channel group configurations. Channel groups define one or more (sequential) channels, with a constant channel spacing between them. Channel groups can differ in the radio configuration both from each other and from the parent protocol. By default, a channel group configuration includes only the General Settings and Channel Configuration cards. Additional parameters defined by the Protocol can be accessed for customization on a channel group basis by sliding the Customized switch on the corresponding card. Channel groups can also be completely overridden to a predefined PHY by checking the Select radio PHY box.

28/46

Proprietary Radio Configurator

RAIL automatically detects when hopping to a new channel requires hopping between channel groups. The configured property values defined by the channel group will be applied automatically for the new channel. This enables users to define virtual channels to the same physical frequency, but with different configuration settings.
The order of the channel groups will be the same in the RAIL_ChannelConfigEntry_t array as shown in the Radio Configurator. Channel group order can be used to override channels in channel groups, as RAIL will always load the channel from the first channel group in which it is defined.
For more on Multi-PHY configuration, see the example in AN1253: EFR32 Radio Configurator Guide for Simplicity Studio 5.
Finalizing a Configuration
When a parameter is modified from its pre-loaded value, small pictograms show up next to the property field on the card. These pictograms symbolize the differences against the originally selected PHY configurations. A “C” means a difference from the original Channel Group property, and a “P” means a difference from the original Protocol Configuration.

Each input field has an Information icon next to it, which opens the embedded version of AN1253: EFR32 Radio Configurator Guide for Simplicity Studio 5 at the relevant section. You can also reach the documentation by clicking View Manual in the top right corner of the perspective.

29/46

Proprietary Radio Configurator
On save the Radio Configurator generates rail_config.c and rail_config.h in the project’s autogen directory. These files are also generated when a project is created.

30/46

Wi-SUN Configurator
Wi-SUN Configurator
Wi-SUN Configurator
When you create a new Wi-SUN project, a Wi-SUN Configurator is added to it by default. The Wi-SUN Configurator provides an interface to the Wi-SUN application’s main settings through three panels: Application, Security, and Radio. For some examples, the Wi-SUN Configurator only displays the Radio panel. These examples do not have the application and security infrastructure. The Wi-SUN Configurator tab can be displayed by opening /config/wisun/wisun_settings.wisunconf. For more information, click View Εγχειρίδιο.
Πίνακας εφαρμογή
The Application panel exposes multiple Wi-SUN stack settings associated with the application, such as: The network name the device will try to connect to The network size setting The device’s TX output power The unicast dwell interval

The MAC address filtering feature provides a way to force a topology on a Wi-SUN network. It is a simpler alternative to spacing out the Wi-SUN devices to achieve the desired topology. A device either does or does not interact with other Wi-SUN devices on the list, depending on the allow/deny option.
Πίνακας Ασφαλείας
The Security panel displays the private key and certificates used by the device to authenticate itself when connecting to a Wi-SUN network. By default, it uses the Silicon Labs demonstration samples. They can be modified to use a distinct certificate infrastructure aligned with the border router or authenticator certificate.

31/46

Wi-SUN Configurator

Radio Panel
The Radio panel is an interface to configure the radio profiles included in a Wi-SUN application. It provides a user interface to access any specified Wi-SUN FAN 1.0 or FAN 1.1 PHY. A radio button allows the user to choose between the FAN 1.0 or FAN 1.1 context.
The complete list can be filtered to help you find the right PHY configuration. An application can embed several PHYs from different regions and different specification versions.

The Application’s Default PHY input defines the PHY that the application starts with. The default value depends on the EFR32 radio board used to create the project. For example, a BRD4163A radio board supporting the 868 MHz band defaults to the
Πνευματικά δικαιώματα © 2025 Silicon Laboratories. Με την επιφύλαξη παντός δικαιώματος.

32/46

Wi-SUN Configurator
mandatory Wi-SUN PHY for the European region (that is, Wi-SUN FAN EU – 1 1a). On the other hand, a BRD4164A radio board supporting the 915 MHz band defaults to the North America mandatory Wi-SUN PHY (that is, Wi-SUN FAN NA – 1 1b). The user can always open the dropdown list and select another default PHY.
Every selected Wi-SUN PHY can be edited in the Radio Configurator by clicking the pen icon. This action opens the Radio Configurator user interface on the selected Wi-SUN PHY. Moreover, non Wi-SUN FAN PHY are listed under <Other Custom Profile= for information.

33/46

ZCL Advanced Platform
ZCL Advanced Platform
ZCL Advanced Platform (ZAP)
The ZCL Advanced Platform (ZAP) is a tool used to configure endpoints for Zigbee and Matter. When you open ZAP, it launches in a new tab next to the <project>.slcp tab. A Zigbee or Matter application can have multiple endpoints. Each endpoint contains a device configuration made up of Clusters on that end-point. The cluster groups differ depending on whether you re configuring a Zigbee or a Matter project, and the interface differs slightly. ZAP for Zigbee:

ZAP for Matter:

34/46

ZCL Advanced Platform

This section is illustrated with a Zigbee project, but the information applies to Matter as well. For more details about using ZAP with Matter, see Matter References: Using ZAP, the ZCL Advanced Platform.
At any point click Tutorial in the menu for an interactive tutorial.
Click ADD ENDPOINT to add a new endpoint.

In the next dialog, select a device type for the endpoint, and optionally change the endpoint number. Click CREATE to create the endpoint.

35/46

ZCL Advanced Platform To modify an endpoint, select it in the left panel.

The Filter dropdown in the upper right filters the clusters shown. To see only clusters that are enabled on the endpoint, select ‘Enabled Clusters’.

36/46

ZCL Advanced Platform

Settings in the Enable column enable either the Client or Server (or both) sides of a cluster. Depending on the changes you make, you may be notified that components have been added to your project. To remove the cluster entirely from the configuration, select ‘Not Enabled’.

Click the Gear icon next to a cluster to enable or disable attributes, manage how they are stored, manage attribute reporting, and also manage the handling of commands on that cluster. The cluster configuration interface consists of three tabs:
Attributes Attribute Reporting

37/46

ZCL Advanced Platform Commands

Configuration changes made through the Zigbee Cluster Configurator for a Zigbee project are saved to <projectfolder>configzclzcl_config.zap. For a Matter project the configuration is saved to <project-folder>configzap<name>.zap. The .zap file is the backing data file for the Zigbee Cluster Configurator configuration for your application. When you save the file, the Zigbee Cluster Configurator not only saves the .zap file into your project, but also automatically generates all the files required for your application. For Zigbee, the files are placed in the project’s autogen folder and all start with the ‘zap’ prefix. For Matter, the files are placed in the project’s autogen > zap-generated folder.
For additional details about cluster configuration and adding a custom cluster, see the Zigbee-focused AN1325: Zigbee Cluster Configurator User’s Guide.

38/46

Λύσεις
Λύσεις
Λύσεις
A solution is a construct that combines two or more projects such that they can be compiled, debugged, and flashed together. The solution is defined by a metadata .solutions file. Solutions can be local or shared. In a local solution, the .solutions file is stored in the Simplicity Studio Workspace. In a shared solution, the file is stored in the project specified when the shared solution is created. Shared solutions are easier to place under source control, and they can be exported to other Workspaces. Solution examples are available on the Example Projects and Demos tab or you can create your own through File > New > Solution or Projects > Manage Solutions > New. The resulting dialog shows available projects in the current Workspace. Name the solution, select the projects to be included in it, and click Finish.

Note: The generic term for the construct that combines multiple projects is a workspace. However, in Simplicity Studio a Workspace is a special directory into which projects (and solutions) are created. Therefore, whenever possible, Simplicity Studio documentation uses the term ‘solution’ for this construct.
Create a Solution from an Example
When you create a solution based on an example, the configuration dialog allows you to edit the name of the projects in the solution as well as the solution.

39/46

Λύσεις

Each project in the solution then opens individually. Project Explorer view shows the solution as a separate folder, and projects in the Workspace folder that are not included in the solution as ‘Other Projects’.

Configure the projects in the solution as you would other project. Select the solution folder and click Build to build all projects in the solution. Project- and solution-level post-build script files (.slpb) are provided with the examples, and will combine the individual projects into a downloadable .s37 image. Double-click an *.slpb file to open the Post-Build Editor to see how the script is configured.

40/46

Λύσεις

While the default memory use in the example solutions is fine for development and debugging, you can use Memory Editor to finalize the application memory layouts. Rebuild the solution to update the memory configurations.
Solutions are required for applications to take advantage of the EFR32 Series 2 TrustZone security feature. See AN1374: Series 2 TrustZone for a discussion of both the feature and how solutions are used to implement it.
Manage Solutions
Right-click the Solution in Project Explorer view, and click Solutions on the context menu to open the Manage Solutions dialog, set the active Configuration or sync solution configurations.
With Manage Solutions (also available on the Project menu) you can create, edit, and remove solutions.

Click Edit… to rename a solution, add or remove projects from a solution, or save a local solution as a shared solution. You must specify the project to contain the solution metadata.

41/46

Λύσεις
If the projects have multiple build configurations and the solution also has multiple build configurations, click Sync Solution Configuration to set the active build configuration of each project to match the solution’s active build configuration.

42/46

Memory Editor
Memory Editor
Memory Editor
The Memory Editor is a graphical tool for editing the flash and RAM memory layout of the applications in a solution. It can be opened from the Project Configurator Configuration Tools tab or the Quick Links card on the Overview tab. Memory Editor shows the Flash and RAM memory map for the projects in the solution. The default memory settings in the example solutions are good enough for software development and debugging, but with the Memory Editor you can fine-tune memory use based on your needs.

43/46

Memory Editor
When you alter memory used by changing either or both applications’ start or end location or size and save the changes, Memory Editor updates the linker file in the project autogen folder with the custom settings. Rebuild the projects to use the new memory configurations in the linker files. Memory Editor displays a warning if your changes cause the applications’ memory use to overlap. This is a beta implementation. Not all example projects have default settings included at this time, which results in a warning when you open the editor. Save the default values that the tool calculates as your starting point.

44/46

Project Retargeting
Project Retargeting
Retarget Project Workflow
Most developers begin their evaluations and firmware development with our development boards but eventually transition to custom hardware. To support this, Silicon Labs provides developers with tools and resources to seamlessly retarget example applications for their own custom boards based on the same or similar device OPN.
For developers aiming to run a Silicon Labs SDK example application on their custom board. For developers who have prototyped an application using a Silicon Labs development kit and wish to migrate their project to a custom board with the same or a similar target device.

1. Αναζήτηση για a Silicon Labs Development Kit based on the same or similar target device as what’s on the custom board. Silicon Labs boards are typically designed with superset target devices to maximize coverage, providing developers access to features such as additional pins, increased memory, enhanced peripherals, and expanded system capabilities. For custom board designs using devices within the same device family, the retargeting workflow supports transitions between superset and subset devices.
2. Create a project based on the desired example for the Silicon Labs Development Kit. 3. From Studio Project Configurator, retarget the board and target device.
Retargeting projects from Silicon Labs board examples utilizes the board configuration, software components, and drivers (e.g., LEDs, buttons, HFXO, LFXO, RF front-end, sensors) inherited from the original Silicon Labs board. This approach carries over the board support configuration to the custom board project, eliminating the need for manual BSP creation with the Pintool, provided the custom board’s pin configuration matches the Silicon Labs board. If the pin configuration differs, such as an LED being assigned to a different pin, the developer must update the configuration using the Pintool based on the custom board’s schematics. 4. Resolve any misconfigurations (e.g. pin definitions) that may have resulted from the migration. When retargeting to a target device with a different pinout (fewer or additional pins), the developer must resolve the pin differences based on the custom board schematic. When retargeting to a target device with the same hardware features (e.g., peripherals, power modes, and memory), the configuration from the original example is retained. However, when retargeting to a device with fewer hardware features, resulting in the loss of a peripheral, the developer must manually address unsupported components to prevent build failures.

45/46

Project Retargeting
When retargeting to a target device with different memory density, the project configurator will modify and define the Linker file επομένως.
Ο πρώηνample app’s system behavior and performance should remain consistent with the original, provided the custom board’s hardware matches that of the Silicon Labs board. Developers can generate a Project Configuration Report to summarize installed board components and verify the project’s configuration.

46/46

Έγγραφα / Πόροι

	SILICON LABS Simplicity Studio 5 Software [pdf] Οδηγός χρήστη Simplicity Studio 5 Software, Software
	SILICON LABS Simplicity Studio 5 Software [pdf] Οδηγός χρήστη Simplicity Studio 5 Software, Software

Αναφορές

Εγχειρίδιο χρήστη

SILICON LABS Simplicity Studio 5 Software

Προδιαγραφές

Οδηγίες χρήσης προϊόντος

Συχνές ερωτήσεις

Έγγραφα / Πόροι

Αναφορές

Αφήστε ένα σχόλιο

Ακύρωση απάντησης