Search Result

Environment SoC / Target: nRF54L15 (nrf54l15dk/nrf54l15/cpuapp) NCS Version: v3.4.0 Library Configuration: CONFIG_NFC_T4T_NRFXLIB=y, CONFIG_NFC_T4T_ISODEP=y (Raw ISO-DEP mode) Thread Model: CONFIG_NFC_THREAD_CALLBACK=y, CONFIG_NFC_OWN_THREAD=y Poller / Reader: Tested with Android smartphones Description I am implementing a custom NFC Type 4 Tag application running in raw ISO-DEP mode on the nRF54L15. The tag is configured using nfc_t4t_setup() (without setting an NDEF payload) and started via nfc_t4t_emulation_start() . The application enables the dedicated NFC platform thread ( CONFIG_NFC_OWN_THREAD=y ) to deliver events. The registered callback validates the incoming frame length and posts valid APDU payloads to a separate processing worker thread using a message queue. The Problem During testing with an NFC reader (for example, during fast polling, transaction bursts, or when the reader pulls away), the callback receives an invalid length condition where (data_length == 0) . Once this condition occurs, the NFC peripheral completely ceases to work: With Error Response: If the callback attempts

We are seeing LTE-M communication dropouts on the nRF9160 with firmware 1.3.6 This has occurred several times with multiple devices. The devices are registered on the same cell, but the connection problems don't happen at the same time. In each case, a previously established, long-lived TCP/IP connection stalls (no more incoming data). Our application detects this and tries to re-open the connection. This requires a DNS lookup (getaddrinfo) which repeatedly fails with EAI_SYSTEM errno=116 (timeout). We have enabled LTE and IP modem traces. I have attached the textual log files we recorded which contain the modem traces as hexdumps, among other information. I have converted the modem traces to the binary format, which I also attached. What is strange is that the Cellular Monitor tool fails to convert the problematic time range. There are about a thousand trace packets in each file, but only fewer than 100 show up in

您好！ 听说现在的例程可以支持导出IQ的功能，请问哪一个版本的NCS可以支持呢，代码是开源的吗，是不是下载了这个版本的NCS就可以导出IQ呢？然后的话是能够导出到自己的电脑上还是通过串口进行导出呢，麻烦您帮我详细解答一下，谢谢了！

Hello Nordic Support Team, I am working on a project using the nRF54LM20B controller, and my application requires operation in a very low-power mode . To optimize power consumption, I would like to know whether it is possible to control or change the CPU clock frequency at runtime in the application. Could you please confirm the following points? Does the nRF54LM20B support runtime CPU clock frequency scaling/control? If yes, is there any supported API or driver in the nRF Connect SDK / Zephyr to change the CPU frequency during runtime? Are there any limitations or recommended practices for changing the CPU clock frequency while the application is running? Could you please share any official sample project, application note, or documentation related to runtime CPU frequency control or low-power configuration for nRF54LM20B? If runtime CPU frequency control is not supported, what is the recommended approach to achieve the lowest possible power

Hello Nordic support, We are preparing a build-only NCS2.9.0 environment on an Apple Silicon Mac, macOS26.5.1 (25F80), with commands run in a managed workspace execution context. We have not installed the SDK globally or interacted with a device. Please help identify whether the following is a release-signing issue or an Apple native trust-evaluation/environment requirement, and provide a supported resolution. Official artifacts and SHA256: 1. files.nordicsemi.com/.../nrfutil 5263376bytes; 1b993eece5a6e3e079ce25fa31a134ce4c12fb51735d10114a2ea4a1df048591 2. Documented macOS universal distribution: files.nordicsemi.com/.../nrfutil 11669520bytes; 866a0d9e6c8b7b3d46b219caa71e485b26bad3f53c9ba7c06d9665620f35b394 3. Core8.2.1 archive: files.nordicsemi.com/.../nrfutil-aarch64-apple-darwin-8.2.1.tar.gz 2851838bytes; 3162977182e1fe712dff1ab353de0471dfd63d2d9b7d4cc197d2c77987a959cc Its extracted executable is5842128bytes; b7ccd9f4931df7168cb590d1129c7c6aed5bf3ae74ad61a43385da7f5544a8b5. Each download matches its publisher X-Checksum-Sha256 header. Native `codesign --verify --strict --verbose=2 ` failed for thin launcher/core; `codesign --verify --strict --all-architectures --verbose=2 ` failed for the separately downloaded documented distribution: ``` invalid signature (code or signature have been modified) In architecture: arm64 ``` `codesign -d --verbose=4` reports TeamIdentifier=P3R8YQEV4L, Runtime Version=15.4.0 and Authority=(unavailable). The universal identifier is nrfutil; thin launcher identifier is nrfutil-6a9af0aeb8524516; core identifier

