s132_nrf52_3.x.x release notes
Introduction to the s132_nrf52_3.x.x release notes
These release notes describe the changes in the s132_nrf52 from version to version, up to versions 3.x.x.
The release notes are intended to list all relevant changes in a given version. They are kept brief, to make it easy to get the overview. More
details regarding changes and new features may be found in the s13x_nrf5x migration document (normally available for major releases only).
Issue numbers in parentheses are for internal use, and should be disregarded by the customer.
Copyright (c) Nordic Semiconductor ASA. All rights reserved.
s132_nrf52_3.1.0
This version of the SoftDevice improves robustness to bit errors in received packets and adds some minor features compared to version
3.0.0. Memory requirements and functional performance are equivalent to version 3.0.0. Refer to the release notes of version 3.0.0 for
further information.
New functionality
GAP
It is now possible to disable and enable slave latency on an active peripheral link. A new option in the GAP options API has
been added for this (DRGN-7831).
It is now possible to disable the initiation of DLE procedure. A new option in the GAP options API has been added for this
(DRGN-8248).
It is now possible to respond with the configured ATT_MTU size during DLE procedure. Default behavior is to respond with
the currently used ATT_MTU size. A new option in the GAP options API has been added for this (DRGN-8335).
It is now possible to completely disable the DLE feature. A new option in the GAP options API has been added for this
(DRGN-8172).
A new compatibility mode has been added to enable interoperability with central devices that may initiate version exchange
and feature exchange control procedures in parallel (DRGN-8232).
Changes
LL
The SoftDevice will no longer reject LL_LENGTH_REQ and LL_LENGTH_RSP with parameters which are out of range
according to Bluetooth 4.2 specification (DRGN-7872).
Bug fixes
Fixed an issue where bit errors in the length field of an encrypted packet caused the packet to be interpreted as longer than was
sent by the peer (DRGN-7898). This issue could have manifested in the following ways:
SoftDevice memory buffer corruption which could lead to an assert or incorrect behavior.
SoftDevice may send a packet with an incorrect MIC field leading to a disconnect from the peer.
Limitations
SoftDevice
If Radio Notifications are enabled, flash write and flash erase operations initiated through the SoftDevice API will be notified
to the application as Radio Events (FORT-809).
Synthesized low frequency clock source is not tested or intended for use with the BLE stack.
Applications must not modify the SEVONPEND flag in the SCR register when running in priority level 1 as this can lead to
undefined behavior.
If the application uses TIMER0 inside a timeslot (scheduled with the Radio Timeslot API), INTENSET for TIMER0 must be
cleared before the timeslot ends (DRGN-7776).
LL
The peripheral role has priority over the central role when it comes to keeping the links alive.
GAP
A broadcaster and a scanner cannot both be active if there are 8 connections established (DRGN-6543).
GATTS
To conform to the Bluetooth specification, there shall not be a secondary service that is not referenced somehow by a
primary service. The SoftDevice does not enforce this (DRGN-906, DRGN-2260).
Known Issues
If is called with set to , an invalid function pointer, or a pointer to a returningsd_softdevice_enable() fault_handler NULL
function, the behavior will be undefined (DRGN-7122).
If Connection Event Length Extension is enabled, the Radio Notification may be suppressed between connection events
(DRGN-7687).
When returns an error code, the scanner may be stopped . To ensure the scanner is in asd_ble_gap_connect() (DRGN-7679)
known state, should be used to stop the scanner when returns an errorsd_ble_gap_scan_stop() sd_ble_gap_connect()
code.
s132_nrf52_3.0.0
The main new features of this major version, compared to the 2.0.1 version, are Configurable ATT_MTU, LE Data Packet Length Extension
(DLE), LL Privacy and LE Ping. The updates from the previous alpha version (3.0.0-2.alpha) are minor changes and bug fixes.
Notes:
This release has changed the Application Programmer Interface (API), requiring applications to be recompiled.
The memory requirements of the SoftDevice have changed.
SoftDevice properties
An updated SoftDevice Specification document is available at .http://infocenter.nordicsemi.com/
The combined MBR and SoftDevice memory requirements for this version are as follows:
Flash: ( bytes).124 kB 0x1F000
RAM: ( bytes) (minimum required memory - actual requirements are dependent upon the configuration6.43 kB 0x19C0
chosen at time).sd_ble_enable()
New functionality
All new features have been introduced in alpha versions 3.0.0-1.alpha and 3.0.0-2.alpha. See the release notes for those versions
below.
Changes
BLE
The length of connection events is now set to fit the configured maximum LL packet size during connection setup
(DRGN-7672). In 3.0.0-2.alpha, the connection event length was increased after a DLE procedure, which would lead to
collisions with other established central links. This change affects the recommended connection intervals documented in
the SDS.
Connection Event Length Extension (enabling extra packets to be sent per connection interval) is now disabled by default
and a new API has been added to enable/disable this feature (DRGN-7562).
GAP
The Tx power level configuration API has been updated to support the +3dBm power level (DRGN-7644).
Bug fixes
Fixed an issue where MIC failures may have happened if the LL payload length is increased to more than 27 bytes on an encrypted
link (DRGN-7779).
Fixed an issue where some LL payload bytes may have been lost if the LL payload length was increased to more than 27 bytes and
there was a CRC error (DRGN-7777).
Fixed an issue where the authenticated payload timeout event ( )BLE_GAP_TIMEOUT_SRC_AUTH_PAYLOAD was not triggered for a
link if the link was blocked multiple times during the authenticated payload timeout expiration (DRGN-7769).
Fixed an issue where the SoftDevice may have asserted if DLE and Radio Notification were used together (DRGN-7710).
FIxed an issue where the SoftDevice may have asserted during the ATT_MTU exchange procedure (DRGN-7703).
Fixed an issue where pairing with passkey entry would fail if the keypress notification was received in the same connection event as
the pairing response (DRGN-7680).
Limitations
SoftDevice
If Radio Notifications are enabled, flash write and flash erase operations initiated through the SoftDevice API will be notified
to the application as Radio Events (FORT-809).
Synthesized low frequency clock source is not tested or intended for use with the BLE stack.
Applications must not modify the SEVONPEND flag in the SCR register when running in priority level 1 as this can lead to
undefined behavior.
If the application uses TIMER0 inside a timeslot (scheduled with the Radio Timeslot API), INTENSET for TIMER0 must be
cleared before the timeslot ends (DRGN-7776).
LL
The peripheral role has priority over the central role when it comes to keeping the links alive.
GAP
A broadcaster a scanner cannot both be active if there are 8 connections established (DRGN-6543).and
GATTS
To conform to the Bluetooth specification there shall not be a secondary service that is not referenced somehow by a
primary service. The SoftDevice does not enforce this (DRGN-906, DRGN-2260).
Known Issues
If is called with set to , an invalid function pointer, or a pointer to a returningsd_softdevice_enable() fault_handler NULL
function, the behavior will be undefined (DRGN-7122).
If Connection Event Length Extension is enabled, the Radio Notification may be suppressed between connection events
(DRGN-7687).
When returns an error code, the scanner may be stopped . To ensure the scanner is in asd_ble_gap_connect() (DRGN-7679)
known state, should be used to stop the scanner when returns an errorsd_ble_gap_scan_stop() sd_ble_gap_connect()
code.
