The errata for the nRF52 indicates higher consumption in managing timers and GPIOTE. Does the BSP for SDK11 follow recommended practice to deal with these errata can I ask...
Hi,
I am trying to understand the pstorage to record a log for temperature. In my code, I can call pstorage_init(), and clear a block but when I try to store some data...
I would like to source a compact BLE board to act as a lock controller developed with with a matching transceiver for use in a fob and an app.
It would toggle the pio and...
Ok so here is the issue. I was trying to build a simple application which is described in the tutorial for characters. After building an advertisement and understanding the...
I was working with IAR and SDK10.0 before. For some reason I have to transfer my project to Keil and SDK9.0. My program worked well for the old settings. While keeps got NRF_ERROR_SOC_NVIC_INTERRUPT_NOT_AVAILABLE...
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…