Nordic Q&A - Recent Threads

NRF Mesh Android Library, return device key even if provisioning fails

jm_solar — Fri, 05 Jun 2026 18:16:22 GMT

We use the NRF Mesh Android Library (and are developing with iOS version as well). An issue that we are running into on a small number of devices is that the library things provisioning failed, but the device being provisioned thinks it succeeded. This leaves the device provisioned with a device key that we cannot access, as the library does not provide a way to access the device key unless provisioning succeeded.

We are addressing this on the firmware side, but more generally as a solution we would like to record every device key that we attempted to provision a device with so that we can attempt recovery from the app using these keys. Otherwise these devices end up as RMAs which is very costly when all we need to do is connect to them with the device key and reset them.

As far as we can tell, this is not currently possible with the NRF Mesh Libraries - is this correct?

Can this feature be added so that provisioning can be made more resilient?

RE: NRF Mesh Android Library, return device key even if provisioning fails

lennyfrank — Sat, 13 Jun 2026 10:18:53 GMT

If provisioning fails on the app side but succeeds on the device, is there any supported way to retrieve the device key afterward, or is the device effectively unrecoverable unless it has a separate reset mechanism? FNF

trying to send and receive the data through can bus moduler using with nrf9160 and esp32 controller (using SPI)

Vivek01 — Thu, 11 Jun 2026 19:51:18 GMT

Hi,

can anyone help me with this situations that i'm facing from a 1 month so i'm connecting esp32 controller to seengreat RS485 Dual CAN Bus moduler and the other hand i'm connecting nrf9160 to seengreat RS485 Dual CAN Bus moduler but i can't send or receive any messages through this and i attach the both screenshot from nrf serial terminal and from esp32 controller terminal and also i attach my overlay code and my both project files. i tried with 125,250,500 KBPS bus speed but i didn't make it and this can bus moduler have 16MHZ and it has 120 ohm resister attached with the moduler and i tried spi-max-frequency = <125000>,<250000>, <500000>, <1000000>.[View:/cfs-file/__key/communityserver-discussions-components-files/4/WACS-_2800_2_2900_.zip:320:240][View:/cfs-file/__key/communityserver-discussions-components-files/4/WACS_5F00_esp32-_2800_2_2900_.zip:320:240]

here is my overlay file code

// can mcp2515 drivers overlay