Hi, Two separate technical questions on the nRF54L15. 1. CHANNEL SOUNDING — SCALING WITH MULTIPLE PEER DEVICES When a single nRF54L15 acts as the central/Initiator and needs to sequentially connect to and run a Channel Sounding exchange with multiple peripheral devices (one at a time, not concurrently), what is the typical time required per device for: connection establishment + Channel Sounding procedure + disconnection? Is there a practical upper limit on how many peer devices a single nRF54L15 can cycle through per second (or per few seconds), given this sequential connect-range-disconnect pattern? Any guidance on how total cycle time scales as peer device count increases would be helpful. 2. DIRECTION FINDING — GPIO/DFE ANTENNA SWITCHING On chips like the nRF52833 and nRF5340, antenna arrays for AoA/AoD are connected via GPIO pins routed through the RADIO peripheral's DFE (Direction Finding Extension) switching hardware (SWITCHPATTERN register, DFEGPIO pins). I've noticed register documentation

Hi, Our project has chosen nPM1300 as the PMIC, and our project's battery is only 28 mAh. When we tested the battery configuration file using the nPM PowerUP app, we found that the lower limit of the battery was 32 mAh. We obtained the source code of the nPM PowerUP application from Git hub and found the lower limit setting in the code. We modified it to 26 mAh and built it locally. Afterwards, we connected it to EK for testing, and the modification seemed successful, and the software ran normally. What I want to confirm with you is that if we want to change the battery capacity limit of the nPM PowerUP application, we only need to modify this position? Thanks. Michael Chenb

Hello, I bought a nRF93M1-DK to evaluate the LTE connectivity. I need to integrate it to an MCU with an already running AT-command interface through UART. I already have my eSIM chip and mobile network operator connectivity. I am trying to setup a project in VS code. could you please tell me where I can find: nRF93M1 AT command user manual nRF54L implemented AT command library tutorial to setup project in VS code Thanks!

We are observing an unexpected increase in current consumption when enabling the LED driver outputs of the nPM1304. We configure the LED drivers to Host mode , which by itself does not cause any noticeable increase in current consumption. However, as soon as we enable any of the LEDDRV SET registers — LEDDRV0SET, LEDDRV1SET, or LEDDRV2SET — we observe an additional current consumption of approximately 300 µA . The behavior is consistent across all three LED driver channels: Configuring the LEDDRV channels to Host mode : no noticeable increase in current consumption. Enabling LEDDRV0SET : approximately +300 µA. Enabling LEDDRV1SET : approximately +300 µA. Enabling LEDDRV2SET : approximately +300 µA. The ~300 µA increase is observed when any one of the three SET registers is enabled . It does not increase by another 300 µA when additional LEDDRV channels are enabled. The additional current consumption appears to be associated specifically

Hi Nordic Team, Application Profile:- BLE: Peripheral + Central simultaneously, Extended Advertising (2 sets), no bonding/no CONFIG_BT_SMP (production provisioning model), MCUmgr/SMP DFU over BLE (device-to-device OTA) Wi-Fi: STA mode only (no AP/P2P), wpa_supplicant with WPA3-SAE, MQTT client over TLS to AWS IoT, plus a second OTA path over HTTPS (S3-hosted firmware) No Thread/Zigbee/802.15.4, no USB, no NFC, no sensor subsystem Current footprint (measured via west build -t rom_report / ram_report ) Resource Used Total % Flash 1,168,716 B 1,850 KB 61.7% RAM 443,552 B 511 KB 84.8% Per-subsystem breakdown (ROM / RAM): Subsystem ROM RAM BLE (host + controller + app glue) ~61.5 KB (5.3%) ~53.1 KB (~12%) Wi-Fi (nRF70 driver + wpa_supplicant + app glue) ~266.4 KB (22.8%) ~82.4 KB (~18.6%) MQTT (app-level, AWS pairing/JSON router) ~39.5 KB (3.4%) ~38.0 KB (8.6%) OTA/DFU (both BLE-SMP and Wi-Fi-S3 paths + MCUmgr) ~24.8 KB (2.1%) ~26.5 KB (6%) mbedTLS/PSA crypto (shared: