Search Result

As title. In nRF54L15 DK, I set "SB_CONFIG_BOOTLOADER_MCUBOOT=y" in file "sysbuild.conf". It makes main function GPIO toggle stop. Do have any solution to prevent this problem? result:

Hello Nordic team, I am testing a plain CoAP telemetry upload from an nRF54L15 DK over Thread using a Raspberry Pi OTBR and NAT64 to ThingsBoard Cloud. Hardware / software: Board: nRF54L15 DK nRF Connect SDK: v3.2.4-4c3fc0d44534 Zephyr: v4.2.99-9673eec75908 OpenThread with a Raspberry Pi OTBR Destination: ThingsBoard Cloud CoAP endpoint NAT64 IPv6 address used by the device: fd57:cacb:e8cf:2::343a:6f12 Plain CoAP port: 5683 The application uses Zephyr/POSIX UDP sockets together with Zephyr’s CoAP packet builder. The relevant socket flow is: sock = socket(AF_INET6, SOCK_DGRAM, IPPROTO_UDP); memset(&server_addr, 0, sizeof(server_addr)); server_addr.sin6_family = AF_INET6; server_addr.sin6_port = htons(5683); server_addr.sin6_scope_id = 0U; inet_pton(AF_INET6, "fd57:cacb:e8cf:2::343a:6f12", &server_addr.sin6_addr); connect(sock, (struct sockaddr *)&server_addr, sizeof(server_addr)); send(sock, request.data, request.offset, 0); poll(..., 5000); recv(sock, response_buf, sizeof(response_buf), MSG_DONTWAIT); The CoAP message is a Confirmable POST to: /api/v1/ /telemetry with JSON payload, for example: {"temperature":25,"counter":0,"source":"zephyr-coap-ack"} The generated CoAP packet length is 113 bytes. Sending works reliably. ThingsBoard receives the telemetry. The OTBR tcpdump shows that

HI I am currently using the nRF54L15 chip with NCS 3.2.1, carrying out secondary development based on the periodic_sync_conn sample project. I intend to adjust the transmit (TX) power before the response data is reported. I have found that the function below can be called to modify TX power; however, this function only works for adjusting the TX power of the advertising broadcaster and has no effect on the TX power used for response transmissions. Which function should I invoke to configure the TX power specifically for response packets? static void set_tx_power ( uint8_t handle_type, uint16_t handle, int8_t tx_pwr_lvl) { struct bt_hci_cp_vs_write_tx_power_level * cp ; struct bt_hci_rp_vs_write_tx_power_level * rp ; struct net_buf * buf , * rsp = NULL ; int err ; buf = bt_hci_cmd_alloc ( K_FOREVER ); if ( ! buf ) { printk ( "Unable to allocate command buffer \n " ); return ; } cp =

Hi, We are developing an application that requires synchronization between two or more nRF9160-based devices. We have the following requirements and constraints: Required time synchronization accuracy: < 1 ms GNSS is not available — devices are deployed underground without access to an external antenna Both devices connect via LTE-M / NB-IoT We have the following questions: What is the expected accuracy of SNTP time synchronization over LTE on the nRF9160? What is the expected accuracy of LTE network time received via NITZ or SIB16 (configurable via AT%XNETTIME )? Are either of these solutions capable of meeting our < 1 ms accuracy requirement? Are there any other Nordic-supported time synchronization solutions that could meet our accuracy requirement given our constraints? Any guidance or alternative approaches would be greatly appreciated. Thank you.

I'm using the prebuilt Aliro stack (libaliro.a, nRF52840), when a session fails inside the library we have no way to get the resulting AliroErrorCode. The stack entry points return void, and HandleTermination carries no code — so internal errors (APDU status, TLV, decryption, invalid state) are invisible to us. We only see "session terminated", with no reason to log or report to our server. Could you expose the session's AliroErrorCode to the application on session end? Since we already implement HandleTermination, the simplest option for us would be to add the error code there, e.g.: void HandleTermination(ConnectionHandle handle, AliroError error); Thanks.

I'm trying to get NFC power-up/restart working on nrf54lDK but the call to sys_poweroff() results in: E: ***** BUS FAULT ***** E: Precise data bus error E: BFAR Address: 0x0 E: r0/a1: 0x400cf000 r1/a2: 0x00000000 r2/a3: 0x00000001 E: r3/a4: 0x00000000 r12/ip: 0x00000000 r14/lr: 0x0007cd37 E: xpsr: 0x81000000 E: Faulting instruction address (r15/pc): 0x0007ccb8 E: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0 E: Current thread: 0x20016318 (unknown) E: Halting system SDK: nRF Connect SDK v3.2.1 Toolchain: nRF Connect SDK Toolchain v3.2.1 board: nrf54l15dk/nrf54l15/cpuapp/ns I added these lines to proj.conf: CONFIG_BUILD_WITH_TFM=y CONFIG_TFM_NRF_SYSTEM_OFF_SERVICE=y but still get the Bus Fault. The sample at 'ncs\v3.2.1\nrf\samples\nfc' does work (not /ns) How can I get this to work for /ns build?

Hi, We have deployed some devices now, and we see quite some modem faults popping up. Could you try to give all info on what you know about these faults we have from the past month? modem_firmware fault_code program_counter count -------------- ---------- --------------- ----- 2.0.2 0x10 0x10f056 86 2.0.2 0x10 0xf6f56 33 2.0.2 0x4 0x7af58 9 2.0.2 0x4 0x92716 9 2.0.2 0x32 0x0 7 2.0.2 0x10 0x1a7754 4 2.0.2 0x10 0x1a582c 4 2.0.2 0x10 0x4a5a6 2 2.0.2 0x10 0x7fbe6 2 2.0.2 0x32 0x10f056 1 2.0.2 0x10 0x735b8 1 2.0.2 0x4 0x173010a 1 2.0.2 0x10 0x10f2f8 1 2.0.2 0x10 0x7813a 1 Thank you.

Environment SoC: nRF54LM20 (DK; silicon reports nRF54LM20B ENGB — also reproduces built for the LM20A target) nRF Connect SDK: v3.3.0-rc2, west v1.5.0 Bluetooth: SoftDevice Controller (peripheral), TrustZone NS build (TF-M) Display: AMOLED driven by the sQSPI softperipheral running on the FLPR (VPR) core, QSPI/Quad, SCK 32 MHz, FLPR HSFLL 128 MHz. Display Buffer streamed in ~52 KB slices via WRMEMST/WRMEMCONT. Symptom The sQSPI transfer aborts mid-buffer with NRF_SQSPI_RESULT_ABORTED (TXUNEXPECTEDIDLE). The display driver retries, but the aborts are frequent enough to be a problem.Occastionally a full system halt. Aborts occur only while BLE is advertising, and only once a bond exists on the device. Connecting stops the aborts; disconnecting (back to advertising) restarts them. Clean reproducible toggle: CONFIG_BT_CTLR_PRIVACY=y and make a bond with a central → aborts; CONFIG_BT_CTLR_PRIVACY=n → zero aborts. or delete bond → zero aborts. Advertising is legacy connectable + scannable (ADV_IND), 200 ms interval. Abort rate scales with

Hi, Does the React Native library for device firmware update found on the link: https://github.com/Salt-PepperEngineering/react-native-nordic-dfu work out-of-the-box on nRF54 family? I found the GATT DFU SMP Service Client in BLE and I wonder if the same protocol is used in this project for updating the firmware over BLE. Best regards!

sacurity failed .... level 1 err 4