&pinctrl {

spi3_default: spi3_default {

group1 {

psels = <NRF_PSEL(SPIM_SCK, 0, 13)>,

<NRF_PSEL(SPIM_MOSI, 0, 11)>,

<NRF_PSEL(SPIM_MISO, 0, 12)>;

};

spi3_sleep: spi3_sleep {

group1 {

psels = <NRF_PSEL(SPIM_SCK, 0, 13)>,

<NRF_PSEL(SPIM_MOSI, 0, 11)>,

<NRF_PSEL(SPIM_MISO, 0, 12)>;

low-power-enable;

};

/ {

chosen {

zephyr,canbus = &mcp2515;

};

&spi3 {

compatible = "nordic,nrf-spim";

status = "okay";

pinctrl-0 = <&spi3_default>;

pinctrl-1 = <&spi3_sleep>;

pinctrl-names = "default", "sleep";

cs-gpios = <&gpio0 25 GPIO_ACTIVE_LOW>;

mcp2515: can@0 {

compatible = "microchip,mcp2515";

reg = <0>;

spi-max-frequency = <250000>;

int-gpios = <&gpio0 17 GPIO_ACTIVE_LOW>;

osc-freq = <16000000>;

bus-speed = <250000>;

status = "okay";

};

// UART overlay

&uart2 {

status = "okay";

current-speed = <115200>;

};

i spend too much time on this and still didn't get anything from this so please help me to get through with this and what else i can do for debugging cuz i change the wires many times and now i order new can bus moduler to get confirmation about that is the moduler don't have the problem or what, i don't know

thanks
vivek

RE: trying to send and receive the data through can bus moduler using with nrf9160 and esp32 controller (using SPI)

Vidar Berg — Sat, 13 Jun 2026 09:40:18 GMT

Hi Vivek,

I looked at the specification for the CAN module and saw that it required a min. voltage of 3.3v. The VDD IO configuration DK is covered in the nRF9160 DK User Guide here: https://docs.nordicsemi.com/r/bundle/ug_nrf9160_dk/page/ug/nrf91_dk/hw_description/power_sources_vdd.html. From this you can see that you will either need an external VDD IO supply to reach 3.3v, or use an external level shifter to communicate with the module. It is also important that you carefully review the specification for the module you are using to see if there may be other issue apart from the incompatible voltage level.

RE: Overlay causes build errors

Jam Alan — Sat, 13 Jun 2026 07:47:02 GMT

Are you talking about a Salesforce overlay team/territory model and encountering deployment or validation errors? speed stars

Overlay causes build errors

Lars Fredrik — Tue, 16 May 2023 23:40:23 GMT

Hei!

I can't seem to get my devicetree overlay to properly work. I have an external LED and two buttons connected to the GPIO ports mentioned in the overlay, and I've tried removing the nodes that causes multiple nodes to wanna use the same pins (for example, I had to move the UART pins).

Below is the build error I get when doing a pristine build, and under that again is the device overlay. Any help is appreciated! :)

Build log:

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:1ad783ea-0c5d-466c-9116-65fa10069b9b:type=text&text=%0D%0A%0D%0A--%20west%20build%3A%20generating%20a%20build%20system%0D%0ALoading%20Zephyr%20default%20modules%20%28Zephyr%20base%29.%0D%0A--%20Application%3A%20A%3A%2Fbachelornordic%2Fmain_unit%0D%0A--%20Found%20Python3%3A%20A%3A%2Fnordicsemi%2Ftoolchains%2Fv2.3.0%2Fopt%2Fbin%2Fpython.exe%20%28found%20suitable%20exact%20version%20%223.8.2%22%29%20found%20components%3A%20Interpreter%20%0D%0A--%20Cache%20files%20will%20be%20written%20to%3A%20A%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2F.cache%0D%0A--%20Zephyr%20version%3A%203.2.99%20%28A%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%29%0D%0A--%20Found%20west%20%28found%20suitable%20version%20%220.14.0%22%2C%20minimum%20required%20is%20%220.7.1%22%29%0D%0A--%20Board%3A%20nrf9160dk_nrf9160_ns%2C%20Revision%3A%200.7.0%0D%0A--%20Found%20host-tools%3A%20zephyr%200.15.2%20%28A%3A%2Fnordicsemi%2Ftoolchains%2Fv2.3.0%2Fopt%2Fzephyr-sdk%29%0D%0A--%20Found%20toolchain%3A%20zephyr%200.15.2%20%28A%3A%2Fnordicsemi%2Ftoolchains%2Fv2.3.0%2Fopt%2Fzephyr-sdk%29%0D%0A--%20Found%20Dtc%3A%20A%3A%2Fnordicsemi%2Ftoolchains%2Fv2.3.0%2Fopt%2Fbin%2Fdtc.exe%20%28found%20suitable%20version%20%221.4.7%22%2C%20minimum%20required%20is%20%221.4.6%22%29%20%0D%0A--%20Found%20BOARD.dts%3A%20A%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fboards%2Farm%2Fnrf9160dk_nrf9160%2Fnrf9160dk_nrf9160_ns.dts%0D%0A--%20Found%20devicetree%20overlay%3A%20a%3A%2Fbachelornordic%2Fmain_unit%2Fboards%2Fnrf9160dk_nrf9160_ns.overlay%0D%0Adevicetree%20error%3A%20a%3A%2Fbachelornordic%2Fmain_unit%2Fboards%2Fnrf9160dk_nrf9160_ns.overlay%3A102%20%28column%203%29%3A%20parse%20error%3A%20expected%20node%20name%2C%20property%20name%2C%20or%20%27%7D%27%0D%0ACMake%20Error%20at%20A%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fcmake%2Fmodules%2Fdts.cmake%3A231%20%28message%29%3A%0D%0A%20%20gen_defines.py%20failed%20with%20return%20code%3A%201%0D%0ACall%20Stack%20%28most%20recent%20call%20first%29%3A%0D%0A%20%20A%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fcmake%2Fmodules%2Fzephyr_default.cmake%3A108%20%28include%29%0D%0A%20%20A%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fshare%2Fzephyr-package%2Fcmake%2FZephyrConfig.cmake%3A66%20%28include%29%0D%0A%20%20A%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fshare%2Fzephyr-package%2Fcmake%2FZephyrConfig.cmake%3A92%20%28include_boilerplate%29%0D%0A%20%20CMakeLists.txt%3A5%20%28find_package%29%0D%0A%0D%0A%0D%0A--%20In%3A%20A%3A%2Fbachelornordic%2Fmain_unit%2Fbuild%2Fzephyr%2C%20command%3A%20A%3A%2Fnordicsemi%2Ftoolchains%2Fv2.3.0%2Fopt%2Fbin%2Fpython.exe%3BA%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fscripts%2Fdts%2Fgen_defines.py%3B--dts%3BA%3A%2Fbachelornordic%2Fmain_unit%2Fbuild%2Fzephyr%2Fzephyr.dts.pre%3B--dtc-flags%3B%27-Wno-unique_unit_address_if_enabled%27%3B--bindings-dirs%3BA%3A%2Fnordicsemi%2Fv2.3.0%2Fnrf%2Fdts%2Fbindings%3BA%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fboards%2Farm%2Fnrf9160dk_nrf9160%2Fdts%2Fbindings%3BA%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fdts%2Fbindings%3B--header-out%3BA%3A%2Fbachelornordic%2Fmain_unit%2Fbuild%2Fzephyr%2Finclude%2Fgenerated%2Fdevicetree_generated.h.new%3B--dts-out%3BA%3A%2Fbachelornordic%2Fmain_unit%2Fbuild%2Fzephyr%2Fzephyr.dts.new%3B--edt-pickle-out%3BA%3A%2Fbachelornordic%2Fmain_unit%2Fbuild%2Fzephyr%2Fedt.pickle%3B--vendor-prefixes%3BA%3A%2Fnordicsemi%2Fv2.3.0%2Fnrf%2Fdts%2Fbindings%2Fvendor-prefixes.txt%3B--vendor-prefixes%3BA%3A%2Fnordicsemi%2Fv2.3.0%2Fzephyr%2Fdts%2Fbindings%2Fvendor-prefixes.txt%0D%0A--%20Configuring%20incomplete%2C%20errors%20occurred%21%0D%0AFATAL%20ERROR%3A%20command%20exited%20with%20status%201%3A%20%27a%3A%5Cnordicsemi%5Ctoolchains%5Cv2.3.0%5Copt%5Cbin%5Ccmake.EXE%27%20%27-DWEST_PYTHON%3Da%3A%5Cnordicsemi%5Ctoolchains%5Cv2.3.0%5Copt%5Cbin%5Cpython.exe%27%20%27-Ba%3A%5Cbachelornordic%5Cmain_unit%5Cbuild%27%20-GNinja%20-DBOARD%3Dnrf9160dk_nrf9160_ns%20-DNCS_TOOLCHAIN_VERSION%3ASTRING%3DNONE%20%27-DBOARD_ROOT%3ASTRING%3Da%3A%2Fbachelornordic%2Fmain_unit%3Ba%3A%2Fbachelortesting%2Fdiv_tests%2Fbme280_test%27%20-DCONFIG_DEBUG_OPTIMIZATIONS%3ASTRING%3Dy%20-DCONFIG_DEBUG_THREAD_INFO%3ASTRING%3Dy%20-DDTC_OVERLAY_FILE%3ASTRING%3Da%3A%2Fbachelornordic%2Fmain_unit%2Fboards%2Fnrf9160dk_nrf9160_ns.overlay%20-DCONF_FILE%3ASTRING%3Da%3A%2Fbachelornordic%2Fmain_unit%2Fprj.conf%20%27-Sa%3A%5Cbachelornordic%5Cmain_unit%27%0D%0A%0D%0A%20%2A%20%20The%20terminal%20process%20terminated%20with%20exit%20code%3A%201.%20%0D%0A%20%2A%20%20Terminal%20will%20be%20reused%20by%20tasks%2C%20press%20any%20key%20to%20close%20it.%20]

nrf9160dk_nrf9160_ns.overlay:

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:fdaae8a3-d493-4c0e-92b9-cd99dd82bfce:type=c_cpp&text=%26pinctrl%20%7B%0D%0A%09i2c2_default%3A%20i2c2_default%20%7B%0D%0A%09%09group1%20%7B%0D%0A%09%09%09psels%20%3D%20%3CNRF_PSEL%28TWIM_SDA%2C%200%2C%2011%29%3E%2C%0D%0A%09%09%09%09%09%3CNRF_PSEL%28TWIM_SCL%2C%200%2C%2012%29%3E%3B%0D%0A%09%09%7D%3B%0D%0A%09%7D%3B%0D%0A%0D%0A%09i2c2_sleep%3A%20i2c2_sleep%20%7B%0D%0A%09%09group1%20%7B%0D%0A%09%09%09psels%20%3D%20%3CNRF_PSEL%28TWIM_SDA%2C%200%2C%2011%29%3E%2C%0D%0A%09%09%09%09%09%3CNRF_PSEL%28TWIM_SCL%2C%200%2C%2012%29%3E%3B%0D%0A%09%09%09low-power-enable%3B%0D%0A%09%09%7D%3B%0D%0A%09%7D%3B%0D%0A%0D%0A%09spi3_default%3A%20spi3_default%20%7B%0D%0A%09%09group1%20%7B%0D%0A%09%09%09psels%20%3D%20%3CNRF_PSEL%28SPIM_SCK%2C%200%2C%203%29%3E%2C%0D%0A%09%09%09%09%09%3CNRF_PSEL%28SPIM_MOSI%2C%200%2C%204%29%3E%2C%0D%0A%09%09%09%09%09%3CNRF_PSEL%28SPIM_MISO%2C%200%2C%205%29%3E%3B%0D%0A%09%09%7D%3B%0D%0A%09%7D%3B%0D%0A%0D%0A%09spi3_sleep%3A%20spi3_sleep%20%7B%0D%0A%09%09group1%20%7B%0D%0A%09%09%09psels%20%3D%20%3CNRF_PSEL%28SPIM_SCK%2C%200%2C%203%29%3E%2C%0D%0A%09%09%09%09%09%3CNRF_PSEL%28SPIM_MOSI%2C%200%2C%204%29%3E%2C%0D%0A%09%09%09%09%09%3CNRF_PSEL%28SPIM_MISO%2C%200%2C%205%29%3E%3B%0D%0A%09%09%09low-power-enable%3B%0D%0A%09%09%7D%3B%0D%0A%09%7D%3B%0D%0A%09%0D%0A%09uart0_default%3A%20uart0_default%20%7B%0D%0A%09%09group1%20%7B%0D%0A%09%09%09psels%20%3D%20%3CNRF_PSEL%28UART_TX%2C%200%2C%2022%29%3E%2C%0D%0A%09%09%09%09%3CNRF_PSEL%28UART_RTS%2C%200%2C%2024%29%3E%3B%0D%0A%09%09%7D%3B%0D%0A%09%09group2%20%7B%0D%0A%09%09%09psels%20%3D%20%3CNRF_PSEL%28UART_RX%2C%200%2C%2023%29%3E%2C%0D%0A%09%09%09%09%3CNRF_PSEL%28UART_CTS%2C%200%2C%2025%29%3E%3B%0D%0A%09%09%09bias-pull-up%3B%0D%0A%09%09%7D%3B%0D%0A%09%7D%3B%0D%0A%09%0D%0A%09uart0_sleep%3A%20uart0_sleep%20%7B%0D%0A%09%09group1%20%7B%0D%0A%09%09%09psels%20%3D%20%3CNRF_PSEL%28UART_TX%2C%200%2C%2022%29%3E%2C%0D%0A%09%09%09%09%3CNRF_PSEL%28UART_RX%2C%200%2C%2023%29%3E%2C%0D%0A%09%09%09%09%3CNRF_PSEL%28UART_RTS%2C%200%2C%2024%29%3E%2C%0D%0A%09%09%09%09%3CNRF_PSEL%28UART_CTS%2C%200%2C%2025%29%3E%3B%0D%0A%09%09%09low-power-enable%3B%0D%0A%09%09%7D%3B%0D%0A%09%7D%3B%0D%0A%7D%3B%0D%0A%0D%0A%26i2c2%20%7B%0D%0A%09compatible%20%3D%20%22nordic%2Cnrf-twim%22%3B%0D%0A%09status%20%3D%20%22okay%22%3B%0D%0A%09clock-frequency%20%3D%20%3CI2C_BITRATE_STANDARD%3E%3B%0D%0A%09%0D%0A%09bme280%3A%20bme280%4076%20%7B%0D%0A%09%09compatible%20%3D%20%22bosch%2Cbme280%22%3B%0D%0A%09%09reg%20%3D%20%3C0x76%20%3E%3B%0D%0A%09%7D%3B%0D%0A%7D%3B%0D%0A%0D%0A%26spi3%20%7B%0D%0A%09status%20%3D%20%22okay%22%3B%0D%0A%09cs-gpios%20%3D%20%3C%26gpio0%207%200%3E%2C%20%3C%26gpio0%208%200%3E%3B%0D%0A%09adxl372%3A%20adxl372%400%20%7B%0D%0A%09%09compatible%20%3D%20%22adi%2Cadxl372%22%3B%0D%0A%09%09reg%20%3D%20%3C0%3E%3B%0D%0A%09%09spi-max-frequency%20%3D%20%3C1000000%3E%3B%0D%0A%09%7D%3B%0D%0A%09atxl362%3A%20adxl362%401%20%7B%0D%0A%09%09compatible%20%3D%20%22adi%2Cadxl362%22%3B%0D%0A%09%09reg%20%3D%20%3C1%3E%3B%0D%0A%09%09spi-max-frequency%20%3D%20%3C1000000%3E%3B%0D%0A%09%7D%3B%0D%0A%7D%3B%0D%0A%0D%0A%26uart0%20%7B%0D%0A%09status%20%3D%20%22okay%22%3B%0D%0A%09current-speed%20%3D%20%3C115200%3E%3B%0D%0A%09pinctrl-0%20%3D%20%3C%26uart0_default%3E%3B%0D%0A%09pinctrl-1%20%3D%20%3C%26uart0_sleep%3E%3B%0D%0A%09pinctrl-names%20%3D%20%22default%22%2C%20%22sleep%22%3B%0D%0A%7D%3B%0D%0A%0D%0A%2F%20%7B%0D%0A%09leds%20%7B%0D%0A%09%09compatible%20%3D%20%22gpio-leds%22%3B%0D%0A%09%09%2F%2F%20There%27s%20also%20led0%20available%20%28green%20on-board%20LED%201%29%0D%0A%09%09%0D%0A%09%09blue_led%3A%20blue_led%20%7B%0D%0A%09%09%09gpios%20%3D%20%3C%26gpio0%200%200%3E%3B%0D%0A%09%09%09label%20%3D%20%22Blue%20on-board%20LED%202%22%3B%0D%0A%09%09%7D%3B%0D%0A%09%09%0D%0A%09%09%2F%2F%20The%20below%20nodes%20are%20taken%20up%20by%20SPI%2FI2C.%0D%0A%09%09%26led1%20%7B%0D%0A%09%09%09%2Fdelete-property%2F%20gpios%3B%0D%0A%09%09%7D%3B%0D%0A%09%09%26led2%20%7B%0D%0A%09%09%09%2Fdelete-property%2F%20gpios%3B%0D%0A%09%09%7D%3B%0D%0A%09%09%26led1%20%7B%0D%0A%09%09%09%2Fdelete-property%2F%20gpios%3B%0D%0A%09%09%7D%3B%0D%0A%09%7D%3B%0D%0A%0D%0A%09buttons%20%7B%0D%0A%09%09compatible%20%3D%20%22gpio-keys%22%3B%0D%0A%09%09%0D%0A%09%09%2Fdelete-node%2F%20button_0%3B%0D%0A%09%09%2Fdelete-node%2F%20button_1%3B%0D%0A%09%09%2Fdelete-node%2F%20button_2%3B%0D%0A%09%09%2Fdelete-node%2F%20button_3%3B%0D%0A%09%09%0D%0A%09%09nrf91_btn_1%3A%20nrf91_btn_1%20%7B%0D%0A%09%09%09gpios%20%3D%20%3C%26gpio0%2027%20%28GPIO_ACTIVE_LOW%20%7C%20GPIO_PULL_UP%29%3E%3B%0D%0A%09%09%7D%3B%0D%0A%0D%0A%09%09nrf91_btn_2%3A%20nrf91_btn_2%20%7B%0D%0A%09%09%09gpios%20%3D%20%3C%26gpio0%2026%20%28GPIO_ACTIVE_LOW%20%7C%20GPIO_PULL_UP%29%3E%3B%0D%0A%09%09%7D%3B%0D%0A%09%7D%3B%0D%0A%7D%3B]

NRF Connect SPIS

Lewy2552 — Tue, 08 Oct 2024 18:31:40 GMT

Hello, I am trying to convert my codebase from segger embedded studio to nrf connect. I am currently working on the spi section of my codebase.

I am communicating from my STM32U5 (Master) processor and my nrf52840 (slave). I have completed the section on the nordic developer academy where nordic outlines spi. Issue that i am having is that it only shows how to set the nrf as master.

Can I have some assistance on how to set up the device tree in order to put the nrf as as slave, as well as how to grab the DT node properly for communication across that line.

Thanks

RE: NRF Connect SPIS

Thereed1952 — Sat, 13 Jun 2026 06:49:18 GMT

You may want to look into the SPIS (Her Trees) driver examples in NCS, as most tutorials focus on the master side. Sharing your current device tree overlay and SPI configuration would make it easier for others to suggest the correct DT node setup and initialization.

RE: nPM1300 BUCK2 not regulating to 3.3 V in standalone mode

tarunkt — Sat, 13 Jun 2026 05:46:04 GMT

Dear Szabolcs,

Thank you for the clarifications and debugging suggestions.

Please find attached the oscilloscope measurements, along with a tabulated summary of the observations under both battery-only and VBUS-connected conditions.

I would appreciate your review of the captured waveforms and measurements. Please let me know if there are any additional checks you would recommend.

Thank you for your guidance.

Regards,

devzone.nordicsemi.com/.../Scope-Measurements.zip

nPM1300 BUCK2 not regulating to 3.3 V in standalone mode

tarunkt — Thu, 11 Jun 2026 07:58:55 GMT

Hi Nordic team,

I'm debugging a custom board using the nPM1300 and I'm seeing unexpected behavior from BUCK2. I'd appreciate any guidance on whether I'm misunderstanding the VSET configuration or if there is another startup/configuration requirement that I'm missing.

Hardware Configuration

PMIC: nPM1300
Operating mode: Standalone (no PMIC configuration over I²C)
BUCK2 desired output: 3.3 V
VSET2 resistor: 300 kΩ to GND
According to the nPM1300 Product Specification v1.3, the VSET2 table shows:
- 250–500 kΩ → 3.3 V
NTC pin connected to GND through a 0 Ω resistor
No intentional connection between BUCK2 output and VSYS
Resistance from VSET2 to GND measures approximately 300 kΩ on the board

Observed Behavior (Board Under Test)

With USB power connected:

Signal	Measured Voltage
VBUS	5.1 V
VSYS	5.0 V
BUCK2 Output (VOUT2)	4.45 V

The expected BUCK2 output is 3.3 V, but instead it sits around 4.45 V.

Battery-only operation

When running from battery:

One board measures ~3.3 V at BUCK2 output
Another board measures ~3.5 V at BUCK2 output

The output appears to track the battery voltage rather than regulate to a fixed 3.3 V.

Questions

Is 300 kΩ a valid VSET2 value for selecting 3.3 V on nPM1300 Product Specification v1.3?
In standalone mode, should BUCK2 automatically enable and regulate to the VSET-selected voltage at startup?
Could grounding the NTC pin through 0 Ω affect BUCK2 startup or operation?
Is it expected that VSYS measures almost the same as VBUS (5.0 V vs 5.1 V) in this configuration?
Are there any recommended measurements or status registers that would help determine whether BUCK2 is actually enabled?

Any suggestions for further debugging would be greatly appreciated.

Thank you.

Guidance Required for nRF9151 Antenna RF Certification Testing and VNA Validation

Milan Pipaliya — Sat, 13 Jun 2026 05:44:48 GMT

Hello Nordic Community,

We are developing a custom product based on nRF9151 using NCS SDK v3.1.0.

On the hardware side, we have already completed antenna matching and tuning activities, including component optimization of the matching network. We are currently performing VNA (Vector Network Analyzer) measurements to verify antenna performance (S11/Return Loss) across the required LTE frequency bands.

For RF validation and certification preparation, we would like guidance on the recommended testing methodology from Nordic.

We found the following modem RF test command:

AT%XRFTEST=1,1,28,7000,23,1,4,1,0,0,0,0

Example configuration:

Band 28
700 MHz
LTE-M (Cat-M1)
+23 dBm TX Power
CW Modulation

Our current validation approach includes:

Antenna tuning and matching network optimization.
VNA measurements (S11/Return Loss).
Firmware-based RF transmission testing using %XRFTEST.
Planned conducted and radiated measurements in an RF laboratory.

We would appreciate guidance on the following:

Is %XRFTEST the recommended and valid method for RF antenna testing and certification preparation on nRF9151?
Which firmware/modem firmware version is recommended for laboratory RF testing?
After VNA verification, what additional RF validation steps are recommended by Nordic before certification?
Are there specific Nordic procedures for:
- Conducted TX measurements
- Radiated antenna measurements
- Output power verification
- Band and frequency verification
- LTE-M certification pre-compliance testing
Can certification-related RF measurements be performed using firmware-controlled test commands such as %XRFTEST, or is there a dedicated Nordic test methodology that should be followed?
Are there any limitations of %XRFTEST when compared to certification lab test procedures?

We are looking for guidance on the complete validation flow, including antenna tuning, VNA measurements, firmware-based RF testing, and certification testing for an nRF9151-based design.

Thank you for your support and guidance.

Best Regards,
Milan

AT%XRFTEST TX command not supported on nRF9151

NanWang — Mon, 03 Mar 2025 03:30:33 GMT

Hi,

We have come across AT%XRFTEST command problem for TX test on nRF9151 EVK. We have used nRF9151 modem firmware version 2.0.2 and executed following AT command on nRF9151 EVK:

"AT%XRFTEST=1,1,19,8370,23,1,4"

"AT%XRFTEST=1,0"

But we get following error:

And we also found AT%XRFTEST command doesn't support TX test on doc nRF91x1 Cellular AT Commands. Could you give any good suggestions for testing TX through this command? Thank you very much.

RE: AT%XRFTEST TX command not supported on nRF9151

Milan Pipaliya — Sat, 13 Jun 2026 05:42:44 GMT

Is using AT%XRFTEST the recommended and valid approach for antenna RF performance testing during certification/pre-compliance testing?

RE: nrf5340 BAP_BROADCAST_SOURCE sample region `RAM' overflowed occur.

Susheel Nuguru — Sat, 13 Jun 2026 05:02:52 GMT

Thanks for finding that, the default values seems to have changed in newer SDK

Kconfig	3.1.1	3.3.0
`BT_CTLR_ADV_ISO_SET`	1	2
`BT_CTLR_ADV_ISO_STREAM_COUNT`	2	4
`BT_CTLR_ISOAL_SOURCES`	2	4
`BT_CTLR_ISO_TX_BUFFERS`	8	12
`BT_ISO_TX_BUF_COUNT`	8	12

Hence the larger memory needs, if you want the same sizes as v3.1.1 add below to your prj.conf and do a prestine build

CONFIG_BT_CTLR_ADV_ISO_SET=1
CONFIG_BT_CTLR_ADV_ISO_STREAM_COUNT=2
CONFIG_BT_CTLR_ISOAL_SOURCES=2
CONFIG_BT_CTLR_ISO_TX_BUFFERS=8
CONFIG_BT_ISO_TX_BUF_COUNT=8

I will report this internally so that this gets attention from the team.

Thanks for reporting it.

nrf5340 BAP_BROADCAST_SOURCE sample region `RAM' overflowed occur.

orip — Fri, 12 Jun 2026 10:42:52 GMT

Bros, I had updated ncs sdk from v3.1.1 to v3.3.1 today, and when I rebuild an nrf5340 project found that NETAPP ram overflowed, and the error could be represented by build the bap_broadcast_source sample, the netapp only has 64k sram, so that means overflowed by 8k can't be settle by tuning parameter, so how to sovle it

c:/ncs/toolchains/936afb6332/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `noinit' will not fit in region `RAM'
c:/ncs/toolchains/936afb6332/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `RAM' overflowed by 7796 bytes

RE: Multiple MCUBoot Keys and Securing a Private Key

J.P. Hutchins — Sat, 13 Jun 2026 00:34:34 GMT

Feature is merged at MCUBoot: https://github.com/mcu-tools/mcuboot/pull/2701

Starting on Zephyr PR, hoping for inclusion in 4.5: github.com/.../111203

Multiple MCUBoot Keys and Securing a Private Key

EDLT — Fri, 31 May 2024 19:16:59 GMT

Using SDK 2.4.2

1) Is there a way to specify multiple MCUBoot keys in the same way they can be specified for NSIB? MCU Boot allows an array of keys, but it looks like zephyr hardcodes it to one key, and I would have to modify keys.c to accommodate an array of public keys. Is this correct? Might there be a simpler way to handle this than having to patch the SDK?

2) NSIB also provides a hook for a custom signing script with SB_SIGNING_COMMAND. This means the private key can be stored on a secure server and not in our code repository. MCUBoot doesn't have a similar mechanism, correct? If I want to insert my own signature, what would prevent me from using a signed image and just replacing the signature in the trailer?

3) If I were able to securely sign an image for MCUBoot, how should I go about getting the public key to the MCUBoot application? The public key array is generated at build time, and I don't see a way to specify my own key c-file or public pem to be used to generate said file.

Thanks!

Unsure about nPM2100 power consumption

Daniel Dakhno — Thu, 28 May 2026 09:40:35 GMT

Hello,

I attempted to rebuild the reference circuitry from the nPM2100, and I am measuring unusual power consumption using the PK2 outputting 1000mV.

Partially, I had a unrealistically low consumption on the input. Far lower than what I was drawing at the output.

On the other hand, I connected a 100 Ohm resistor to the output. I did not configure anything via I2C.

On the output, I measured a current of 30mA, which makes sense.

On the input, the PK2 was reporting a current of 300mA.

In summary:

Input: 1000mV, drawing 300mA.

Output: drawing 30mA via 100Ohm resistor.

I would be glad to have these questions answered:

1. Are these numbers realistic? Could I be missing a component?

2. Is it reasonable to use the nPM2100 without any configuration via I2C?

3. Is there some chart outlining the efficiency of the nPM in different voltages etc.?

4. Is the PK2 able to reliably measure the current consumption of the nPM2100 with it's measurement frequency?

Thanks a lot!

RE: Unsure about nPM2100 power consumption

Daniel Dakhno — Sat, 13 Jun 2026 00:12:38 GMT

I understand, thanks.

Attached is my second attempt, hopefully with a higher chance of success...devzone.nordicsemi.com/.../npm2100_5F00_caaa_5F00_config1.zip

nRF54L15: high current consumption after using FPU, need information about FPU_IRQn interrupt vector.

Frank Viganske — Fri, 12 Jun 2026 08:39:56 GMT

Hi,

i am working on a project using the nRF54L15.

Hardware: custom board with nRF54L15

Software:

Wirepas SDK (1.6.2)
nrfx drivers (version 3.9.0) with some customization to integrate it into the SDK
CMSIS DSP floating point libraries (Version 5.1)

I see in my current measurements that idle current increases by roughly 300µA after using the floating point unit. I already checked the developer zone for any similar tickets, and there are lots of them, though all are for other SoC, like nRF52 series.

Most of these tickets suggest the high current consumption comes from unhandled FPU interrupts. I was already able to confirm that this is indeed the reason for the increased current. Now i'm trying to implement a solution for this.

The suggested solution from other tickets is to do something like the code below:

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:61027edc-9a1a-4ef2-b3bb-e6b6be24a2cc:type=c_cpp&text=__STATIC_INLINE%20void%20pwr_mgmt_fpu_sleep_prepare%28void%29%0A%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20uint32_t%20original_fpscr%3B%0A%0A%20%20%20%20%20%20%20%20CRITICAL_REGION_ENTER%28%29%3B%0A%20%20%20%20%20%20%20%20original_fpscr%20%3D%20__get_FPSCR%28%29%3B%0A%20%20%20%20%20%20%20%20%2F%2A%0A%20%20%20%20%20%20%20%20%20%2A%20Clear%20FPU%20exceptions.%0A%20%20%20%20%20%20%20%20%20%2A%20Without%20this%20step%2C%20the%20FPU%20interrupt%20is%20marked%20as%20pending%2C%0A%20%20%20%20%20%20%20%20%20%2A%20preventing%20system%20from%20sleeping.%20Exceptions%20cleared%3A%0A%20%20%20%20%20%20%20%20%20%2A%20-%20IOC%20-%20Invalid%20Operation%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%20-%20DZC%20-%20Division%20by%20Zero%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%20-%20OFC%20-%20Overflow%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%20-%20UFC%20-%20Underflow%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%20-%20IXC%20-%20Inexact%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%20-%20IDC%20-%20Input%20Denormal%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%2F%0A%20%20%20%20%20%20%20%20__set_FPSCR%28original_fpscr%20%26%20~0x9Fu%29%3B%0A%20%20%20%20%20%20%20%20__DMB%28%29%3B%0A%20%20%20%20%20%20%20%20NVIC_ClearPendingIRQ%28FPU_IRQn%29%3B%0A%20%20%20%20%20%20%20%20CRITICAL_REGION_EXIT%28%29%3B%0A%0A%20%20%20%20%20%20%20%20%2F%2A%0A%20%20%20%20%20%20%20%20%20%2A%20The%20last%20chance%20to%20indicate%20an%20error%20in%20FPU%20to%20the%20user%20%0A%20%20%20%20%20%20%20%20%20%2A%20as%20the%20FPSCR%20is%20now%20cleared%0A%20%20%20%20%20%20%20%20%20%2A%0A%20%20%20%20%20%20%20%20%20%2A%20This%20assert%20is%20related%20to%20previous%20FPU%20operations%20%0A%20%20%20%20%20%20%20%20%20%2A%20and%20not%20power%20management.%0A%20%20%20%20%20%20%20%20%20%2A%0A%20%20%20%20%20%20%20%20%20%2A%20Critical%20FPU%20exceptions%20signaled%3A%0A%20%20%20%20%20%20%20%20%20%2A%20-%20IOC%20-%20Invalid%20Operation%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%20-%20DZC%20-%20Division%20by%20Zero%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%20-%20OFC%20-%20Overflow%20cumulative%20exception%20bit.%0A%20%20%20%20%20%20%20%20%20%2A%2F%0A%20%20%20%20%20%20%20%20ASSERT%28%28original_fpscr%20%26%200x7%29%20%3D%3D%200%29%3B%0A%20%20%20%20%20%7D]

That is, 1. clear the FPU exception bits in FPSCR, 2. clear the pending IRQ with NVIC_ClearPendingIRQ(FPU_IRQn);

Which brings me to my problem. I can't find any definition for FPU_IRQn for the nRF54L15, neither in the Nordic Documentation nor in any of the processor header files.

For other SoCs FPU_IRQn is defined as an enum value in IRQn_Type. For the nRF54L15, in nrf54l15_application.h there is a similar type definition for IRQn_Type, but it does not contain the FPU_IRQn.

Maybe it is just named differently?

So my question is: how do i clear the pending IRQ for the FPU on the nRF54L15?

Best regards

Frank Viganske

RE: nRF54L15: high current consumption after using FPU, need information about FPU_IRQn interrupt vector.

hmolesworth — Fri, 12 Jun 2026 22:25:47 GMT

The six FPU events such as EVENTS_FPUIOC are noted as "RW"; maybe try writing a '0' to those registers which read as '1' to see if that clears the event; I haven't tried this but would like a working option.

Series Resistor on VBUS

Arielle — Thu, 11 Jun 2026 21:48:18 GMT

Hi! Do people actually use the 2.2-4.7Ohm series resistor on the VBUS input to the nRF5340? It's just such a low resistance, I don't particularly see the point. Thanks!

RE: Series Resistor on VBUS

Arielle — Fri, 12 Jun 2026 21:59:47 GMT

Makes sense, thank you!

RE: trying to send and receive the data through can bus moduler using with nrf9160 and esp32 controller (using SPI)

Vivek01 — Fri, 12 Jun 2026 21:39:32 GMT

Hi Vidar,

i measured PO. 25(CS) = 1.80v and PO. 17(INT) = 2.58v in nRF9160DK and i measured PO.5(CS) = 3.30v and PO.4(INT) = 3.30v in esp32. so you tell me that the nRF9160 DK is configured to use 1.8v by default, which is too low then can you please tell me, what's the solution for this to send and receive the data with this model.

thanks

vivek

Fetching RSSI values while synced on a BIS

Ran531 — Fri, 12 Jun 2026 21:27:30 GMT

Hello,

We are trying to assess signal quality while synced to a BIS and we would like to use the RSSI values. RSSI values do show up when scanning and at least in the Auracast sample, scanning stops once we sync on the PA. Also, RSSI from advertisement values do not represent the actual LE Audio stream RSSI?

I know about the HCI command to read RSSI, but it requires a connection handle which I don't have? Does that even make sense in a broadcast scenario? If it does where can I find the relevant connection handle for the BIS or BIG if synced on more than one channel?