Skip to main content

Firmware Update (Using Abeeway Updater)

This section describes how to carry out the firmware update using Abeeway updater. There are two important firmware in the tracker that need frequent update (MCU Firmware and BLE Firmware). Here are the keys steps to carry out for the firmware update:

WARNING
  • Abeeway Updater is only supported in Windows and Linux
  • For update of large number of trackers with Smart badge docking station or USB hub, please ensure using ONLY Linux with the specific distribution/hardware PC model in Abeeway Updater documentation.
  • Ensure you are using USB data cable or smart badge docking station that supports data transfer
  • Ensure the correct MCU and Firmware binaries are selected that match the hardware model. Incorrect firmware might damage the tracker permanently.
  • Ensure that the MCU firmware config file has no invalid or non-existing parameters that are not present in the MCU/Application firmware. Please cross-check the config file parameters are present in Abeeway Firmware Reference Guide. Any invalid or non-existing parameters in firmware config file that do not match the firmware binary will be rejected and the configuration will not be applied correctly. The example firmware config files are available here.
  • The firmware parameters can change between different MCU Firmware versions. Please ensure to refer to the reference guide that is matching the MCU firmware version.
  • The config file should only have parameters that are changed from factory default to reduce the size of the config file. The factory default of all the firmware parameters can be found in Abeeway Firmware Reference Guide
  • The flash size of the firmware is very limited. Please avoid putting large number of parameters in the config file. The config file is appended to the firmware binary at the end of firmware update process. If this appended file is bigger than the flash size, the tracker might be damaged permanently and will void the warranty. The combined file size of MCU firmware binary and config file should not exceed 240KBytes. For changing more than 10 parameters, please refer to Abeeway Updater (see chapter: Updating ONLY the tracker configuration). Alternatively, you can also use Abeeway Device Manager (device configuration tab) to send LoRaWAN downlinks.
  • Before carrying out the firmware update for large number of trackers in the field, please carry out the firmware update of few trackers and check the configuration using Tera term or similar serial communication tool. You can check the configuration of the tracker by entering config show on the serial console. This will avoid potential mistake when carrying out firmware update for the large number of trackers. Please visit here on how to interact with the CLI over USB port.
  • Abeeway Updater or any other serial communication tool, like Tera term should not be running simultaneously. The tracker can only communicate with one of them at a time.
  • For any issues with USB port, please refer to Abeeway Updater documentation, Chapter: troubleshooting USB port

  1. Install the required software from here

  2. Identify your tracker model from here

  3. Download the MCU/BLE Firmware binaries and config file from here

  4. Update the firmware using Abeeway Updater

  5. Check the firmware configuration on CLI using serial console application application application, like Tera term. You will need to enter config show to check firmware configuration on CLI. Please visit here on how to interact with CLI over USB port.

Last updated on