Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions sld272-bluetooth-system-performance/auto-pa-mode.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Bluetooth LE Auto PA mode

**NOTE**: The content on this page is deprecated as of the SiSDK 2025.6.1 release. For additional details or guidance, please contact Silicon Labs Support.

## Introduction

The EFR32 families of chips each come equipped with two or three Power Amplifiers (PAs):
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@ Tests were performed using Silicon Labs evaluation hardware, with each product f

| Setup Component |Version / Board |
|-|-|
| Bluetooth SDK (embedded) |3.2.4 / 3.3.2 |
| Gecko SDK |4.0.2 |
| EFR32 Connect |2.4.1 / 2.4.3 |
| ERF32xG13 |BRD4104A |
| ERF32xG21 |BRD4181A / BRD4181B |
| EFR32xG22 |BRD4182A |
| Bluetooth SDK (embedded) |10.1.1 |
| Simplicity SDK |2025.6.2 |
| Simplicity connect mobile application |3.2.0 |
| ERF32xG24B |BRD4186C |
| ERF32xG27 |BRD4194A |
| EFR32BG29 |BRD4414A |
Original file line number Diff line number Diff line change
Expand Up @@ -275,7 +275,7 @@ The table below provides the details of the test cases. All the test cases were
<tr>
<td>5.6</td>
<td>Characteristic</td>
<td>User Len 1</td>
<td>User Length 1</td>
<td>
<ul>
<li>Type = user</li>
Expand All @@ -289,7 +289,7 @@ The table below provides the details of the test cases. All the test cases were
<tr>
<td>5.7</td>
<td>Characteristic</td>
<td>User Len 255</td>
<td>User Length 255</td>
<td>
<ul>
<li>Type = user</li>
Expand All @@ -303,7 +303,7 @@ The table below provides the details of the test cases. All the test cases were
<tr>
<td>5.8</td>
<td>Characteristic</td>
<td>User Len Variable 4</td>
<td>User Length Variable 4</td>
<td>
<ul>
<li>Type = user</li>
Expand Down Expand Up @@ -359,7 +359,6 @@ The table below provides the details of the test cases. All the test cases were
</ul>
<p>The parameters are set as above and device sends the data to the mobile. Mobile computes the throughput (Bytes/S).</p>
<p>Pass if there is successful data transfer between the device and mobile.</p>
<p>See <a href="04-test-results.md"></a> for more details.</p>
</td>
</tr>
<tr>
Expand Down Expand Up @@ -416,5 +415,42 @@ The table below provides the details of the test cases. All the test cases were
<p>Pass if there is no error and read value matches the pre-set value (0x55) after pairing.</p>
</td>
</tr>
<tr>
<td>8.4</td>
<td>Security and Encryption</td>
<td>CCCD retention on bonded connection</td>
<td>
<ul>
<li>Type = hex</li>
<li>Length = 1</li>
<li>Properties = Bonded_Notify</li>
<li>Value = 0x55</li>
</ul>
<p>Mobile connects to DUT and creates bonding with DUT(reuse existing bonding from test case 8.3)</p>
<p>Mobile writes CCCD to different value from the default and disconnects from DUT.</p>
<p>Mobile reconnects to DUT (Pass: if reconnect without pairing process).</p>
<p>Mobile reads CCCD (Pass: if the CCCD value is the same as the value written before the disconnection).</p>
<p>Mobile writes CCCD (Pass: if the CCCD value was written).</p>
</td>
</tr>
<tr>
<td>8.5</td>
<td>Security and Encryption</td>
<td>LE Privacy 1.2</td>
<td>
<ul>
<li>Type = hex</li>
<li>Length = 2</li>
<li>Properties = Read, write</li>
<li>Value =0x01</li>
</ul>
<p>Mobile connects to and creates bonding with DUT (reuse existing bonding from test case 8.3)</p>
<p>Mobile writes a value 00 04 00 to the characteristic. This triggers a connection close on DUT. </p>
<p>DUT adds the tester’s address to the accept list and enables accept list based filtering.</p>
<p>DDUT adds the tester’s identity resolution key (IRK) to the resolve list.</p>
<p>Mobile reconnects to DUT with resolvable private address (RPA) - RPA is sent in the connection request (if tester used RPA during the first connection, then a new RPA should be generated)</p>
<p>Test case is success if mobile was able to connect to DUT</p>
</td>
</tr>
</tbody>
</table>
Loading
Loading