Dear
The BLE Multi-link example (ble_app_multilink_central and ble_app_multilink_peripheral)
shows how one central device can connect to multiple peripheral devices. ...
In the MCP app, if I have the following service data for an Eddystone beacon:
0x10, // Eddystone-URL type
0x00, // TX power in dBm. This is a signed integer so 0xEE ...
I have the nRF Control Panel Android application. It works fine with several BLE devices, but specifically for the Fitbit Flex, it fails to connect.
I know Fitbit wristbandes...
Hi,
The situation:
I was able to successfully receive known packets from a device running gzp_device_dynamic_pairing, from, the host running the gzp_host_dynamic_pairing...
Hi everyone
nrf51822,softdevice s130 2.0.0
now i used softdevice s130 establish two connection as a central with two s110 peripheral device,at the same time i establish...
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…