1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
|
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>Release Notes for STM32WB Copro Wireless Binaries</title>
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<link rel="stylesheet" href="../../../_htmresc/mini-st_2020.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
<link rel="icon" type="image/x-icon" href="../../../_htmresc/favicon.png" />
</head>
<body>
<div class="row">
<div class="col-sm-12 col-lg-4">
<center>
<h1 id="release-notes-for">Release Notes for</h1>
<h1 id="stm32wb-copro-wireless-binaries"><mark>STM32WB Copro Wireless Binaries</mark></h1>
<p>Copyright © 2020 STMicroelectronics<br />
</p>
<a href="https://www.st.com" class="logo"><img src="../../../_htmresc/st_logo_2020.png" alt="ST logo" /></a>
</center>
<h1 id="known-limitations">Known Limitations</h1>
<p><strong>If Anti-Rollback needs to be activated</strong>, please make sure to activate it only after installing the latest FUS version (>= V1.2.0) and after successfully installing a wireless stack (without deleting it). <strong>Otherwise, further wireless stack installation will be blocked.</strong></p>
<h1 id="purpose">Purpose</h1>
<p>This release covers the delivery of STM32WB Coprocessor binaries.</p>
<p>Here is the list of references to user documents:</p>
<ul>
<li><a href="http://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/dm00513965.pdf">AN5185</a> : ST FW upgrade services for STM32WB</li>
<li><a href="https://www.st.com/resource/en/user_manual/dm00403500-stm32cubeprogrammer-software-description-stmicroelectronics.pdf">UM2237</a> : STM32CubeProgrammer User Manual</li>
</ul>
<p>Here is the list of the supported binaries:</p>
<ul>
<li>stm32wb1x_BLE_HCI_AdvScan_fw.bin
<ul>
<li>HCI Layer only mode 5.2 certified : Link Layer, HCI</li>
<li>BT SIG Certification listing : <a href="https://launchstudio.bluetooth.com/ListingDetails/70712">Declaration ID D042213</a></li>
<li>To be used for advertising and scanning through HCI interface</li>
</ul></li>
<li>stm32wb1x_BLE_LLD_fw.bin
<ul>
<li>BLE LLD (Low Level Driver) Radio Transparent firmware</li>
<li>To be used for direct access on BLE LLD features and API</li>
</ul></li>
<li>stm32wb1x_BLE_Stack_full_fw.bin
<ul>
<li>Full BLE Stack 5.2 certified : Link Layer, HCI, L2CAP, ATT, SM, GAP and GATT database</li>
<li>BT SIG Certification listing : <a href="https://launchstudio.bluetooth.com/ListingDetails/59722">Declaration ID D042164</a>
<ul>
<li>Following features are kept:
<ul>
<li>GAP peripheral, central (LL Master up to 6 links with Slave up to 2 links/ Master up to 7 links with Slave up to 1 links/ Master up to 8 links )</li>
<li>GATT server, client</li>
<li>Data length extension</li>
<li>2Mbit PHY / PHY update</li>
<li>Privacy</li>
<li>White list</li>
<li>Legacy Pairing, LE secure connections</li>
<li>HCI interface (full, like stm32wb5x_BLE_HCILayer_fw.bin)</li>
<li>Direct Test Mode</li>
</ul></li>
</ul></li>
</ul></li>
<li>stm32wb1x_BLE_Stack_light_fw.bin
<ul>
<li>Full BLE Stack 5.2 certified : Link Layer, HCI, L2CAP, ATT, SM, GAP and GATT database</li>
<li>BT SIG Certification listing : <a href="https://launchstudio.bluetooth.com/ListingDetails/59722">Declaration ID D042164</a></li>
<li>Wireless Ble stack Light configuration – Slave Only
<ul>
<li>Following features are kept:
<ul>
<li>GAP peripheral only (LL Slave up to 2 links)</li>
<li>GATT server</li>
<li>Data length extension</li>
<li>Privacy</li>
<li>White list</li>
<li>Legacy Pairing, LE secure connections</li>
<li>HCI interface (reduced)</li>
<li>Direct Test Mode</li>
</ul></li>
<li>BLE “Slave Only” stack implies that with this stack configuration, STM32WB is not able to scan and request a BLE connection.</li>
<li>It will just advertise, and accept incoming connection request from other master devices (e.g. Smartphone) (Slave up to 2 links).</li>
<li>While with the “full feature” BLE stack, STM32WB1xx is able to support both master and slave roles on different links.</li>
</ul></li>
</ul></li>
<li>stm32wb1x_BLE_Stack_basic_fw.bin
<ul>
<li>Full BLE Stack 5.2 certified : Link Layer, HCI, L2CAP, ATT, SM, GAP and GATT database</li>
<li>BT SIG Certification listing : <a href="https://launchstudio.bluetooth.com/ListingDetails/59722">Declaration ID D042164</a></li>
<li>Wireless Ble stack Basic configuration
<ul>
<li>Following features are kept:
<ul>
<li>GAP peripheral & Central (8 links - LL slave up to 2 links)</li>
<li>GATT server, client</li>
<li>Data length extension</li>
<li>Privacy</li>
<li>White list</li>
<li>Legacy Pairing, LE secure connections</li>
<li>HCI interface (reduced)</li>
</ul></li>
<li>Following features are removed from Full BLE Stack:
<ul>
<li>L2Cap Connection - oriented channel (Chip/ Ip over BLE,…)</li>
<li>Additional beacon</li>
<li>Some HCI interface features (won’t be able to process through HCI interface)</li>
<li>Phy update (2Mb/s)</li>
<li>Direct test mode</li>
</ul></li>
</ul></li>
</ul></li>
<li>stm32wb1x_BLE_HCILayer_fw.bin
<ul>
<li>HCI Layer only mode 5.2 certified : Link Layer, HCI with Direct Test Mode</li>
<li>BT SIG Certification listing : <a href="https://launchstudio.bluetooth.com/ListingDetails/70712">Declaration ID D042213</a></li>
</ul></li>
</ul>
<p><mark>How to flash the Wireless Coprocessor Binary via SWD/JTAG by ST-LINK (STM32CubeProgrammer GUI)</mark></p>
<ul>
<li><p><em>Inside the below procedure, the references to binaries name and install address are provided in the section <strong>Main Changes</strong> of this file.</em></p></li>
<li><p>STEP 1: Use STM32CubeProgrammer GUI</p>
<ul>
<li><p>Version 2.7.0 or higher.</p></li>
<li><p>It gives access to Firmware Upgrade Service (FUS) (<a href="http://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/DM00513965.pdf">AN5185</a> : ST firmware upgrade services for STM32WB Series.) through Bootloader.</p></li>
<li><p>It is currently available as Graphical User Interface (GUI) mode (or Command Line Interface (CLI) mode).</p></li>
</ul></li>
<li><p>STEP 2: Access to SWD Interface (system flash)</p>
<ul>
<li>For NUCLEO-WB15 :
<ul>
<li>Power ON via ST-LINK and Jumper JP1(USB_STL)</li>
</ul></li>
<li>open STM32CubeProgrammer GUI and select “ST-LINK”</li>
<li>in ST-LINK configuration: (Port: SWD) then select “Connect”</li>
</ul></li>
<li><p>STEP 3: select “Start FUS” in Firmware Upgrade Services</p></li>
<li><p>STEP 4: Download new wireless stack (after “FW Delete” if requested)</p>
<ul>
<li>in Firmware Upgrade Service: (File Path: [Wireless_Coprocessor_Binary], Start Adress: [Install@])</li>
<li>then select “Firmware Upgrade” (with “Verify download” and “Start stack after upgrade”) Please check <strong>Firmware Upgrade Services Binary Table</strong> for Install@ parameter depending of the binary. (<strong>optional</strong>: activate “Anti-Rollback” on downloaded binary) If you need to perform FUS related manipulations, you always need to START the FUS in case the FUS is not running.</li>
</ul></li>
</ul>
<p><mark>How to compute available flash size </mark></p>
<ul>
<li><p>The default linker file is provided in [\Drivers\CMSIS\Device\ST32WBxx\Source\Templates].</p>
<p>The maximum flash memory that can be used by the application is up to the Secure Flash Start Address (SFSA) that can be read from the option byte.</p>
<p>The <strong>ICFEDIT_region_ROM_end</strong> in the linker can be modified with a value up to : (0x08000000 + (SFSA << 11)) - 1 considering minimum CPU secure area size is one sector (2kBytes).</p></li>
<li><p><strong>Example</strong>: When the SFSA option byte is set to 0x37, the maximum value to be used for __ICFEDIT_region_ROM_end is 0x0801B800 – which is 110kB of flash</p></li>
<li><p><strong>Note</strong>: The SFSA option byte can only be set by the CPU2. The user cannot modify that value.</p></li>
</ul>
</div>
<div class="col-sm-12 col-lg-8">
<h1 id="update-history">Update History</h1>
<div class="collapse">
<input type="checkbox" id="collapse-section4" checked aria-hidden="true"> <label for="collapse-section4" aria-hidden="false">V1.12.1 / 12-July-2021</label>
<div>
<h2 id="main-changes">Main Changes</h2>
<p><strong>Associated changes in Wireless Coprocessor Binary</strong>:</p>
<ul>
<li>BLE:
<ul>
<li>ID 110164 : Update BLE stack to avoid BLE link loss in case of Flash Erase while BLE RF is in process</li>
</ul></li>
</ul>
<p><strong>Wireless Coprocessor Binary Table</strong>: Provides Install address for the targeted binary to be used in flash procedure via SWD/JTAG.</p>
<table>
<thead>
<tr class="header">
<th>Wireless Coprocessor Binary</th>
<th>stm32wb1x(320K)</th>
<th>Version</th>
<th>Date</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>stm32wb1x_BLE_HCILayer_fw.bin</td>
<td>0x08033000</td>
<td>V1.12.1<span class="icon-st-update"></span></td>
<td>07/12/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_HCI_AdvScan_fw.bin</td>
<td>0x0803C800</td>
<td>V1.12.1<span class="icon-st-update"></span></td>
<td>07/12/2021</td>
</tr>
<tr class="odd">
<td>stm32wb1x_BLE_LLD_fw.bin</td>
<td>0x0803F800</td>
<td>V1.12.0<span class="icon-st-unchanged"></span></td>
<td>05/27/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_Stack_basic_fw.bin</td>
<td>0x08021800</td>
<td>V1.12.1<span class="icon-st-update"></span></td>
<td>07/12/2021</td>
</tr>
<tr class="odd">
<td>stm32wb1x_BLE_Stack_full_fw.bin</td>
<td>0x0801C000</td>
<td>V1.12.1<span class="icon-st-update"></span></td>
<td>07/12/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_Stack_light_fw.bin</td>
<td>0x08028000</td>
<td>V1.12.1<span class="icon-st-update"></span></td>
<td>07/12/2021</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="collapse">
<input type="checkbox" id="collapse-section3" aria-hidden="true"> <label for="collapse-section3" aria-hidden="false">V1.12.0 / 17-June-2021</label>
<div>
<h2 id="main-changes-1">Main Changes</h2>
<p><strong>Associated changes in Wireless Coprocessor Binary</strong>:</p>
<ul>
<li>BLE:
<ul>
<li>Introducing following new binary: <strong>stm32wb1x_BLE_Stack_basic_fw.bin</strong></li>
<li>The command “ACI_GAP_START_NAME_DISCOVERY_PROC” will be deprecated on next STM32Cube_FW_WB release v1.13.0</li>
<li>ID 73463 : Additional Beacon Feature support<br />
</li>
<li>ID 98146 : The Command SHCI_C2_DEBUG_Init() is updated to disable low power mode on CPU2 if necessary</li>
<li>ID 100904 : Remove ability to read the initial static random address<br />
</li>
<li>ID 102435 : Add BLE Basic stack support. New M0 binary (removal of following features are removed from Full BLE Stack: “L2Cap Connection - oriented channel, Additional beacon, Some HCI interface features, Phy update (2Mb/s), Direct test mode” )</li>
<li>ID 104807 : Fix issue after the white list clearing for device also in resolving list. The device was seen as it was still in the white list.</li>
<li>ID 104813 : Deliberately corrupted scanning PDU makes the STM32WB crash: fix consists in filtering the parameters whose value can exceed the allowed range</li>
<li>ID 105676 : Critical code optimized in timing during execution<br />
</li>
<li>ID 106277 : Support of HCI_LE_SET_ADVERTISING_DATA command on Basic Stack</li>
<li>ID 106287 : HCI_HOST_BUFFER_SIZE returns Command Complete. Previous release, it was HCI command status event</li>
<li>ID 106290 : Enabling the GAP privacy enables the following events:
<ul>
<li>LE Data Length Change Event</li>
<li>LE PHY Update Complete Event</li>
</ul></li>
</ul></li>
</ul>
<p><strong>Wireless Coprocessor Binary Table</strong>: Provides Install address for the targeted binary to be used in flash procedure via SWD/JTAG.</p>
<table>
<thead>
<tr class="header">
<th>Wireless Coprocessor Binary</th>
<th>stm32wb1x(320K)</th>
<th>Version</th>
<th>Date</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>stm32wb1x_BLE_HCILayer_fw.bin</td>
<td>0x08033000</td>
<td>V1.12.0<span class="icon-st-update"></span></td>
<td>05/31/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_HCI_AdvScan_fw.bin</td>
<td>0x0803C800</td>
<td>V1.12.0<span class="icon-st-update"></span></td>
<td>05/31/2021</td>
</tr>
<tr class="odd">
<td>stm32wb1x_BLE_LLD_fw.bin</td>
<td>0x0803F800</td>
<td>V1.12.0<span class="icon-st-update"></span></td>
<td>05/27/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_Stack_basic_fw.bin</td>
<td>0x08021800</td>
<td>V1.12.0<span class="icon-st-add"></span></td>
<td>05/31/2021</td>
</tr>
<tr class="odd">
<td>stm32wb1x_BLE_Stack_full_fw.bin</td>
<td>0x0801C000</td>
<td>V1.12.0<span class="icon-st-update"></span></td>
<td>05/31/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_Stack_light_fw.bin</td>
<td>0x08028000</td>
<td>V1.12.0<span class="icon-st-update"></span></td>
<td>05/31/2021</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="collapse">
<input type="checkbox" id="collapse-section2" aria-hidden="true"> <label for="collapse-section2" aria-hidden="false">V1.11.1 / 23-March-2021</label>
<div>
<h2 id="main-changes-2">Main Changes</h2>
<p><strong>Associated changes in Wireless Coprocessor Binary</strong>:</p>
<ul>
<li>BLE :
<ul>
<li>ID 102917 : Apply “VCO patch” for all packages [STM32WB15/STM32WB10] to solve “RX path issue” at low temperatures on Slow corners</li>
<li>ID 102000 : [STM32WB55/STM32WB15]: Default CFG_BLE_MAX_CONN_EVENT_LENGTH value updated for all BLE examples</li>
<li>ID 99680 : 2nd link secure fail if master database is clear during 1st link connection</li>
<li>ID 101346 : ACI_GAP_BOND_LOST_Event timeout does not work if ALLOW rebond not sent</li>
<li>ID 101921 : PTS issue ticket done CASE0070853: destination channel ID value above 1000 should be allowed and test passed</li>
<li>ID 94289 ,ID 102395 ,ID 100425 : BLE_Ota application improvments (SBSFU ready, Flash driver use, SEM7 flash activity control)</li>
</ul></li>
<li>install address updated</li>
</ul>
<p><strong>Wireless Coprocessor Binary Table</strong>: Provides Install address for the targeted binary to be used in flash procedure via SWD/JTAG.</p>
<table>
<thead>
<tr class="header">
<th>Wireless Coprocessor Binary</th>
<th>stm32wb1x(320K)</th>
<th>Version</th>
<th>Date</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>stm32wb1x_BLE_HCILayer_fw.bin</td>
<td>0x08032800</td>
<td><strong>v1.11.1</strong></td>
<td>03/22/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_HCI_AdvScan_fw.bin</td>
<td>0x0803C000</td>
<td><strong>v1.11.1</strong></td>
<td>03/22/2021</td>
</tr>
<tr class="odd">
<td>stm32wb1x_BLE_LLD_fw.bin</td>
<td>0x0803E800</td>
<td><strong>v1.11.1</strong></td>
<td>03/22/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_Stack_full_fw.bin</td>
<td>0x0801C000</td>
<td><strong>v1.11.1</strong></td>
<td>03/22/2021</td>
</tr>
<tr class="odd">
<td>stm32wb1x_BLE_Stack_light_fw.bin</td>
<td>0x08028000</td>
<td><strong>v1.11.1</strong></td>
<td>03/22/2021</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="collapse">
<input type="checkbox" id="collapse-section1" aria-hidden="true"> <label for="collapse-section1" aria-hidden="false">V1.11.0 / 12-February-2021</label>
<div>
<h2 id="main-changes-3">Main Changes</h2>
<p><strong>Associated changes in Wireless Coprocessor Binary</strong>:</p>
<ul>
<li>Initial version of the binaries.</li>
</ul>
<p><strong>Wireless Coprocessor Binary Table</strong>: Provides Install address for the targeted binary to be used in flash procedure via SWD/JTAG.</p>
<table>
<thead>
<tr class="header">
<th>Wireless Coprocessor Binary</th>
<th>stm32wb1x(320K)</th>
<th>Version</th>
<th>Date</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>stm32wb1x_BLE_HCILayer_fw.bin</td>
<td>0x08032000</td>
<td><strong>v1.11.0</strong></td>
<td>12/02/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_HCI_AdvScan_fw.bin</td>
<td>0x0803B800</td>
<td><strong>v1.11.0</strong></td>
<td>12/02/2021</td>
</tr>
<tr class="odd">
<td>stm32wb1x_BLE_LLD_fw.bin</td>
<td>0x0803E000</td>
<td><strong>v1.11.0</strong></td>
<td>12/02/2021</td>
</tr>
<tr class="even">
<td>stm32wb1x_BLE_Stack_full_fw.bin</td>
<td>0x0801B800</td>
<td><strong>v1.11.0</strong></td>
<td>12/02/2021</td>
</tr>
<tr class="odd">
<td>stm32wb1x_BLE_Stack_light_fw.bin</td>
<td>0x08027800</td>
<td><strong>v1.11.0</strong></td>
<td>12/02/2021</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<footer class="sticky">
<p>For complete documentation on STM32WBxx, visit: [<a href="http://www.st.com/stm32wb">www.st.com/stm32wb</a>]</p>
<em>This release note uses up to date web standards and, for this reason, should not be opened with Internet Explorer but preferably with popular browsers such as Google Chrome, Mozilla Firefox, Opera or Microsoft Edge.</em>
</footer>
</body>
</html>
|
