app : nrf tools on git hub
s130: sdk v11
s110: sdk v8.1.0
example : nrf_ble_uart.
after modify, it happen, is there some definition shoud modify in app?
by the war,the...
Hi......
the board advertising correct,and it work normal (connect,send and receive data),bug it's name can not display in app scan menu. the definition is "liu",but displaying...
HI,
with the new version of the bluetooth website, i can not find the link to overview the profile,service,characteristic and something else related to it.
thank you.
I've developed my BLE application that is based on nRF518822 and softdevice S110 v.8.0.0.
I've defined 6 services (4 with 2 characteritics each and 2 with 1 characteristic...
I can get right value when I chose QDEC_SAMPLEPER_SAMPLEPER_512us in slow application ,but in my application my max data rate is more than 2k, so the QDEC value is less than...
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…