Firmware updates

This page describes how to update the app-nrf91-origin firmware on the device.

Files

• Firmware Downloads
• Firmware Changelog

info

To find the correct firmware update file please also see the individual product pages.

Updating the firmware

The firmware can be updated either via USB or over-the-air using the Lobaro Platform.

Local via USB

1. Download the ~boot.hex firmware: Firmware downloads.

   note

   The firmware file is named like this: app-nrf91-origin+0.3.5+hw4~boot.hex.

2. Connect the device using the Lobaro USB Config Adapter to your computer.

3. Update the firmware using the Lobaro Maintenance Tool.

Remote using Lobaro Platform

The following prerequisites need to be met to update the firmware over-the-air using the Lobaro Platform:

• The device needs to be connected via NB-IoT or LTE-M.
• The firmware needs to be uploaded to your Lobaro Platform instance by your platform admin.

When all prerequisites are met, create a downlink of type fw for the affected devices on the platform with the following contents. Change the file names according to the desired firmware version.

Firmware update downlink example

{
  "d": {
    "app": "app-nrf91-origin+0.3.5+hw4.hex",
    "boot": "app-nrf91-secure+0.2.1.hex"
  },
  "q": "fw"
}

See IoT Platform Documentation → Devices → Downlinks on how to create downlinks.

For platform admins, the firmware can be downloaded here: Firmware downloads.

Remote via MQTT

This option is intended for customers who operate their own MQTT backend and do not use the Lobaro Platform. For device management and executing firmware updates over MQTT using the Lobaro Platform, please refer to: Remote using Lobaro Platform.

Firmware updates and configuration changes without the Lobaro Platform can be performed using the MQTT device synchronization mechanism described in MQTT → Device Synchronization.

Any backend implementing this specification should manage devices via MQTT, including:

• Telemetry and device uplink handling
• Device state synchronization
• Configuration synchronization
• Chunked over-the-air firmware transfer (app and boot)

A reference implementation of such a backend is available upon request. Please contact: support@lobaro.de

It can be used for evaluation, testing, or as a starting point for a custom backend implementation.

The MQTT broker may be:

• A self-hosted broker (e.g. Mosquitto)
• A cloud MQTT service
• A public MQTT broker