Search Result

First question so I apologize if I'm missing any info. I am trying to implement the the power fail comparator on a low power battery system running a nRF54L15. Idle current less than 6uA and system off mode consumes about 3uA. It looks like the power fail comparator uses IRQ 261. What is the power domain of IRQ 261 and the power fail comparator? Is it possible to use this feature in an idle state with less than 6uA current? And when I enter deep sleep, would this feature need to be turned off (it looks like it does but if there is just any additional context that would be helpful)? Thank you!

Environment : nrf5340dk used as a mean to flash our custom board PCA10095 2.0.2 2025.14 Custom board: PCB with MDBT53 (embedding a nrf5340 with chip antenna) Description of the issue I have been trying to flash my custom board with the standard nrf procedure, using a 10 pin flat cable between the DK and my custom board. However, we've encountered this message in the programmer of nrfDesktop tools: 15:10:52.945 Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, Device error: Setting the debug port SELECT register failed while powering up sys and debug regions (Unknown error in the J-Link DLL (error code =-1)). This might indicate that the debug port is unavailable. Double-check device power supply and SWD lines, and ensure that SWD is not disabled 15:10:52.987 Error: Failed with exit code 1. One or more batch tasks failed: * 1050022343:

Hi, We have a BLE peripheral on nRF52833-QIAA (custom board based on nrf52833 ) building with NCS 2.8.0 , sysbuild, extended advertising, GATT, a prebuilt custom bootloader , and static partitions ( pm_static ). We need to move to NCS 3.4.0 . Can we jump 2.8.0 -> 3.4.0 directly, or must we go through intermediate NCS releases? In 3.4.0, is SoftDevice Controller required for nRF52833, or can we keep the Zephyr BT controller ( bt_ctlr_set_public_addr() , bt_le_ext_adv_* )? Will our existing sysbuild + pm_static layout (custom bootloader at 0x0 , app at 0x3000 ) still work, and can we still DFU an application-only hex onto devices that already have the current bootloader? Is TinyCrypt still supported in 3.4.0, or do we have to switch to PSA / Mbed TLS? For a custom nRF52833 board, what usually breaks first in this upgrade (board files, BT APIs, Partition Manager, or flash size)?

Board: nRF9151 DK, PCA10201 rev 1.1.0 Serial number: 1052048398 J-Link OB firmware: J-Link OB-nRF5340-NordicSemi, compiled Jul 8 2025 10:15:34 NCS / Toolchain: nRF Connect SDK v3.4.0 (bundled toolchain), Toolchain Manager nrfutil device: 2.19.3 / nrf-device-lib 0.22.21 / SEGGER J-Link JLink_V9.24a nrfjprog: bundled with nRF Command Line Tools --- Symptom --- No data whatsoever is received on either VCOM0 (COM3) or VCOM1 (COM4) via USB-CDC, regardless of firmware, tool, cable, or USB port used. SWD programming, verification, reset, and Board Configurator communication all work perfectly on the same USB connection, ruling out a dead/undetected board. --- What was tested (all with identical result: 0 bytes received) --- 1. Custom minimal Zephyr app (board target nrf9151dk/nrf9151/ns, sysbuild+TF-M), printk() loop every 2s, CONFIG_CONSOLE=y / CONFIG_UART_CONSOLE=y in prj.conf. Built and flashed via `west build` + `nrfjprog --program ... --chiperase --verify --reset` (tfm_merged.hex), and separately via VS Code nRF Connect extension (nrfutil runner). Both build+flash+verify

Does the nRF9151 support SGP.32 IPAd? I can't find any documentation regarding IPAd support on the modem.

Hi, In the NRF54LM20A Development Kit, in addition to the tank circuit (L5 + C8) in the path between DECA and DECRF, there is also a filter made from C7=2.2uF and FB2=15nH. However, in the NRF54LM20A datasheet FB2 is removed and C7 is not populated. Which reference should I use? Is there a disadvantage when removing this filter or was it deemed unnecessary? Thanks, Eyal

Hi, From this old thread, nRF Sniffer seems can decrypt the mesh packet. Sniffing Bluetooth Mesh packets But I still failed with add network key, application key, device key and IV index. I attach the wireshark capture file for reference. devzone.nordicsemi.com/.../mesh_5F00_light_5F00_ctrl_5F00_260826.pcapng And also nRF Mesh APP export JSON file. devzone.nordicsemi.com/.../nRF-Mesh-Network.json

dfu_target_reset how to use this function in a DFU firmware update

Hello, I couldn't find the schematic symbols and PCB packaging for the nrf9151 on altium, could you provide them please ? Thank you for your help

Hi, I have been testing Channel Sounding precision and am experiencing difficulty achieving stable ranging results. Regardless of the configuration changes I make, the ranging measurements remain highly susceptible to interference, and the accuracy is rarely better than 0.5 m. Are there any additional configuration options I can adjust to improve the ranging accuracy? Would any code changes help improve the stability or precision of the measurements? I have included the relevant configuration files and a small snippet of the changes I made to main.c below. Hardware setup: Initiator: nRF54L15 DK Reflector: nRF54L15 Tag prj.conf for ras_initiator # # Copyright (c) 2024 Nordic Semiconductor ASA # # SPDX-License-Identifier: LicenseRef-Nordic-5-Clause # CONFIG_NCS_SAMPLES_DEFAULTS=y CONFIG_DK_LIBRARY=y CONFIG_BT=y CONFIG_BT_SMP=y CONFIG_BT_CENTRAL=y CONFIG_BT_MAX_CONN=1 CONFIG_BT_BONDABLE=n CONFIG_BT_GATT_CLIENT=y CONFIG_BT_GATT_DYNAMIC_DB=y CONFIG_BT_CHANNEL_SOUNDING=y CONFIG_BT_RAS=y CONFIG_BT_RAS_RREQ=y CONFIG_BT_SCAN=y CONFIG_BT_SCAN_FILTER_ENABLE=y CONFIG_BT_SCAN_UUID_CNT=1 # The Ranging Profile recommends a MTU of at least 247 octets. CONFIG_BT_L2CAP_TX_MTU=498 CONFIG_BT_BUF_ACL_TX_SIZE=502 CONFIG_BT_BUF_ACL_RX_SIZE=502 CONFIG_BT_ATT_PREPARE_COUNT=3 CONFIG_BT_CTLR_DATA_LENGTH_MAX=251 # This reduces RAM usage. Additional RAM is