Search Result

Hi dear: For 52833, how should I use SPIM3 based on nrf5_sdk.17.1.0? Yang.

We use the NRF Mesh Android Library (and are developing with iOS version as well). An issue that we are running into on a small number of devices is that the library things provisioning failed, but the device being provisioned thinks it succeeded. This leaves the device provisioned with a device key that we cannot access, as the library does not provide a way to access the device key unless provisioning succeeded. We are addressing this on the firmware side, but more generally as a solution we would like to record every device key that we attempted to provision a device with so that we can attempt recovery from the app using these keys. Otherwise these devices end up as RMAs which is very costly when all we need to do is connect to them with the device key and reset them. As far as we can tell, this is

This is a continuation of this ticket. nrf54l15 zigbee end-device is bound with its On/Off client cluster to a On/Off server cluster of another ZigBee smart lamp. I can see with a wireshark sniffing that this device sends when appropriate On or Off commands to the short address it takes apparently from internal table. Now it happened so that for some reason (irrelevant to this case) that smart lamp has changed its short address. So the one nrf54l15 is using is no more valid. Old one: 0xb7cf, new one: 0x56a8 I can see from the sniffed traffic, that after a couple of failed attempts to send the command, nrf54l15 sends a broadcast request to resolve the short address by the IEEE MAC address. And the lamp in question indeed answers that broadcast request, telling it's current short address (0x56a8) to which nrf54l15 also sends an ACK. But that's it: no

I am testing a custom board prototype and having trouble getting I2C to work. During testing, I was able to observe activity on the SDA line, although it consisted of only a single-bit pulse with no address. I also observed a clock signal on SCL when I added an additional pull-down resistor to the SDA line (I discovered this while checking for shorts), which was quite confusing. However, I now suspect that this was simply undefined hardware behavior resulting from an invalid pin configuration. Initially, I was using P2.03 as SCL and P2.04 as SDA, but then I noticed that TWIM has a clock pin requirement. I made a hardware workaround to move SCL to P2.01, but the behavior remained the same. I then noticed another requirement in the datasheet stating that a peripheral can only use GPIOs from the same power domain. According to the block diagram , GPIO

Hi team, Please find below logs. While programing this error occurs. please find the logs and do needful. Earlier programing happens now it's not happened. Based on below logs please suggest what is the issue. The voltages are fine. Recovering device. This operation might take 30s. [error] [ Client] - Encountered error -21: Command recover executed for 14 milliseconds with result -21 [error] [ Worker] - Encountered unexpected debug port ID 0, expected 6 ERROR: Recover failed. Please make sure that the correct device family is given ERROR: and try again. NOTE: For additional output, try running again with logging enabled (--log). NOTE: Any generated log error messages will be displayed. FATAL ERROR: command exited with status 62: nrfjprog --recover -f NRF91 --snr 960020146

Hello together, i am trying to connect to an Azure Blob Storage Container via https with a nrf9160 but I am only getting error 111 (connection refused). For that I am using the https_client sample as first step. I modified the sample: 1. I copied the contents of nrf9160dk_nrf9160_ns.conf to actinius_icarus_ns.conf and added this line to my board config CONFIG_HTTPS_HOSTNAME="xxxx.blob.core.windows.net" 2. Used Firefox to download the DigiCert Global Root G2 certificate (named "blob-core-windows-net.pem". see attachment under /cert). 3. Changed the input file of that nice little function in the CMake file so that it reads in the correct certificate (Digicert): generate_inc_file_for_target( app cert/blob-core-windows-net.pem ${gen_dir}/DigiCertGlobalG2.pem.inc ) Then I am flashing the board and reading the output via a serial terminal. The output is the following (Note: I replaced the actual host and ip with a placeholder): *** Booting nRF Connect SDK v2.8.0-a2386bfc8401 *** *** Using Zephyr OS v3.7.99-0bc3393fb112 *** HTTPS client

Hello, We are using a custom board based on the nRF5340 + nRF7003 Fanstel module with NCS SDK v2.6.2. Our application uses MCUboot with dual-bank OTA updates. The secondary image slot is located in external flash, while application-specific data is stored permanently in internal flash using NVS. During production, we write some configuration data to the internal flash only once. This data is then used by the application during normal operation and communication throughout the product lifetime. The data is not modified after production programming. Issue : We have observed that after a successful OTA update, the data stored in the NVS partition is occasionally erased. The issue is intermittent and difficult to reproduce consistently. It occurs approximately once in every 10 OTA update attempts. Expected behaviour: The NVS data stored in internal flash should remain intact after OTA updates and device reboots. Observed behaviour: OTA update completes successfully. MCUboot

Dear Support, I'm using nCS v3.1.1 and the Matter example project. Could you please provide a simple example showing how to use GPIOTE + DPPI + TIMER capture? My goal: capture the timer value when a GPIO pin level changes (interrupt). I'm not sure how to configure these peripherals correctly. A minimal code example would be very helpful. Thank you. Best regards,

Hello everyone, I have tried several different approaches to solve this issue, but I have not been successful so far. My goal is to generate an interrupt when the LIS2MDL magnetic field measurements (X, Y, and Z) go below a defined threshold. I created a small test application (shown below) to verify the interrupt functionality. I have experimented with many different threshold values, including very low and very high settings, but the interrupt is never triggered. Has anyone successfully used the LIS2MDL threshold interrupt feature with Zephyr or the nRF5340? Am I missing a required configuration step, such as interrupt routing, GPIO configuration, or sensor initialization? Alsi "I'm having an doubt verifying if a trigger was successfully programmed on the sensor. When I configure it like this: The function always returns success (ret == 0), even when I set a trigger type that the sensor theoretically doesn't support. I have

Hi, I am using two nRF52833 devices with the nRF5 SDK. They are paired and bonded to each other. Occasionally, I encounter the following error in peer_manager_handler : Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102 From my understanding, error 4102 indicates a bonding mismatch — i.e., the stored bonding information on the two sides is inconsistent. However, the issue can be resolved simply by power-cycling both nRF52833 devices. After restart, the connection and encryption work normally. Why does error 4102 occur intermittently, and why does a power cycle fix it? Could this be related to improper handling of bonding recovery, flash corruption, or connection context cleanup in the Peer Manager? Thank you.