Blogs - All Comments

RE: Frequently asked questions for the nPM1300 and nPM1304

Tomi Koskela — Mon, 11 May 2026 09:09:27 GMT

Thanks for your enquiry. It depends on the compiler/tools what it would actually require. Please make a devzone ticket with more details and we can look into it.

RE: What’s new in nRF Connect SDK v3.3.0?

Sebastian Viviani — Thu, 07 May 2026 15:34:32 GMT

[mention:a0ff8ace14ec40dcaa083b2ddce0cfef:e9ed411860ed4f2ba0265705b8793d05] I can see the files for both the nRF54LS05A and nRF54LS05B in the SDK, and boards seem to be picked correctly by VS Code too, I guess it's a local error at your setup?

RE: Introducing the RISC-V coprocessor of the nRF54L Series

ujur007 — Wed, 29 Apr 2026 18:03:14 GMT

Hello!, I have a custom PCB where I have meshed up the spi00 pins by interchanged MISO/MOSI lines. Can RISC-V processor come to rescue? .

RE: What’s new in nRF Connect SDK v3.3.0?

Stefan Schmidt — Mon, 27 Apr 2026 07:13:59 GMT

The nRF54LS05A does not seem to be supported?!?

RE: What’s new in nRF Connect SDK v3.3.0?

drollinger — Fri, 24 Apr 2026 15:44:48 GMT

I have spent time recently developing a complete zephyr rtos development environment on a raspberry pi, obvious adavantages: https://github.com/cydrollinger1968/Complete-Zephyr-Development-from-Raspberry-Pi . I wonder if the SDK could be ported to the RPI like this work?

RE: Meet the Axon NPU: Accelerating Edge AI on the nRF54L Series

maxxlife — Thu, 16 Apr 2026 07:55:20 GMT

I created an Axon NPU benchmark and measured about 4 MACs per cycle. Could an engineer please review my code and the benchmarking steps I used to confirm whether the method and result look correct? Details are here: https://www.hackster.io/maxxlife/nrf54l20b-axon-npu-benchmark-on-zephyr-9c1998

RE: What’s new in Bluetooth®︎ Core 6.2: An overview

Murad — Sat, 11 Apr 2026 14:37:55 GMT

@Joel Kauppo or anyone from Nordic,

I have a question regarding Google Find My Device / Find Hub SDK access.

We are developing an ultra-small BLE tag (MicroTag) under SONYROID Co., Ltd. (Project ID: 59106960746) and I need to understand the exact process to obtain the Find My Device SDK and API from Nordic.

Specifically:
1. What is the approval process? Do we need Google's approval first, or do we request from Nordic directly?
2. Is there a public API for backend to fetch location data, or is the location data only available to the end-user on their phone?
3. I already submitted a private ticket. Will Nordic provide the SDK access through that, or do I need to contact someone specific (e.g., Brian Ha)?

Any guidance would be greatly appreciated. Thank you!

RE: Frequently asked questions for the nPM1300 and nPM1304

boqin — Fri, 03 Apr 2026 08:13:22 GMT

my SoC is Cortex-M55,i want to use the fuel gauge algorithm,what should i do?

RE: Introducing the RISC-V coprocessor of the nRF54L Series

Sebastian Viviani — Wed, 01 Apr 2026 22:18:38 GMT

Hi Jack,
probably best to create a support ticket for this, as this seems to be something related to sysbuild.

RE: Evaluating Bluetooth®︎ Channel Sounding with our open-source Android app on Google Pixel 10

NickinFrance — Tue, 31 Mar 2026 13:42:16 GMT

I note that the above states " and the number of Channel Sounding antenna paths must be configured to 2". Does that mean that the Pixel 10 has dual Bluetooth antennas, since I believe the DK only has a single antenna?

RE: Meet the Axon NPU: Accelerating Edge AI on the nRF54L Series

watchwrestlingae — Tue, 31 Mar 2026 10:04:55 GMT

Will LiteRT support be available for non-NPU models like the nRF54L15 as well? If yes, is there any timeline for when we can expect it? watch wrestling.

RE: Meet the Axon NPU: Accelerating Edge AI on the nRF54L Series

StevenBos — Sat, 28 Mar 2026 01:17:01 GMT

Will LiteRT support also come to non-NPU models like the nRF54L15? If so, when can this be expected? Robin M Saltnes

RE: Introducing the RISC-V coprocessor of the nRF54L Series

Jack jpeng — Thu, 26 Mar 2026 09:26:56 GMT

Hello! I’m currently looking to use the M33 on the nRF54L15 for range-finding calculations, whilst the RISC-V VPR coprocessor handles some feature processing. I’m currently using NCS v3.2.1, and I’ve built two images. The one below is for the RISC-V VPR coprocessor; here is the CMake file for RISV.

# uwb_merge/sysbuild.cmake
cmake_minimum_required(VERSION 3.20.0)

ExternalZephyrProject_Add(
    APPLICATION cpuflpr
    SOURCE_DIR  ${APP_DIR}/cpuflpr
    BOARD       nrf54l15dk/nrf54l15/cpuflpr
    BUILD_ONLY  y                          
)

add_dependencies(${DEFAULT_IMAGE} cpuflpr)

Currently, the PM script continues to add `cpuflpr` to the `--images` list, even though there is no corresponding entry in `partitions.yml`, causing the Python script to crash. (The `BUILD_ONLY y` option does not take effect in the `partition_manager.cmake` file for NCS v3.2.1.) The purpose of `BUILD_ONLY y` is to allow sysbuild to compile this image, but not to hand it over to the Partition Manager for management; instead, cpuapp is responsible for loading it into SRAM and booting it at runtime. Is there a good solution to fix this?

RE: Implementing MQTT over Wi-Fi on the nRF7002 Development Kit

SulikS — Fri, 20 Mar 2026 17:35:41 GMT

Hi guys,
Could somebody please provide the information about the power consumption for this example? Perhaps somebody can measure it with the power profiler kit?
I would be very grateful.

RE: DECT NR+: A technical dive into non-cellular 5G

ErMaqsood — Tue, 17 Mar 2026 16:25:36 GMT

Hi Heidi,

Greeting for the day.

I appreciate your support.

I currently have a DECT NR+ setup running on the nRF9151, based on the HELLO DECT PHY sample using nRF Connect SDK v3.3.0preview2. I am seeking your guidance on how to route data across a small NR+ cluster, specifically in the following topology:

[cluster1] Leaf (Node1) ⇄ Router (Relay) ⇄ Leaf (Node2) [cluster2]

Could you please advise on the correct approach, configuration, or APIs required to enable multi‑hop data routing between Leaf nodes through the Router?

Thank you.