This blog post is a follow up to the Nordic Thingy:52 node.js/Raspberry Pi demos blog post, and will described how you can run and what to expect from each of the Node.js examples that have been provided in the GitHub repository. It will also described an additional example of how you can use the Node.js library to post a tweet based on sensor data.
If you are looking for a Python interface instead of Node.js, please have a look at the following blog post for some more...
This post describes how you can get the ble_app_hrs_freertos example project running in Atollic TrueSTUDIO 8.0 on a pca10040 board. This is a managed make build, it does not rely on the makefile provided by Nordic. No Nordic source files are changed and it even uses the existing gcc linker files from Nordic.
1) Download and install Atollic 8.0
2) Download and unzip nRF_SDK_14.0.0_3bcc1f7.
3) Download the project zip file.
Just a quick post to say that we have ported the Adafruit GFX and SSD1306 libraries to nRF52832. Currently only I2C is supported.
The code can be found here:
Here it's seen working with our Bluey nRF52 development board. More information about Bluey here:
In this project, we’re going to build a BLE Beacon that transmits temperature, humidity and ambient light levels to a dashboard on the internet. Bluetooth Low Energy is a technology that was designed from the ground up to reduce power consumption. It’s common for BLE devices to keep going and going for months on a coin cell battery. A beacon is a typical example of such a device. All it does is wake up periodically, send data, and go back to sleep. There are different methods of connecting to a BLE device. In the case of the beacon...
This example shows a simple GPIO driver for seamless handling of the GPIO and GPIOTE peripherals of the nRF52 series. This example is particularly intended for developers who wish to develop their own driver. The code is available on GitHub at the following URL: https://github.com/NordicSemiconductor/nrf52-drv-gpio-example.
The figure below points out the important Keil GUI buttons for running this example.
Follow these steps to run the example:
Released in December 2016, the new Bluetooth 5 offers truly exciting possibilities for home, industry, and commerce as well as the more traditional areas of wearables and personal devices historically associated with Bluetooth.
Nordic’s nRF52832 is a Bluetooth 5-ready SoC that combines an ARM Cortex-M4F microprocessor with a 2.4GHz multiprotocol radio, supporting Bluetooth Low Energy (BLE).
Zerynth provides a platform for programming nRF52832 boards in Python using paradigms and features typical of personal computer (PC) and mobile programming.
Enabling the use of Python for Microcontrollers and embedded solutions, Zerynth allows:
Bluetooth 5 - now arriving in smartphones
As we know, Bluetooth 5 was launched last December by the Bluetooth SIG. The nRF52 Series from Nordic have always had Bluetooth 5 and its arrival in the mix for the nRF52 Series and this family of SoCs was designed early on to be able to meet the exciting new features of Bluetooth 5. Smartphones play such a key role in most Bluetooth products that their adoption of new Bluetooth features is always eagerly anticipated, as this is fundamental to the use of new Bluetooth features.
The Big News: Samsung Galaxy S8 supports Bluetooth...
The new Bluetooth 5 specification promises twice the speed and 4 times the range. Doubling the speed is achieved by increasing the on-air datarate to 2Mbps, while quadrupling the range is achieved by lowering the bitrate to increase the sensitivity of the receiver. We at Nordic have made a demo showing these features with our newest SoftDevice(s) and specifically our newest chip, the nRF52840. It was showcased at CES 2017 in January.
Here is a more in depth description of the demo.
The demo is based on the ATT_MTU throughput example in SDK 13.0.0-1.alpha, which allows...
PDM stands for pulse density modulation.
PDM is a form of modulation used to represent an analog signal with a binary signal. In a PDM signal, specific amplitude values are not encoded into codewords of pulses of different weight as they would be in pulse-code modulation (PCM).
Currently, PDM is a very popular and low-cost solution particular into mobile telephones.
The detail specification on the nRF52832 can be found at the infocenter.
In this example, we would like to show how to use the PDM interface on the nRF52832 to record and convert to the PCM format. And then, it...
Here is a demo of a small graphics engine I designed that allows me to embark moving pictures on a nRF52832 directly in code with a reasonable occupied memory size (i can do RLE or LZ4 compression).
The screen Newhaven Display (NHD-C12864A1Z-FSRGB-FBW-HT1) which is given for 3 to 4 FPS is here pushed to its limits with some tricks to 8 FPS. The nRF52832 is cool here, for animations i can run up to 100 FPS depending on complexity but the screen cannot follow the cadence (because pixel commutation time is too long and contrast become to weak).
The nrf52832 is quite a competent System on Chip. Even with the long list of errata for the preview release this chip packs a punch.
I've been playing around with this chip for sometime now and have made Github repository for anyone looking to get started. It has a BSD license, so feel free to use it.
Do checkout the UARTE driver Tx implementation, it is specifically done to use the EASYDMA feature to work with a low footprint implementation of printf. It uses a ping-pong buffer concept for this. And unlike the deep...
I've started an nRF52832 library for those devs who are interested in creating their PCB's in Eagle. Its the QFN chip right now. I read somewhere that a BGA version is planned also, so I'll try to add that in the future.
It's located on GitHub here: https://github.com/Jacob-Dixon/Eagle-Libraries