Skip to content

Conversation

@silabs-dimayorg
Copy link
Contributor

@silabs-dimayorg silabs-dimayorg commented Nov 20, 2025

Updating Images and wording to include Studio 6 workflows in the Matter Provisioning documentation.

Description

Updates to Studio 6 workflow of the Matter Provisioning tool

Changes Made

Added formatting to the already existing links
Added Simplicity Commander installation link

Checklist


Note

Refreshes the Matter provisioning doc for Studio 6 with GFW details, updated links/paths, a new image, and removal of outdated sections.

  • Docs (Matter provisioning):
    • Update Commissionee hardware description to reference the selector guide and supported devices list in provision/images.
    • Add and clarify links (Simplicity Commander install, repo references); tweak path example to sisdk_release.
    • Introduce and describe Generator Firmware (GFW) usage and -gf option; add BLE self-provisioning note formatting and directory path backticks.
    • Replace Studio image with images/lighting-over-thread-example-ss6.png.
    • Remove outdated content (chip-cert binary location note; "Install Matter Device Attestation Credentials Component" subsection).

Written by Cursor Bugbot for commit 7a1015c. This will update automatically on new commits. Configure here.

Updating Images and wording to include Studio 6 workflows in the Matter Provisioning documentation.
- **Commissionee**

- WSTK with MG24A or MG24B (Initial boards supported for Matter CPMS Alpha program). The provisioning script currently supports MG12 devices but will no longer do so moving forward. In this tutorial, you will build an application with a BRD4187C.
- WSTK with a Matter compatible development board (see the [Silicon Labs Matter Selector Guide](https://www.silabs.com/wireless/matter/selector-guide). The provisioning script currently supports the devices listed in [Generator Firmware Images](http://github.com/SiliconLabs/matter_extension/tree/main/provision/images). In this tutorial, we will build an application with a BRD4187C.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- WSTK with a Matter compatible development board (see the [Silicon Labs Matter Selector Guide](https://www.silabs.com/wireless/matter/selector-guide). The provisioning script currently supports the devices listed in [Generator Firmware Images](http://github.com/SiliconLabs/matter_extension/tree/main/provision/images). In this tutorial, we will build an application with a BRD4187C.
- WSTK with a Matter compatible development board (see the [Silicon Labs Matter Selector Guide](https://www.silabs.com/wireless/matter/selector-guide). The provisioning script currently supports the devices listed in [Generator Firmware Images](http://github.com/SiliconLabs/matter_extension/tree/main/provision/images). In this tutorial, you build an application with a BRD4187C.

- Simplicity Commander:

- Please install Simplicity Commander and add it to you environment variables.
- Please install [Simplicity Commander](https://www.silabs.com/software-and-tools/simplicity-studio/simplicity-commander?tab=getting-started) and add it to you environment variables.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Please install [Simplicity Commander](https://www.silabs.com/software-and-tools/simplicity-studio/simplicity-commander?tab=getting-started) and add it to you environment variables.
- Install [Simplicity Commander](https://www.silabs.com/software-and-tools/simplicity-studio/simplicity-commander?tab=getting-started) and add it to your environment variables.

Once you have generated the PAA, PAI and DAC and have installed the provisioning tool you can use it to write the Commissionable Data and the Device Attestation Data. As previously mentioned, there are two provisioning flows possible, following are the necessary steps to correctly provision your device.

Go to the ./matter_extension/provision/directory:
Go to the `./matter_extension/provision/directory:`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Go to the `./matter_extension/provision/directory:`
Go to the `./matter_extension/provision/directory`.

### Generator Firmware

To choose different provisioning flows, the provisioning script has the argument option -gf to direct the script:
The [Generator Firmware (GFW)](https://github.com/SiliconLabs/matter_extension/tree/main/provision#generator-firmware) is a FreeRTOS application that runs on the targeted device, and assists with the provisioning of the device. To choose a specific Generator Firmware, the provisioning script has the argument option -gf to direct the script:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The [Generator Firmware (GFW)](https://github.com/SiliconLabs/matter_extension/tree/main/provision#generator-firmware) is a FreeRTOS application that runs on the targeted device, and assists with the provisioning of the device. To choose a specific Generator Firmware, the provisioning script has the argument option -gf to direct the script:
The [Generator Firmware (GFW)](https://github.com/SiliconLabs/matter_extension/tree/main/provision#generator-firmware) is a FreeRTOS application that runs on the targeted device, and assists with the provisioning of the device. To choose a specific Generator Firmware, the provisioning script has the argument option `-gf` to direct the script:

Copy link
Contributor

@silabs-orion silabs-orion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, nothing to add to @silabs-JayR changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants