We are proud to present our new BLE DEVKIT.N main Board for nRF51822 Development Kit. It is a must for every bluetooth low energy developer using nordic tools.
Some of the feature
- Easy access to all GPIO pins(P0.00-P0.30) by multiple types of connectors, suitable for any applications and extension boards
- Easy tracing via printf redirecting to serial communication port
- Different ways to power up the nRF51822 Development Kit, via USB, coin cell battery(CR2032) or external power supply(5V-30V)
- Full compatibility with Nordic SDK examples, so not need to reconfigure any pins for buttons or LEDs. Just works
- BLE DEVKIT.N provides a room for mini prototype breadboard giving additional flexibility to the developer
- DIP switches(SW1,SW2,SW3) allow an easy connect/disconnect of buttons, LEDs and USB-to-UART bridge to the GPIOs
BLE DEVKIT.N R1
More info at BLE DEVKIT.N
For embedded hardware tracing and debuting is a vital step to a stable product. Unfortunately it is not all the time a easy task. Luckily BLE DEV.N board has an option to trance and debug via serial port.
You need to:
- add #include “mk_trace.h”
- initialise the mk_trace service with: mk_trace_init(256,256);
- add trace messages like: mk_trace(“ADV START: %d\n\r”, m_advertising_mode); or mk_trace(“ERROR code: %d, line: %d file:%s….)
- run some terminal software like putty with com port number(using Device Manager) and speed: 921600
P.S. You can find the service code and sample at github .
We updated User Manual for the BLE DEV.N R2 Board with more detailed explanation about change which is needed because of the crystal we use on the board. When you try to run all Nordic Bluetooth Low Energy examples (ble_…) with our board, you need to change clock source to NRF_CLOCK_LFCLKSRC_SYNTH_250_PP in SOFTDEVICE_HANDLER_INIT macro like this SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM...
It will make initialisation of the SoftDevice to pass successfully and your example with not hang anymore.
Just uploaded sample application, which can connect to the Bluetooth SensorTag (CC2541) and display ambient and IR temperature. In order to run it is good to have Apple machine with Bluetooth 4.0 (Bluetooth Low Energy support).
It supports connection to multiple Bluetooth SensorTags (CC2541)
but is not tested. Sorry I have just one!
Today we experimented to program BLE DEV.N R2 ST-LINK/V2 from STM32F3DISCOVERY and “hourra”(hurray)! It was possible to program it and debug it step by step directly from IDE.
BLE DEV.N with ST-LINK/V2
BLE DEV.N R2, ST-LINK/V2, Keil IDE
We expect that probably will be possible even to use the cheapest board from ST 32F0308DISCOVERY
and tomorrow we will test with it too.
So one more option to program and make fun!
Happy Christmas Everyone!
We just publish the user manual for the BLE DEV.N board, revealing lot about the product and it’s usage.
We also tested the board with Nexus 5, Android 4.4 and it works like a charm. Meanwhile Nordic Semiconductor releases richly-featured nRF Toolbox for Bluetooth smart development on Android with memory efficient DFU, so Android fans can start coding and experimenting with full speed.
Today we added blinky example to the SDK. It assumes that board is pre-programmed with SoftDevice and Bootloader. If you do not have such, you need to change memory areas as follows IROM1 start 0x0, size 0x40000, IRAM1 start 0x20000000, size 0x4000 for 256k chip.
Now, it is possible to upload custom code using on BLE DEV.N board USB-Serial connection. This will remove the need of owning a programmer (which are quite expensive). I think it will make happy all the hobbits who does not have bugged to buy, but have the passion to explore magic of the Bluetooth Low Energy (BLE) and do nice gadgets talking with their smart phones.
Here is the detailed document BLE DEV.N DFU v1.0
It starting to be really interesting seeing the first application using iBeacon. Will be competitor to NRF or?
Apple iBeacons in the Store
Taking stock of Apple’s iBeacon
Today I found a very interesting research paper about
Power Consumption Analysis of Bluetooth Low Energy, ZigBee and ANT Sensor Nodes in a Cyclic Sleep Scenario. Not a surprise, BLE is the winner.
“We found that BLE achieved the lowest power
consumption, followed by ZigBee and ANT. The
parameters that dominated power consumption were not
the active or sleep currents but rather the time required to
reconnect after a sleep cycle and to what extent the RF
module slept between individual RF packets.”