Hello,
We are developing a product based on the nRF52840. According to the blog post nRF Connect SDK gets Long-term support with version 3.4.0 , NCS v3.4.0 declares the...
Subject: Request for Optimal Battery Solution for nRF54L15 Matter End Device
Hello DevZone Team,
I am opening this ticket to identify the optimal power solution for my...
Hi,
On the nRF93M1 DK, we can switch between physical SIM and eSIM with %SIMCFG="SimSlot" (mfw 1.5.0).
1. Is SimSlot written to NVM on set, or in the flush at CFUN=0?...
Hello, I've built sample aws_iot for target nrf54l15dk/nrf54l15/cpuapp, using the provided .conf & .overlay files for nrf54l15dk using NCS 3.4.1. The certificates and keys...
We feed the nRF54LM20A’s VBUS pin (the USB high-speed PHY) from the nPM1300’s VBUSOUT, so that the PMIC’s input protection guards the module and the processor sees VBUS only...
Since I wrote about CrossWorks a few weeks ago, several people have mailed me and asked me if I have any sample projects. I didn't, so I just created some.
I've created projects which build blinky_example…
Updated version here (21.04.15): https://devzone.nordicsemi.com/tutorials/7/development-with-gcc-and-eclipse/
I have noticed that there have been several questions on development with Eclipse and GCC…
Atomwear is a micro, modularized, open source, wearable BLE device for DIYers. It makes any BLE(Bluetooth Low Energy) projects easier
Overview - What’s the Atomwear?
Atomwear is a BLE product based…
You may have a nRF51 chip that is "bricked" and both nRFGo Studio and nrfjprog recover option doesn't work. You can try to use J-link Commander to recover. In some case, J-link Commander showed that it…
I created this blog post to document the bugs reported on nRF51 SDK v6.0.0
The workaround for each bug would also be provided here as a temporary solution before the bug is fixed in the future release…
Our most advanced Bluetooth Smart SoftDevice to date is now - S130. We're excited in a big way about this one covering as it does so many different options in one protocol stack.
Again, we always value…