Hello Guys
I'm currently working on a BLE AoA (Angle of Arrival) application using the nRF52833 Development Kit . I’ve run into some challenges regarding hardware connectivity...
Hi
I'm migrating applications I wrote using SDK 17 to nrfConnect 3.0 with Zephyr.
I implemented USB devices with combined multiple USB classes. One of those classes was...
Hi,
I am working on ncs 2.9.1 @ nRF54L15.
I followed this academy course to add a single channel saadc in simple mode:
ADC read works properly, but the current read...
Hi,
In one of our future hardware designs, we have a MPU (running LInux) connected to a Bluetooth SOC over a serial interface (uart/spi/...).
Our first approach was...
Hello everyone,
I'm working on an NRF54L15 DK evaluation board and I need to use NFCT pins as normal GPIOs. I found out here that I should define CONFIG_NFCT_PINS_AS_GPIOS...
Em::Blocks supports now the nRF51 devices from Nordic. You can select in the new project wizard which device family (51422 or 51822) and if soft devices are needed or not.
The templates for the softdevices…
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…