Device Firmware Update (DFU)
1. Firmware types and update methods
Abeeway devices support firmware updates to keep the applicative (MCU) and BLE up to date with the latest released firmware, if needed. Depending on the device and firmware type, updates can be performed via USB, BLE, or the cellular network.
1.1 Upgradable firmware
The AT3 can only update the following applications:
- MCU application: This is the "Asset Tracker" code (e.g. AT3) defining the top-level application behavior of the device. It runs on the main MCU.
- BLE stack: The BLE subsystem firmware
Both the MT3333 GNSS and the LR1110 chip have upgradable firmware, but these chipsets are flashed in factory and cannot be upgraded by users.
1.2 Firmware upgrade source
The AT3 offers three alternatives, or sources, to upgrade the firmwares listed above:
- USB: The firmware can be updated via USB using XMODEM, except on ATEx/IECEx Zone 1 devices (the USB data tracks are disabled to prevent injection of high voltage) and specific versions requiring military-grade security.
- BLE: The firmware can be updated via BLE using the Beehive tool.
- Cellular: The firmware can be updated over the cellular network (Combo Cellular LPWAN CompactTracker only).
You should be aware that It's important to note that all firmware binaries, regardless of the upgrade source, must be signed.
The device will decline a firmware upgrade request under any of the following conditions:
- No external flash memory available on the device.
- Cellular network not fully configured (see Configuration) — applicable when the FUOTA source is the cellular network.
- No cellular modem present on the device — applicable when the FUOTA source is the cellular network.
- Device operating in SOS mode.
- Low battery condition detected.
- Temperature out of the supported operating range (low or high temperature detected).
The firmware update process over the cellular network consists of two phases:
- Phase 1 — Binary file download: the firmware binary is downloaded and stored in external flash memory.
- Phase 2 — Code transfer: the downloaded binary is copied from external flash into the main MCU's internal flash memory, and the device reboots into the new firmware.
Once the download is complete AT3 verifies that the binary type matches the platform type (e.g., Compact Tracker, Combo Cellular Compact Tracker, Abeeway 1WL EVK). If this check passes, the firmware signature is verified.
1.3 Binary signature
To comply with the new EU security standard EN 18031 (file authentication), all remote firmware upgrade methods now require signed firmware. Signed files are identified by the .sign extension.
The signature is a SHA-256 digest of the binary code, encrypted with Abeeway's Elliptic curve DSA (ECDSA) private key. To verify the signature, AT3 calculates the SHA-256 digest of the downloaded binary file then checks the signature validity leveraging the embedded PKA (Public Key Accelerator) engine.
2. Firmware update methods
2.1 Firmware update via USB
For the badge trackers (except ATEX Zone 1 models), the USB port is accessible through the magnetic connector. For the Compact and Combo Cellular LPWAN Compact trackers, accessing the USB port requires opening the casing.
You should be aware that Abeeway trackers DO NOT derive their power from the USB port when connected to a charger. All power is still provided by the battery.
The DFU via USB can be triggered using the dedicated CLI command:
dfu xtransfer <at3/ble>
The firmware type should be specified as an argument:
- at3: to upgrade the MCU application.
- ble: to upgrade the BLE stack.
Procedure
Connect the device using a USB cable, select the appropriate USB port from your terminal, and open the connection (in Tera Term: File → New Connection).
You must enter your user password (default 123) to obtain a User> prompt before typing further commands.
You can change the user password via parameter 0x010e core_cli_password. Do not set this to 0, as it disables user access entirely. If this happens, contact Abeeway support for a superuser password.
Once you see the User> prompt, you are in interactive mode and can enter further commands.
Before upgrading, it is recommended to back up your current configuration:
- Disable logs to prevent parasitic output:
sys log off. - Display and copy the current configuration:
conf show all.
You are now ready to start the firmware upgrade via USB. From the CLI, type:
User> dfu xtransfer at3
If the upload is successful, after reboot, you will be back at the AT3 command line interface. Enter the user password again, then at the User> prompt, type sys info to confirm the device is running the new firmware.
If the update fails, the device will automatically roll back to the previous firmware.
2.2 Firmware update via BLE
You must use the Beehive tool available at Abeeway guide.
Beehive is optimized for the Chrome browser as it requires BLE connectivity support from the browser.
You must pair the device with your computer before using Beehive. Under Windows, go to "Bluetooth and other device settings", then 'add device' and chose the Bluetooth device category. The computer searches for nearby advertising devices, you may need to click "Show all devices" to see your device. Select the device and click connect.
If you don't see your device, you may need to activate BLE advertising. On the Compact tracker, this requires a magnet (use a strong magnet), and an activation sequence, by default 3 seconds near the hall sensor (small arrow on the casing), then 3 seconds away form sensor, then 3 seconds close to the sensor again.
Procedure
Select Connect a BLE device button in the Beehive tool and select the target device.
After connecting, you will see several options:
- Export config to back-up your parameter set to a file.
- Import config to restore theparamteter set from a backup file.
- Firmware update to initiate an applicative firmware update or a BLE subsystem firmware update.
The firmware updates take about 30s to complete.
2.3 Firmware update via the cellular network (Cellular FUOTA)
The FUOTA overcellular network is only available on only for Combo Tracker devices.
The firmware binary is downloaded over the cellular network using HTTPS (TLS 1.2 with Basic Authentication), ensuring encrypted and authenticated communication.
HTTP Basic Authentication is enabled by default. The device uses the following credentials:
- Username: Device EUI (DevEUI).
- Password: Device hardware hash ID (Base64-encoded on the server side).
If the server does not require HTTP Basic Authentication, the device will proceed with the file download even if authentication is enabled on the device.
The device stores the firmware segments to external flash memory. The download is resilient to temporary disconnections and will resume from the last completed offset.
- The binary download process may require multiple retries. Each retry has a timeout of 300 s (5 min).
- The FUOTA process starts regardless of the network manager configuration. For example, even when the device is configured to use the LoRa network only, the network manager will resume normal behavior once the file download is finished.
- Note that in LoRa-only configuration, application uplinks will be queued and not sent over the cellular network. In other words, the cellular network will be used only for binary downloads. Also, the backup network notification will not be sent when the cellular network is connected, since the backup network is not configured by the user.
Procedure
To test FUOTA, use the following CLI command format:
dfu network <server> <port> <file>
For example:
dfu network raw.githubusercontent.com 443 /AbeewayUser/hosting/main/at3-mctcell-release_v1.3-192-*.bin.sign
In the expected scenario, FUOTA is instead triggered remotely by a downlink command sent from the server (see Application requests section).
3. Configuration management
When FUOTA is performed using a configuration file appended to the new binary (for the MCU application), the device treats the new configuration as described in the Configuration management section.