You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: softdevice_controller/CHANGELOG.rst
+18-13Lines changed: 18 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ Changelog
9
9
10
10
All notable changes to this project are documented in this file.
11
11
12
-
Master branch
13
-
*************
12
+
nRF Connect SDK v1.5.0
13
+
**********************
14
14
15
15
Added
16
16
=====
@@ -45,17 +45,21 @@ Bugfixes
45
45
* Fixed an issue where the LL control procedures LE start encryption and LE connection parameter update could not be initiated at the same time (DRGN-11963).
46
46
* Fixed an issue where the generation of QoS Connection event was not disabled after an HCI reset (DRGN-15291).
47
47
48
-
Known issues and limitations
49
-
============================
48
+
Limitations
49
+
===========
50
+
51
+
The RSSI value reported by the Softdevice Controller is the raw value from the radio peripheral.
52
+
Some SoCs require compensation of the RSSI value based on the chip temperature.
53
+
See the Errata document for the respective SoC for detailed information.
50
54
51
-
* The RSSI value reported by the Softdevice Controller is the raw value from the radio peripheral.
52
-
Some SoCs require compensation of the RSSI value based on the chip temperature.
53
-
See the Errata document for the respective SoC for detailed information.
55
+
For the nRF53 Series, you can retrieve the chip temperature by reading the value of the temperature peripheral on the network core.
56
+
To do this with the SoftDevice Controller, use the Zephyr HCI VS Read Chip Temperature command (``BT_HCI_OP_VS_READ_CHIP_TEMP``).
57
+
58
+
For the nRF52 Series, you can use the Zephyr sensor API instead of the HCI command to retrieve the chip temperature.
54
59
55
-
For the nRF53 Series, you can retrieve the chip temperature by reading the value of the temperature peripheral on the network core.
56
-
To do this with the SoftDevice Controller, use the Zephyr HCI VS Read Chip Temperature command (``BT_HCI_OP_VS_READ_CHIP_TEMP``).
57
-
For the nRF52 Series, you can use the Zephyr sensor API instead of the HCI command to retrieve the chip temperature.
58
-
You can then use the retrieved temperature value to compensate the raw RSSI value, following the workaround in the Errata document.
60
+
You can then use the retrieved temperature value to compensate the raw RSSI value, following the workaround in the Errata document.
61
+
62
+
See the :ref:`nrf:known_issues` page in |NCS| for the list of known issues and limitations for this release.
59
63
60
64
nRF Connect SDK v1.4.0
61
65
**********************
@@ -208,6 +212,7 @@ nRF Bluetooth LE Controller 0.3.0-3.prealpha
208
212
209
213
Added
210
214
=====
215
+
211
216
* Added support for nRF52833.
212
217
213
218
Bugfixes
@@ -271,7 +276,7 @@ nRF Bluetooth LE Controller 0.2.0-4.prealpha
271
276
nRF Bluetooth LE Controller 0.2.0-3.prealpha
272
277
********************************************
273
278
274
-
* Fixed a bug causing an assert in ``ble_controller_soc.c:29``.
279
+
Fixed a bug causing an assert in ``ble_controller_soc.c:29``.
275
280
276
281
nRF Bluetooth LE Controller 0.2.0-2.prealpha
277
282
********************************************
@@ -300,7 +305,7 @@ Added
300
305
Bugfixes
301
306
========
302
307
303
-
* Fixed an issue in HCI control flow that severely limited Bluetooth LE throughput.
308
+
Fixed an issue in HCI control flow that severely limited Bluetooth LE throughput.
0 commit comments