Unable to use CONFIG_BT_LL_SOFTDEVICE_PERIPHERAL on nRF54L

Hi,

I’m trying to use the SoftDevice Controller in peripheral-only mode on the nRF54L15 (using NCS 3.0.1), but I can’t get it to build with `CONFIG_BT_LL_SOFTDEVICE_PERIPHERAL=y`.

OS: Windows 11
NCS version: 3.0.1
Board: nRF54L15dk


Example I’m using: github.com/.../l5_e2_sol

The build fails with the following error:

CMake Error at C:/ncs/v3.0.1/nrfxlib/softdevice_controller/CMakeLists.txt:28 (message):
  This combination of SoC and floating point ABI is notsupported by the
  SoftDevice Controller lib.

I’m not entirely sure what’s causing this, but it seems the peripheral-only SoftDevice Controller might be built for soft ABI, while the nRF54L05 SoC and toolchain use a hard-float ABI by default. If that’s the case, I assume that’s why it only builds with `CONFIG_BT_LL_SOFTDEVICE_MULTIROLE`.

I tested the same application on the nRF52DK (nRF52832), and it builds fine with the peripheral-only controller. It also results in noticeably lower flash and RAM usage (~16 KB and ~1.2 KB savings compared to the multirole controller), which would be very useful for low-footprint BLE peripheral applications on the nRF54L05.

Is this a known limitation for the nRF54L series, or is there a way to use the peripheral-only controller variant on this SoC? We’d still like to take advantage of the pre-certified Bluetooth Host + SoftDevice Controller stack provided in the official NCS releases.

Thanks in advance.

Best regards,
Tadej

Parents Reply
  • Hi Sigurd,

    Thank you for the quick reply. That clarifies everything.

    I noticed that nRF Connect SDK v3.1.0-preview3 is already available. Since we're getting close to certification and production, do you know when the official v3.1.0 release (with certified Host and SoftDevice Controller subsystems for the nRF54L05) will be available, along with the corresponding Bluetooth Declaration IDs (DNs)?

    Best regards,
    Tadej

Children
Related