The NRF24L01+ chip is used in many MySensors projects. This chip depends on an additional processor like an ATMEGA. With Nordic Semiconductor NRF5 series a powerful alternative as combination of CPU and Radio is available.

The NRF5 chips have an on-chip radio module which is compatible with the NRF24 series or BLE. At the current state, BLE is not supported by MySensors. The NRF5 series has a lot of internal Hardware:

• ARM Cortex-M0 (NRF51)/Cortex-M4 with FPU (NRF52)
• 16k-256k RAM
• 128k-1M Flash
• 31 GPIO ports
• ADC
• Timers + RTC
• Hardware Number Generator
• Internal temperature sensor
• SPI
• I2C
• UART
• Watchdog timer
• Comparator and Low Power Comparator
• PWM
• AES (encryption, CCM for encryption, ECB for hashing)
• USB (nRF52840)
• ...

With Shortcuts and the PPI (Programmable peripheral interconnect), the periphery can do a lot, work without CPU interaction like enable or disable radio on a timer event.

Buying guide

At the moment two series are available. The nRF51 series including the nRF51822 (BLE license) and nRF51422 (BLE & ANT+ license) and the nRF52 series including the nRF52832. An enhanced version, the nRF52840 is in hardware development and currently not available and not supported by MySensors.

There are a lot of modules available. If you plan to use an nRF5 module with MySensors you have to choose a Version with the high-frequency oscillator, this is included in most modules available.

If you plan a battery-powered sensor, you should choose a module including the low-frequency oscillator (32,768kHz) for precise low power sleep modes and the inductor the for DC/DC regulator.

The NRF52 do things faster while consuming less power. The chip is more flexible. For most flexibility and compatibility, only use nRF52 chips.

Required Hardware and Drivers

Most nRF5 modules comes without programmer and serial converter. You need to buy a dedicated programmer (CMSIS-DAP/DAPLink 1.5, J-Link or ST-Link v2) and mostly a 3.3V serial converter(J-Link and ST-Link). With Linux most programmers and serial adapters are supported. With Windows, you have to look if a signed driver is available for your programmer and serial device.

A proven variant to start program various devices without dealing with a lot of drivers or bad hardware is to buy a RedBear BLE Nano2 kit.

Don't buy an nRF5 development kit to program other nRF5 modules. The programmer is hard wired to the nRF5 chip on most DK boards.

Linux

With Linux, you can use any type of supported programming adapter (J-Link, ST-Link v2 and DAPLink). For fixing the permissions a file "/etc/udev/rules.d/50-programmer.rules" is required. You have to add your user to the "plugdev" group.

# CMSIS-DAP
ATTRS{idVendor}=="0d28", ATTRS{idProduct}=="0204", MODE="664", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="0d28", ATTRS{idProduct}=="0204", MODE="664", GROUP="plugdev"

# J-Link
ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0101", MODE="664", GROUP="plugdev"
ATTRS{idVendor}=="1366", ATTRS{idProduct}=="0105", MODE="664", GROUP="plugdev"

# ST-Link
ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3748", MODE="664", GROUP="plugdev"

Windows

For windows, you need to install the correct driver. A good starting point is to use Zadig which installs a lot of drivers. When it's not working you can install the correct driver manually:

• CMSIS-DAP: Driver Setup for mbed devices
• J-Link: Zadig
• ST-Link: ST-LINK, ST-LINK/V2, ST-LINK/V2-1 USB driver signed for Windows7, Windows8, Windows10

If you have trouble with J-Link adapters, install the original Software (J-Link Software and Documentation pack for Windows](https://www.segger.com/downloads/jlink)), start "J-Link Configurator" for firmware updates and remove all software and drivers and restart zadig to install WinUSB.

OSX

"No additional setup required." Look at https://github.com/sandeepmistry/arduino-nRF5/#os-x

Preparing Arduino

Arduino doesn't support the nRF5 platform in a standard setup. You have to add the arduino-nRF5 platform via Arduino's Board Manager like described in https://github.com/sandeepmistry/arduino-nRF5/#installing

Configure MySensors

Use actual development snapshot https://github.com/mysensors/MySensors for your MySensors installation.

There is no need to configure anything special to create a MySensors Node or Gateway. Add a "#define MY_RADIO_NRF5_ESB" to your sketch to enable the radio device in Enhanced ShockBurst mode (ESB). This mode is compatible with MySensors nRF24 implementation.

Migrate code

EEPROM like memory

The nRF5 MCU has no EEPROM memory like AVR controllers. The internal flash can erased 10,000 (nRF52) or 20,000 (nRF51) times per page. To extend the lifetime there is implemented a NVRAM class. By using hwReadConfigBlock, hwWriteConfigBlock, hwReadConfig or hwWriteConfig the memory can accessed.

Any write operation is added to an internal log. This operation is fast until the log is full. When the log is full, a new flash page from an internal pool is written. This process can take up to 4 seconds. If you need to write often in a time critical situation, call the MySensors "sleep" function with a time > 5000ms. This forces to clear the log when its not possible to write more than 32 bytes.

The number of available writes per byte depending on the highest address written in NVRAM. When you only use the first 8 Bytes of the NVRAM, you have 5,100,000 write cycles per byte. If you use all 3072 bytes available, you have only 3,300 write cycles per byte.

GPIO Input mode

Many of MySensors examples configure input with a pullup resistor by writing high to the input pin. This didn't work:

// Incorrect
// pinMode(BUTTON_PIN,INPUT); // Setup the button
// digitalWrite(BUTTON_PIN,HIGH);   // Activate internal pull-up

// Correct
hwPinMode(DIGITAL_INPUT_SENSOR, INPUT_PULLUP);

GPIO Output mode

If you configure a pin as OUTPUT pin with pinMode command, the pin can drive a current of 2mA without violating the specification. If you want to use more current, you have to switch to the "High Drive" mode. Please read the GPIO documentation at https://infocenter.nordicsemi.com

At the moment on Arduino, there is no definition of various OUTPUT modes. If you want to access all nRF5 output modes, you have to use hwPinMode and the OUTPUT_... macro. The modes available are:

• OUTPUT_S0S1 -> Standard 0, Standard 1
• OUTPUT_H0S1 -> High Drive 0, Standard 1
• OUTPUT_S0H1 -> Standard 0, High Drive 1
• OUTPUT_H0H1 -> High Drive both
• OUTPUT_D0S1 -> Disconnected 0, Standard 1
• OUTPUT_D0H1 -> Disconnected 0, High Drive 1
• OUTPUT_S0D1 -> Standard 0, Disconnected 1
• OUTPUT_H0D1 -> High Drive 0, Disconnected 1

Interrupts

If you create your own interrupt routines, please use the NRF_RESET_EVENT macro to reset an event. This macro incorporates with the caching of NRF52 MCUs.

NRF_RESET_EVENT(NRF_RADIO->EVENTS_END);

Watchdog timer

The MySensors port for nRF5 supports using the Watchdog. You can use the same commands like defined in "avr/wdt.h" but disable cannot disable the watchdog. The watchdog is set to a period of 36h of CPU runtime.

When the CPU is in a sleep mode, the watchdog timer is stopped.

Don't set the watchdog timeout below 4500ms, this can conflict with the usage of the NVRAM (s. EEPROM like memory)

Known Issues

While sleeping and wait for a pin change, the current consumption is 1mA on older nRF51 chips. The fix is documented at http://infocenter.nordicsemi.com/pdf/nRF51822-pan_v3.0.pdf

If '#define MY_DEBUG' is disabled, the radio doesn't handle ping packages. There are timing issues with the implementation of the protocol.