Search Result

Hello, I have 2 Memfault projects that I'd like to rename, but I can't find any way to do this through the web app, and the API authorization keeps getting rejected (tried with organization auth token, as well as email + password). I'm not sure if it's not available to users or just not supported. Would it be possible to have them renamed? Thank you!

Hello, I'm working on a prototype device based on the nRF9151 DK. HW: nRF9151 DK, nRF9151 LACA A1A Tested with modem_shell sample app, NCS v3.4.0. Symptom: on boot, "The modem reports a UICC failure. Is SIM installed?" / Network registration status: UICC fail. Diagnostics: AT%CSUS? --> 0 (physical UICC slot correctly selected) AT+CFUN=4 --> +CFUN: 4 ; SIM_VCC on J5 C1 = 0 V (correct) AT+CFUN=41 --> OK ; SIM_VCC pulses ~360 ms with retries Oscilloscope at the socket during activation: CLK clean 1.818 MHz (varies 200 kHz-1.8 MHz across retries), RST 2-3 pulses ~100 ms, I/O shows clean digital data - the card IS responding AT%XSIM? --> 0 AT+CPIN? --> ERROR AT+CEER --> +CEER: "UICC 0" Ruled out: SIM card: 1NCE, Onomondo, Conexa - all identical NO ATR Modem FW: mfw_nrf91x1 2.0.4, 2.0.3 - all identical Config: AT%XFACTORYRESET=1 performed, no change; %CSUS=0 Modem drives VCC/CLK/RST correctly and the card

Hi Nordic Team, I am trying to implement a secure boot chain on the nRF54L15 DK using NCS v3.4.0 (LTS) with the following configuration: Board: nrf54l15dk/nrf54l15/cpuapp NCS version: v3.4.0 Boot chain: NSIB MCUboot Application: BLE SMP FOTA using MCUmgr I followed the available Nordic documentation and DevZone recommendations to configure NSIB + MCUboot together. sysbuild.conf: # Enable two-stage boot chain SB_CONFIG_SECURE_BOOT_APPCORE=y SB_CONFIG_BOOTLOADER_MCUBOOT=y # ED25519 keys SB_CONFIG_SECURE_BOOT_SIGNATURE_TYPE_ED25519=y SB_CONFIG_BOOT_SIGNATURE_TYPE_ED25519=y # Store MCUboot verification key in KMU SB_CONFIG_MCUBOOT_SIGNATURE_USING_KMU=y # Signing keys SB_CONFIG_SECURE_BOOT_SIGNING_KEY_FILE="${APP_DIR}/keys/nsib_priv.pem" SB_CONFIG_BOOT_SIGNATURE_KEY_FILE="${APP_DIR}/keys/mcuboot_priv.pem" # Generate KMU provisioning file SB_CONFIG_MCUBOOT_GENERATE_DEFAULT_KEY_FILE=y prj.conf: CONFIG_SERIAL=y CONFIG_CONSOLE=y CONFIG_UART_CONSOLE=y CONFIG_LOG=y CONFIG_LOG_BACKEND_UART=y CONFIG_PRINTK=y CONFIG_LOG_MODE_IMMEDIATE=y CONFIG_BT_PERIPHERAL=y CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y CONFIG_MCUMGR_TRANSPORT_BT_PERM_RW_AUTHEN=y Flashing I perform a full recover before programming: west flash --recover and Programming completes successfully without any reported errors. Relevant output: -- west flash: rebuilding [0/8] Performing build step for 'app' ninja: no work to do. [1/8] Performing build step for 'mcuboot' ninja: no work to do. [7/7] Completed 'mcuboot' WARNING: Specifying runner

As in subject, psa_aead_finish function generates incorrect tag for AES-GCM when Nordic proprietary library is used. Works fine with Oberon backend. Similar problem reported 3 years ago: RE: Enabling CONFIG_PSA_CRYPTO_DRIVER_CC3XX causes incorrect tag when using AES-GCM , there it was related to too short nonce. Tested with NCS 3.3.0 and 3.4.0 on nRF5340. Below code compares authentication tag generated by single-part and multi-part PSA Crypto API on the same iv, auth data, key, plaintext. #define ASSERT_PSA(func, ...) \ { \ psa_status_t s = func(__VA_ARGS__); \ if (s != PSA_SUCCESS) { \ printk(# func " failed: %i\n", s); \ goto exit; \ } \ } void test() { psa_key_id_t k_id = -1; { ASSERT_PSA(psa_crypto_init); uint8_t key[32]; ASSERT_PSA(psa_generate_random, key, sizeof(key)); psa_key_attributes_t key_attr = PSA_KEY_ATTRIBUTES_INIT; psa_set_key_usage_flags(&key_attr, PSA_KEY_USAGE_ENCRYPT); psa_set_key_algorithm(&key_attr, PSA_ALG_GCM); psa_set_key_type(&key_attr, PSA_KEY_TYPE_AES); psa_set_key_bits(&key_attr, PSA_BYTES_TO_BITS(sizeof(key))); ASSERT_PSA(psa_import_key, &key_attr, key, sizeof(key), &k_id); uint8_t iv[12]; ASSERT_PSA(psa_generate_random, iv, sizeof(iv)); const uint8_t AUTH_DATA[] = {'T', 'e', 's', 't'}; const uint8_t

