|
| 1 | +s115_9.0.0-4.prototype |
| 2 | +====================== |
| 3 | + |
| 4 | +This version is a major release, providing support for nRF54L series devices. |
| 5 | + |
| 6 | +Notes: |
| 7 | + |
| 8 | +- This release has changed the API. This requires changes to applications. |
| 9 | +- The release notes list changes since s115_9.0.0-3.prototype. |
| 10 | + |
| 11 | + |
| 12 | +SoftDevice properties |
| 13 | +--------------------- |
| 14 | + |
| 15 | +* This SoftDevice variant is compatible with |
| 16 | + nRF54L05, nRF54L10, and nRF54L15. |
| 17 | + |
| 18 | +* The SoftDevice memory requirements for this version are as follows: |
| 19 | + |
| 20 | + * NVM: **107.0 kB** (0x1AC00 bytes). |
| 21 | + |
| 22 | + * RAM: **4.9 kB** (0x1380 bytes). |
| 23 | + This is the minimum required memory. The actual requirements depend on the |
| 24 | + configuration chosen at ``sd_ble_enable()`` time. |
| 25 | + |
| 26 | + * Call stack: The SoftDevice uses a call stack combined with the application. |
| 27 | + The worst-case stack usage for the SoftDevice is |
| 28 | + **1.8 kB** |
| 29 | + (0x700 bytes). Application writers should ensure |
| 30 | + that enough stack space is reserved to cover the worst-case SoftDevice call |
| 31 | + stack usage combined with the worst-case application call stack usage. |
| 32 | + |
| 33 | +* SoftDevice base address: |
| 34 | + |
| 35 | + * nRF54L05: 0x062000 (``s115_nrf54l05_9.0.0-4.prototype_softdevice.hex``). |
| 36 | + |
| 37 | + * nRF54L10: 0x0E2000 (``s115_nrf54l10_9.0.0-4.prototype_softdevice.hex``). |
| 38 | + |
| 39 | + * nRF54L15: 0x162000 (``s115_nrf54l15_9.0.0-4.prototype_softdevice.hex``). |
| 40 | + |
| 41 | +* The Firmware ID of this SoftDevice is 0x309B. |
| 42 | + |
| 43 | +New Features |
| 44 | +------------- |
| 45 | + |
| 46 | +Changes |
| 47 | +------- |
| 48 | + |
| 49 | +* GAP |
| 50 | + |
| 51 | + * The SoftDevice no longer enforces the spec-required 1 second interval between channel map updates (``ble_gap_opt_ch_map_t``) (DRGN-26253). |
| 52 | + |
| 53 | + |
| 54 | +Limitations |
| 55 | +----------- |
| 56 | + |
| 57 | +* SoftDevice |
| 58 | + |
| 59 | + * If Radio Notifications are enabled, flash write and flash erase operations |
| 60 | + initiated through the SoftDevice API will be notified to the application as |
| 61 | + Radio Events (DRGN-5197). |
| 62 | + |
| 63 | + * Synthesized low frequency clock source is not tested or intended for use |
| 64 | + with the Bluetooth LE stack. |
| 65 | + |
| 66 | + * Applications must not modify the SEVONPEND flag in the SCR register when |
| 67 | + running in priority levels higher than 6 (priority level numerical values |
| 68 | + lower than 6) as this can lead to undefined behavior. |
| 69 | + |
| 70 | + * The SoftDevice may generate several events when connected, based on peer |
| 71 | + actions, meaning without previous action from the application. The |
| 72 | + ``BLE_GAP_EVT_PHY_UPDATE_REQUEST`` event, for instance, is generated when a |
| 73 | + connected peer sends a Phy Update Request, even when an application does not |
| 74 | + include logic to change PHY. There are several such events that may require |
| 75 | + action from an application if they are received. For more information, see the |
| 76 | + ``sd_ble_enable()`` API in SoftDevice. |
| 77 | + |
| 78 | + * Configuring multiple connection configurations (see ``ble_conn_cfg_t::conn_cfg_tag``) is not supported (DRGN-23839). |
| 79 | + |
| 80 | +* GATT |
| 81 | + |
| 82 | + * To conform to the Bluetooth Core Specification, there shall be no |
| 83 | + secondary service that is not referenced somehow by a primary service. The |
| 84 | + SoftDevice does not enforce this (DRGN-906). |
| 85 | + |
| 86 | +Known Issues |
| 87 | +------------ |
| 88 | + |
| 89 | +* SoftDevice |
| 90 | + |
| 91 | +* LL |
| 92 | + |
| 93 | + * If the application adds an all zeroes IRK with the |
| 94 | + ``sd_ble_gap_device_identities_set()``, it will be treated as a valid entry |
| 95 | + in the device identity list. An all zeroes IRK is invalid and must not be |
| 96 | + added (DRGN-9083). |
0 commit comments