This web page creates
the data for DeviceFirmwareUpdate OverTheAir capabilities of Nordic's nRFconnect to update the
CUSTOMER Register area of the
for Ruuvi firmware 2.6.0. This area is dedicated by Nordic as an area in NonVoltial Memory for
User Information Configuration. It begins at
memory location x'10001080' and is 32 words long. Version 2.6.0 only uses the first 9 words. It is preserved across power cycles and is not erased using the
nrfjprog --program file.hex --sectorerase
It is erased with
--eraseuicr as well as
--sectoranduicrerase, --chiperase --eraseall, --recover .
Firmware version 2.6.0 includes a check to insure that the
UICR area matches the version of the code
which sets the tunable parameters.
It also outputs the values used to Segger RealTimeTransfer (aka log ) via j-link if you have the Ruuvi Development Shield. Some of the settings are also transmitted in an advertisment packet
with the first payload byte being x'C0' ( C0nfiguration).
You can copy the hex file from the rose colored area at the bottom of this page and paste it into a file on you laptop/desktop.
Then use nRFutil to create a DFU OTA packet, transfer it to your mobile device and use nRFconnect to update the RuuviTag.
Using this technique it is possible to make changes easily without any programming skills and without installing the entire tool chain necessary to compile and create the firmware image. You can tweak the parameters repeatedly and test them see what the best values for each Ruuvi Sensor.
If you have the Segger j-link program you can view the values used from the log messages reported via JLinkRTTClient (or telnet localhost 19021).
Future versions of this page will create a Device Firmware Update package so you can
change the tunables Over The Air using the