Hi, I have a question with regard to the nPM1100 PMIC and entering ship mode (not exiting it). If I am interpreting the datasheet correctly, the SHPHLD pin must be held HIGH prior to activating ship mode via SHPACT (correct me if I am wrong). The reference schematic in section 7.1 of the datasheet shows SHPHLD connected to VBAT via a 100k resistor and a switch connected to GND to pull it LOW when pressed. In my scenario (no MCU involved) I want to be able to enter ship mode at the press of a button that sets SHPACT to HIGH (by connecting VSYS?), however, I don't need the switch with SHPHLD as I can exit ship mode bby connecting VBUS (the USB cable). My questions are, 1. If I don't need the switch on SHPHLD, do I just connect SHPHLD directly to VBAT? 2. Do I still need the

Category: Bluetooth / Channel Sounding --- Hardware: - Board: nRF54L15DK (nrf54l15dk/nrf54l15/cpuapp) - nRF Connect SDK: v3.1.0 - Sample: nrf/samples/bluetooth/channel_sounding_ras_reflector - Build command: west build -p -b nrf54l15dk/nrf54l15/cpuapp -- -DEXTRA_CONF_FILE=android_ranging.conf Mobile device: - Device: Google Pixel 10 - Android version: 17 - nRF Toolbox version: 4.3.2 --- Issue Description: When connecting the channel_sounding_ras_reflector sample (built with android_ranging.conf) to a Pixel 10 running Android 17 via nRF Toolbox v4.3.2, the CS setup phase completes successfully up to and including CS security enable. After that, no CS procedures ever start and no ranging data is produced. The app appears stuck — no distance measurements are shown and there is no further activity. --- Steps to Reproduce: 1. Build and flash channel_sounding_ras_reflector with android_ranging.conf on nRF54L15DK 2. Open nRF Toolbox v4.3.2 on Pixel 10 (Android 17) 3. Navigate to the Channel Sounding / Ranging tile 4. Connect to "Nordic CS Reflector" 5. Complete BLE

Hi Nordic Support, I am facing an issue where the peripheral registers are not visible in the Keil debugger during a debug session. Only the core registers are available, and I am unable to access peripheral registers through the System Viewer. Development Environment: IDE: Keil MDK-ARM (uVision) v5.43.1.0 Nordic SDK: nRF5 SDK v17.1.0 Debug Probe: J-Link Device: nRF52840 Board Details: Marking on PCB: 10056 Hardware Revision: 3.0.3 Issue Description: The application builds, programs, and runs successfully. During debugging, the peripheral registers are not visible in Keil's System Viewer/Peripherals window. I expected to see peripherals such as GPIO, UART, TIMER, etc., but they are missing. Could you please let me know: Is there any additional configuration required in Keil to enable the peripheral register view? Does this depend on a specific Device Family Pack (DFP) or SVD file? Is this a known issue with this board or SDK version? Any guidance

Hi: Use nRF54LM20A_DK. Use ncs 3.1.1. And this is source code: devzone.nordicsemi.com/.../4477.boards.zip The following error occurred: « *** Booting nRF Connect SDK v3.1.1-e2a97fe2578a *** *** Using Zephyr OS v4.1.99-ff8f0c579eeb *** Hello World! nrf54lm20dk/nrf54lm20a/cpuapp HF clock started W: Experimental DMA enabled E: Failed to allocate net_buf 4095 E: Buffer for data|status is missing E: Malformed setup packet E: Failed to allocate net_buf 4095 E: Buffer for data|status is missing E: Malformed setup packet E: Failed to allocate net_buf 4095 E: Buffer for data |status is missing E: Malformed setup packet E: Failed to allocate net_buf 4095 E: Buffer for data|status is missing E: Malformed setup packet

Hello, I use the NCS v3.3.0 (ncs\v3.3.0\nrf\applications\nrf_desktop). Can the desktop dongle connect to two keyboards at the same time? Development boards: two nrf54lm20‑dk (using the build for nrf54lm20b) and one nrf52840dongle (using the build for 52840dongle). Initially, I configured both nrf54lm20‑dk boards as MOUSE devices. They could both connect to the nrf52840dongle simultaneously, and message reporting from both devices worked normally. Later, I configured both nrf54lm20‑dk boards as keyboards and modified the prj.conf of the nrf52840dongle. I found that I could pair both keyboards, but they cannot stay online at the same time. If both are online concurrently, the nrf52840dongle freezes/crashes. Neither a long press nor a short press of SW1 has any effect, and no log is output. The only way to recover is to power cycle the dongle. Logs and prj.conf of nrf52840dongle, as well as prj.conf of nrf54lm20dk are attached below for your reference. Below is the

With SDK 3.3.1 I do not get the logging messages when building the Hello World app unless CONFIG_LOG=y is added to prj.conf. Perhaps this is left as an exercise for the reader! Nordic AI says " Note that in nRF Connect SDK, CONFIG_LOG (along with CONFIG_LOG_MODE_MINIMAL ) is automatically enabled for all samples via CONFIG_NCS_SAMPLES_DEFAULTS ." but this doesn't seem to apply for the Hello World sample.