0 results found on Nordicsemi
All results121686 results found on DevZone
Dear Nordic Semiconductor Support Team, We are preparing a small, non-commercial research experiment to investigate the timing characteristics of Bluetooth Low Energy (BLE) packet reception using the nRF52840 DK (PCA10056) and Nordic's official nRF Sniffer for Bluetooth LE . We would appreciate clarification from an engineer familiar with the sniffer firmware and its timestamp implementation before purchasing the hardware. Experimental setup Our intended configuration is: Receiver: Nordic nRF52840 DK (PCA10056), hardware revision not yet confirmed. Firmware: Official nRF Sniffer for Bluetooth LE firmware distributed with nrfutil. Host: Windows PC. Connection: Direct nRF USB port, following Nordic's current recommendations. Capture software: Wireshark with Nordic's official nrfutil BLE Sniffer integration. Transmitter: A nearby BLE device generating advertising packets. Output: Original, unmodified packet captures (.pcapng) for offline timing analysis. The receiver will be stationary during the initial experiment. Research objective Our primary objective is to determine whether the official sniffer provides a reliable,
forum
11/17/2026
our application is occasionally getting stuck in a tcp (tls) send. it's not permanently stuck since things like our cell provider's 'rnetwork reset' gets things moving along. a little reverse engineering (and waiting for the hang) leads me to _req_forward() from libmodem.a called from nrf_sendto(). this loooks like: int32_t _req_forward(int32_t arg1, int32_t shared, int32_t* buf) *(uint32_t*)(shared + 0xc) = buf; *(uint32_t*)buf = 0xbc00c1ee; int32_t timeout = -1; rpc_client_msg_send(4, arg1, shared); int32_t err; do { err = *(uint32_t*)buf; if (err != 0xbc00c1ee) return rpc_error_to_nrf_errno(err); err = nrf_modem_os_timedwait(2, &timeout); } while (err == 0); if (err context == context) || (context == 0) || (thread->context == 0)) k_sem_give(&thread->sem); however, there's a window from when _req_forward() calls rpc_client_msg_send() and when nrf_modem_os_timedwait() makes the thread available to the isr to be signalled. hoisting the irq lock from sleeping_add() into nrf_modem_os_timedwait() helps our case but i guess there's still a theorhetical race (w/o fully knowing
forum
11/17/2026
Hello, As per data sheet "Endurance 10 000 write/erase cycles" Does it mean do we need to consider either write or erase as 1 unit or both write and erase as write will convert bit 1 to 0 and erase will convert bit 0 to 1. Ex: If I write and erase same flash sector 10 times then whether can I say, completed 10 cycles (Only erase) or 20 cycles (Write + erase). Thanks & Regards Vishnu Beema
forum
11/17/2026
Running a test that sends a small ping packet to a server about 1/minute and I'm seeing intermittent board resets. I'm still trying to track down the cause, but in one case the the debugger stopped at nrf_modem_fault_handler (fault=0x200290c8 ) at nrf/lib/nrf_modem_lib/fault.c:68 68 lte_net_if_modem_fault_handler(); (gdb) p *fault $1 = {reason = 16, program_counter = 1728588} (gdb) p/x fault->reason $2 = 0x10 (gdb) p/x fault->program_counter $3 = 0x1a604c Running Zephyr with SDK 3.2.0, modem firmware 2.0.2. Would updating the modem firmware to 2.0.4 be likely to have any effect on this fault? Thanks for any information.
forum
11/16/2026
Hi AFAIK CRA needs SPDX 3.0 which can no be generated by west ncs-sbom in NCS 3.4. Will SPDX 3.0 generation be backported from 3.4.99/3.5 to 3.4 LTS? Thanks in advance
forum
11/16/2026
Hello Nordic support, We are designing a battery-powered device using the u-blox NORA-B206-00B module, based on the nRF54L15. u-blox support recommended contacting you regarding an unpowered ADC input condition. The module is supplied at 2.5 V by an LDO. Battery voltage is measured through the following circuit: Battery positive to ADC input: 1 MΩ, 1%. ADC input to GND: 330 kΩ, 1%. ADC input to GND: 10 nF. Battery and module share the same ground. Maximum nominal battery voltage: 4.17 V. The divider produces approximately 1.035 V with a high-impedance input. However, the battery can remain connected while the module supply is off, so the ADC pin remains connected to this divider when VDD is nominally 0 V, including during power-down transitions. The upper resistor limits the steady-state current supplied by the battery to approximately 4.2 µA at most, including its 1% tolerance. We understand that the actual injected current
forum
11/16/2026
Hi Nordic DevZone, We are currently looking at how best to handle nRF9151 programming in mass production, and I would like to understand Nordic’s intended approach a bit better. The nRF91 Series Production Programming documentation describes the production programming flow, including the modem firmware loader, modem update and verification. I also understand that Nordic currently recommends nrfutil 91 modem-firmware-upgrade for programming the modem firmware. For automated production using dedicated gang programmers( not j-links ), is the intention that programmer vendors implement this production-programming algorithm themselves? If so, do you know of any third-party production programmers that have already implemented the complete nRF9151 flow, including modem firmware programming ? It would also be helpful to know whether: Nordic has known or validated programmer implementations available; Nordic provides any reference implementation, library, or validation support for programmer vendors. Ultimately, we are trying to understand what production programming architecture Nordic expects customers to
forum
11/16/2026
Hello Nordic team, What is the image frequency of the nRF54L15 receiver? We need this information for Bluetooth SIG RF-PHY qualification (RFPHY/RCV/BV-03-C, RFPHY/RCV/BV-09-C),but could not find it in the product documentation. Best regards,
forum
11/16/2026
Our prototype is back. At first, I used NRF Connect to flash it, but the official PC software couldn't flash the firmware. I followed the wiring instructions: (1) connect SDIO, connect the clock line, and connect the DK board's select to the target board's GND, (2) the external board has separate power, (3) the wire length is less than 10 cm. Burning failed with an error, as shown below: 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 17:25:18.877 Error: Failed with exit code 1. One or more batch tasks failed: * 1057797650:
forum
11/16/2026
We are developing an application based on the nRF9151 using NCS 3.1.1 and modem firmware mfw_nrf91x1_2.0.3 . We would like to use Proprietary PSM to control the modem's sleep behavior when the network grants standard PSM settings that greatly differ from our requested TAU and Active Time values. Our main question: If the network supports standard PSM but grants different TAU and/or Active Time values than those requested by the device, is there a way to force the modem to use Proprietary PSM with our preferred settings instead of the network-granted settings? In other words, can Proprietary PSM be explicitly selected or prioritized even when standard PSM is available, so that we can control the modem's sleep duration independently of the network's PSM configuration? If this is possible, please clarify the required configuration or AT commands/API, and whether there are any limitations.
forum
11/15/2026