SiliconLabsSoftware · silabs-mehdi (silabs-mehdi) · Sep 9, 2026 · Sep 7, 2026 · Sep 8, 2026
diff --git a/security/encrypted_advertisement/README.md → ...rtising/encrypted_advertisement/README.md b/security/encrypted_advertisement/README.md → ...rtising/encrypted_advertisement/README.md
diff --git a/..._advertisement/SimplicityStudio/readme.md → ..._advertisement/SimplicityStudio/readme.md b/..._advertisement/SimplicityStudio/readme.md → ..._advertisement/SimplicityStudio/readme.md
diff --git a/...c_encrypted_advertisement_advertiser.slcp → ...c_encrypted_advertisement_advertiser.slcp b/...c_encrypted_advertisement_advertiser.slcp → ...c_encrypted_advertisement_advertiser.slcp
diff --git a/.../soc_encrypted_advertisement_scanner.slcp → .../soc_encrypted_advertisement_scanner.slcp b/.../soc_encrypted_advertisement_scanner.slcp → .../soc_encrypted_advertisement_scanner.slcp
diff --git a/...nfig/advertiser/gatt_configuration.btconf → ...nfig/advertiser/gatt_configuration.btconf b/...nfig/advertiser/gatt_configuration.btconf → ...nfig/advertiser/gatt_configuration.btconf
diff --git a/.../config/scanner/gatt_configuration.btconf → .../config/scanner/gatt_configuration.btconf b/.../config/scanner/gatt_configuration.btconf → .../config/scanner/gatt_configuration.btconf
diff --git a/...rypted_advertisement/images/add_log_1.png → ...rypted_advertisement/images/add_log_1.png b/...rypted_advertisement/images/add_log_1.png → ...rypted_advertisement/images/add_log_1.png
diff --git a/...rypted_advertisement/images/add_log_2.png → ...rypted_advertisement/images/add_log_2.png b/...rypted_advertisement/images/add_log_2.png → ...rypted_advertisement/images/add_log_2.png
diff --git a/...rypted_advertisement/images/add_log_3.png → ...rypted_advertisement/images/add_log_3.png b/...rypted_advertisement/images/add_log_3.png → ...rypted_advertisement/images/add_log_3.png
diff --git a/...rypted_advertisement/images/add_log_4.png → ...rypted_advertisement/images/add_log_4.png b/...rypted_advertisement/images/add_log_4.png → ...rypted_advertisement/images/add_log_4.png
diff --git a/...rypted_advertisement/images/add_log_5.png → ...rypted_advertisement/images/add_log_5.png b/...rypted_advertisement/images/add_log_5.png → ...rypted_advertisement/images/add_log_5.png
diff --git a/...ertisement/images/add_simple_button_1.png → ...ertisement/images/add_simple_button_1.png b/...ertisement/images/add_simple_button_1.png → ...ertisement/images/add_simple_button_1.png
diff --git a/...ertisement/images/add_simple_button_2.png → ...ertisement/images/add_simple_button_2.png b/...ertisement/images/add_simple_button_2.png → ...ertisement/images/add_simple_button_2.png
diff --git a/...ertisement/images/add_simple_button_3.png → ...ertisement/images/add_simple_button_3.png b/...ertisement/images/add_simple_button_3.png → ...ertisement/images/add_simple_button_3.png
diff --git a/...encrypted_advertisement/images/btconf.png → ...encrypted_advertisement/images/btconf.png b/...encrypted_advertisement/images/btconf.png → ...encrypted_advertisement/images/btconf.png
diff --git a/...sement/images/encrypted_advertisement.png → ...sement/images/encrypted_advertisement.png b/...sement/images/encrypted_advertisement.png → ...sement/images/encrypted_advertisement.png
diff --git a/...advertisement/images/extended_scanner.png → ...advertisement/images/extended_scanner.png b/...advertisement/images/extended_scanner.png → ...advertisement/images/extended_scanner.png
diff --git a/...encrypted_advertisement/images/result.png → ...encrypted_advertisement/images/result.png b/...encrypted_advertisement/images/result.png → ...encrypted_advertisement/images/result.png
diff --git a/...rypted_advertisement/inc/advertiser/app.h → ...rypted_advertisement/inc/advertiser/app.h b/...rypted_advertisement/inc/advertiser/app.h → ...rypted_advertisement/inc/advertiser/app.h
diff --git a/...encrypted_advertisement/inc/scanner/app.h → ...encrypted_advertisement/inc/scanner/app.h b/...encrypted_advertisement/inc/scanner/app.h → ...encrypted_advertisement/inc/scanner/app.h
diff --git a/...rypted_advertisement/src/advertiser/app.c → ...rypted_advertisement/src/advertiser/app.c b/...rypted_advertisement/src/advertiser/app.c → ...rypted_advertisement/src/advertiser/app.c
diff --git a/...ted_advertisement/src/advertiser/app_bm.c → ...ted_advertisement/src/advertiser/app_bm.c b/...ted_advertisement/src/advertiser/app_bm.c → ...ted_advertisement/src/advertiser/app_bm.c
diff --git a/...ypted_advertisement/src/advertiser/main.c → ...ypted_advertisement/src/advertiser/main.c b/...ypted_advertisement/src/advertiser/main.c → ...ypted_advertisement/src/advertiser/main.c
diff --git a/...encrypted_advertisement/src/scanner/app.c → ...encrypted_advertisement/src/scanner/app.c b/...encrypted_advertisement/src/scanner/app.c → ...encrypted_advertisement/src/scanner/app.c
diff --git a/...rypted_advertisement/src/scanner/app_bm.c → ...rypted_advertisement/src/scanner/app_bm.c b/...rypted_advertisement/src/scanner/app_bm.c → ...rypted_advertisement/src/scanner/app_bm.c
diff --git a/...ncrypted_advertisement/src/scanner/main.c → ...ncrypted_advertisement/src/scanner/main.c b/...ncrypted_advertisement/src/scanner/main.c → ...ncrypted_advertisement/src/scanner/main.c
diff --git a/advertising/periodic_advertisement_with_responses/encrypted_pawr/README.md b/advertising/periodic_advertisement_with_responses/encrypted_pawr/README.md
@@ -0,0 +1,248 @@
+# Encrypted Periodic Advertising with Responses and PAST Example
+
+## Description
+
+This example demonstrates secure application-data exchange between one access point and multiple tags using Bluetooth LE Periodic Advertising with Responses (PAwR) Encrypted Advertising Data (EAD), and Periodic Advertising Synchronization Transfer (PAST).
+
+The example consists of two projects:
+
+- **Access point:** provisions tags, operates the PAwR advertiser, encrypts subevent data, and decrypts tag responses.
+- **Tag:** advertises for provisioning, receives PAwR synchronization through PAST, decrypts its assigned subevent, and sends an encrypted response.
+
+A temporary Bluetooth connection is used to provision each tag. After provisioning, the regular data exchange is connectionless and uses PAwR subevents and response slots.
+
+### Access point
+
+At boot, the access point initializes its EAD session, begins scanning for tags, and starts its PAwR train. It uses passive scanning on the 1M PHY and identifies tags by the custom **Secure Tag** service UUID included in their extended advertisements.
+
+In this demonstration, a tag ID selects both the subevent to which the tag subscribes and the response slot in which it transmits. This one-to-one mapping is an application choice and can be changed as needed.
+
+The following APIs perform the main access-point operations.
+
+1. Configure and start scanning for tags:
+
+```c
+sl_bt_scanner_set_parameters(sl_bt_scanner_scan_mode_passive,
+                             200,
+                             200);
+
+sl_bt_scanner_start(sl_bt_scanner_scan_phy_1m,
+                    sl_bt_scanner_discover_observation);
+```
+
+2. Create an advertising set and start the PAwR advertiser:
+
+```c
+sl_bt_advertiser_create_set(&pawr_advertising_set_handle);
+
+sl_bt_pawr_advertiser_start(pawr_advertising_set_handle,
+                            PERIODIC_ADV_INTERVAL,
+                            PERIODIC_ADV_INTERVAL,
+                            0,
+                            SUBEVENT_NUMBER,
+                            SUBEVENT_INTERVAL,
+                            RESPONSE_SLOT_DELAY,
+                            RESPONSE_SLOT_SPACING,
+                            RESPONSE_SLOT_NUMBER_PER_SUBVENT);
+```
+
+3. Connect to a discovered tag and provision it through GATT:
+
+```c
+sl_bt_connection_open(report->address,
+                      report->address_type,
+                      sl_bt_gap_phy_1m,
+                      &connection_handle);
+
+sl_bt_gatt_discover_primary_services_by_uuid(...);
+sl_bt_gatt_discover_characteristics_by_uuid(...);
+sl_bt_gatt_write_characteristic_value(...);
+```
+
+4. Transfer the PAwR synchronization information to the tag using PAST:
+
+```c
+sl_bt_advertiser_past_transfer(connection_handle,
+                               0,
+                               pawr_advertising_set_handle);
+```
+
+5. Encrypt and provide data for each requested PAwR subevent:
+
+```c
+sl_bt_ead_randomizer_update(&nonce);
+sl_bt_ead_encrypt(...);
+sl_bt_ead_pack_ad_data(...);
+
+sl_bt_pawr_advertiser_set_subevent_data(req.advertising_set,
+                                        subevent_index,
+                                        0,
+                                        RESPONSE_SLOT_NUMBER_PER_SUBVENT,
+                                        advertisement_len,
+                                        advertisement_buffer);
+```
+
+When a response report is received, the access point uses the response slot to locate the associated tag record and tag-specific key. It unpacks and decrypts the response using `sl_bt_ead_unpack_ad_data()` and `sl_bt_ead_decrypt()`.
+
+The access point periodically checks its tag records. A tag without a successfully decrypted response for 30 seconds is marked stale, allowing its ID and response key slot to be reused.
+
+### Tag
+
+At boot, the tag configures itself to synchronize when PAST information is received. It then starts connectable extended advertising. The tag's GATT database advertises the custom [Secure Tag service](config/gatt_configuration.btconf#L51), which contains:
+
+- **Tag ID:** the identifier assigned by the access point.
+- **AP Sync Key Material:** the EAD session key and initialization vector used to decrypt access-point subevent data.
+- **Tag Response Key Material:** the tag-specific EAD session key and initialization vector used to encrypt responses.
+
+The following APIs perform the main tag operations.
+
+1. Configure automatic synchronization from received PAST information:
+
+```c
+sl_bt_past_receiver_set_default_sync_receive_parameters(
+  sl_bt_past_receiver_mode_synchronize,
+  PERIODIC_SYNC_SKIP,
+  PERIODIC_SYNC_TIMEOUT,
+  sl_bt_sync_report_all);
+```
+
+2. Start connectable extended advertising for discovery and provisioning:
+
+```c
+sl_bt_advertiser_create_set(&advertising_set_handle);
+sl_bt_extended_advertiser_generate_data(
+  advertising_set_handle,
+  sl_bt_advertiser_general_discoverable);
+
+sl_bt_extended_advertiser_start(
+  advertising_set_handle,
+  sl_bt_extended_advertiser_connectable,
+  0);
+```
+
+3. After receiving the PAST transfer, subscribe to the subevent assigned by the tag ID:
+
+```c
+sl_bt_pawr_sync_set_sync_subevents(
+  pawr_handle,
+  sizeof(subevents_subscription_list),
+  subevents_subscription_list);
+```
+
+4. Decrypt the received subevent data and prepare an encrypted response:
+
+```c
+sl_bt_ead_unpack_ad_data(...);
+sl_bt_ead_decrypt(...);
+sl_bt_ead_randomizer_update(&tag_resp_nonce);
+sl_bt_ead_encrypt(...);
+sl_bt_ead_pack_ad_data(...);
+```
+
+5. Send the response in the slot assigned to the tag:
+
+```c
+sl_bt_pawr_sync_set_response_data(pawr_handle,
+                                  sync_report->event_counter,
+                                  sync_report->subevent,
+                                  sync_report->subevent,
+                                  tag_id,
+                                  secret_data_len,
+                                  response_buffer);
+```
+
+If the tag loses PAwR synchronization while it is disconnected, a periodic timer causes it to resume connectable advertising so that the access point can provision it again.
+
+### Provisioning and synchronization sequence
+
+1. The access point starts the PAwR train and scans for the Secure Tag service.
+2. The tag starts connectable extended advertising.
+3. The access point discovers the tag and opens a Bluetooth connection.
+4. The access point discovers the Secure Tag service and its three characteristics.
+5. The devices establish a bonded, encrypted LE Secure Connections link.
+6. The access point assigns a tag ID.
+7. The access point writes the shared AP synchronization key material.
+8. The access point creates and writes unique response key material for the tag.
+9. The access point transfers the PAwR synchronization information using PAST.
+10. The access point records the tag as active and closes the connection.
+11. The tag subscribes to the subevent corresponding to its assigned ID.
+12. The devices continue exchanging encrypted data without a Bluetooth connection.
+
+## Simplicity SDK version
+
+- Simplicity SDK v2025.12.1
+
+## Hardware required
+
+- Two or more Wireless Starter Kit mainboards
+- One Bluetooth-capable Series 2 radio board for the access point
+- One Bluetooth-capable Series 2 radio board for each tag
+
+At least two devices are required: one access point and one tag.
+
+## Setting up
+
+> **Note:** The provided projects already contain the required source files, software components, and configuration. The following steps are useful if you you are starting from the basic bluetooth empty
+
+### Access point
+
+1. Open Simplicity Studio v6 with Simplicity SDK v2025.12.1 or a compatible version.
+2. generate a bluetooth empty project.
+3. Verify that the following important software components are installed:
+   - Extended Advertising
+   - Scanner for extended advertisements
+   - Periodic Advertising using PAwR trains
+   - Transfer periodic synchronization information for a local advertising set
+   - GATT Client
+   - Security Manager
+   - Encrypted Advertising Data Core
+   - Log
+4. Verify that [app.c](src/access_point/app.c), [main.c](src/access_point/main.c), and [app.h](inc/access_point/app.h) are included in the generated project.
+5. Build and flash the project to the access-point device.
+6. Open the serial console for the device. (make sure that you enable VCOM in the board control component)
+
+### Tag
+
+1. Open Simplicity Studio v6 with Simplicity SDK v2025.12.1 or a compatible version.
+2. Verify that the following important software components are installed:
+   - Extended Advertising
+   - PAST Receiver
+   - Synchronization to Periodic Advertising with Responses trains
+   - GATT Server
+   - Security Manager
+   - Encrypted Advertising Data Core
+   - Log
+3. Insert [gatt_configuration.btconf](config/gatt_configuration.btconf) is the config/btconf directory
+5. Verify that [app.c](src/tag/app.c), [main.c](src/tag/main.c), and [app.h](inc/tag/app.h) are included in the generated project.
+6. Build and flash the project to the tag device.
+7. Open the serial console for the device.(make sure that you enable VCOM in the board control component)
+
+## Usage
+
+1. Reset the access point. It prints its Bluetooth address, starts scanning for tags, and starts the PAwR train.
+2. Reset a tag. It advertises the Secure Tag service.
+3. The access point connects to the tag, assigns an ID, provisions the EAD keys, and transfers PAwR synchronization.
+4. After the connection closes, the tag reports the received PAwR timing and synchronization state.
+5. Observe the tag decrypting access-point messages and the access point decrypting tag responses.
+6. Reset additional tags one at a time to provision multiple devices.
+
+## Results
+
+Below is the tag log, it shows:
+- A boot sequence that starts advertising
+- A connection with increased security
+- Reception of an ID (also keys that are not logged here)
+- Reception of the PAWR train and  connection close
+- The subevent subscribed and the payload
+- The response and its payload
+
+![tag_log](images/tag_log.png)
+
+Below is the access point log, it shows:
+- A boot sequence that starts scanning for tags
+- The stack requests to the application for the subevents data of the PAWR train
+- A connection event with increased security
+- GATT operation to write a tag ID, AP sync key and tag response key
+- The response from the tag to subevent 0 in response slot 0
+
+![ap_log](images/ap_log.png)
diff --git a/...periodic_advertisement_with_responses/encrypted_pawr/SimplicityStudio/readme.md b/...periodic_advertisement_with_responses/encrypted_pawr/SimplicityStudio/readme.md
@@ -0,0 +1,8 @@
+# encrypted pawr Example
+
+The readme file of this project can be found [here](https://github.com/SiliconLabs/bluetooth_stack_features/blob/master/advertising/periodic_advertisement_with_responses/encrypted_pawr/README.md).
+
+.
+> Note: In this project all the necessary software components are installed, source files are copied, and configurations are set, hence you can disregard the Setting Up section of the online readme file. Nevertheless, if you want to add the demonstrated feature to your own project, it might be good to know what software components you must install, and what configurations you must set beforehand, hence reading through the Setting Up section might be useful.
+
+> Note: This project requires a bootloader. For Series 1 (EFR32xG1x) devices please flash a **Bluetooth In-place OTA DFU** bootloader or an **Internal Storage** bootloader to your device to get this application to work. For Series 2 (EFR32xG2x) devices please flash a **Bluetooth Apploader OTA DFU** bootloader to your device
diff --git a/...ement_with_responses/encrypted_pawr/SimplicityStudio/soc_encrypted_pawr_access_point.slcp b/...ement_with_responses/encrypted_pawr/SimplicityStudio/soc_encrypted_pawr_access_point.slcp
@@ -0,0 +1,62 @@
+project_name: soc_encrypted_pawr_access_point
+package: Bluetooth
+label: Bluetooth - SoC Encrypted PAwR Access Point
+description: >
+  Provisions PAwR tags, transfers synchronization with PAST, and exchanges encrypted advertising data.
+category: Bluetooth Examples
+quality: development
+
+component:
+  - id: device_init
+  - id: clock_manager
+  - id: bluetooth_stack
+  - id: gatt_configuration
+  - id: bluetooth_feature_legacy_advertiser
+  - id: bluetooth_feature_extended_advertiser
+  - id: bluetooth_feature_legacy_scanner
+  - id: bluetooth_feature_extended_scanner
+  - id: bluetooth_feature_connection_role_central
+  - id: bluetooth_feature_connection_role_peripheral
+  - id: bluetooth_feature_gatt
+  - id: bluetooth_feature_gatt_server
+  - id: bluetooth_feature_sm
+  - id: bluetooth_feature_system
+  - id: bluetooth_feature_pawr_advertiser
+  - id: bluetooth_feature_advertiser_past
+  - id: ead_core
+  - id: app_assert
+  - id: app_log
+  - id: app_os_helper
+  - id: component_catalog
+  - id: gatt_service_device_information_override
+  - id: mpu
+  - id: rail_util_pti
+  - id: sl_main
+
+source:
+  - path: ../src/access_point/app.c
+  - path: ../src/access_point/main.c
+
+include:
+  - path: ../inc/access_point/
+    file_list:
+      - path: app.h
+
+readme:
+  - path: ../README.md
+
+configuration:
+  - name: SL_STACK_SIZE
+    value: "2752"
+  - condition:
+      - psa_crypto
+    name: SL_PSA_KEY_USER_SLOT_COUNT
+    value: "0"
+
+tag:
+  - hardware:rf:band:2400
+
+ui_hints:
+  highlight:
+    - path: ../README.md
+      focus: true
diff --git a/..._advertisement_with_responses/encrypted_pawr/SimplicityStudio/soc_encrypted_pawr_tag.slcp b/..._advertisement_with_responses/encrypted_pawr/SimplicityStudio/soc_encrypted_pawr_tag.slcp
@@ -0,0 +1,68 @@
+project_name: soc_encrypted_pawr_tag
+package: Bluetooth
+label: Bluetooth - SoC Encrypted PAwR Tag
+description: >
+  Receives PAwR synchronization with PAST and exchanges encrypted advertising data with an access point.
+category: Bluetooth Examples
+quality: development
+
+component:
+  - id: device_init
+  - id: clock_manager
+  - id: bluetooth_stack
+  - id: gatt_configuration
+  - id: bluetooth_feature_legacy_advertiser
+  - id: bluetooth_feature_extended_advertiser
+  - id: bluetooth_feature_legacy_scanner
+  - id: bluetooth_feature_connection_role_central
+  - id: bluetooth_feature_connection_role_peripheral
+  - id: bluetooth_feature_gatt
+  - id: bluetooth_feature_gatt_server
+  - id: bluetooth_feature_sm
+  - id: bluetooth_feature_system
+  - id: bluetooth_feature_past_receiver
+  - id: bluetooth_feature_pawr_sync
+  - id: ead_core
+  - id: app_assert
+  - id: app_log
+  - id: app_os_helper
+  - id: component_catalog
+  - id: gatt_service_device_information_override
+  - id: mpu
+  - id: rail_util_pti
+  - id: sl_main
+
+source:
+  - path: ../src/tag/app.c
+  - path: ../src/tag/main.c
+
+include:
+  - path: ../inc/tag/
+    file_list:
+      - path: app.h
+
+readme:
+  - path: ../README.md
+
+config_file:
+  - override:
+      component: gatt_configuration
+      file_id: gatt_configuration_file_id
+    path: ../config/gatt_configuration.btconf
+    directory: btconf
+
+configuration:
+  - name: SL_STACK_SIZE
+    value: "2752"
+  - condition:
+      - psa_crypto
+    name: SL_PSA_KEY_USER_SLOT_COUNT
+    value: "0"
+
+tag:
+  - hardware:rf:band:2400
+
+ui_hints:
+  highlight:
+    - path: ../README.md
+      focus: true