Firmware Update
When the RTLS network is forming, the initiator anchor specifies the firmware version necessary for the network. When an automatic FW update is enabled, any device wishing to participate (join) the network must have the same firmware (version number and the checksum). If a new device does not have the correct firmware, it will be updated as per the subsections below.
Firmware update via Bluetooth
If one wants to update the entire network to a new firmware image while the network is operational, it is sufficient just to update the initiator via Bluetooth. The initiator will then automatically propagate the new firmware to all other devices over the UWB radio link. Note that as the initiator is updated first, it will restart the network, and as each device rejoins the network, its firmware will be updated. Thus, during the FW update, the nodes performing the updat will be “offline”.
Firmware update via UWB
As introduced in the DWM1001 System Overview [4], the nodes will compare their firmware version to the network they want to join. If the firmware version is different, the nodes will try to update their firmware before joining. This firmware update function can be enabled/disabled in the configuration. Here, it lists the rules of the function that the nodes will follow.
Tag:
When enabled, the tag will always check the firmware version and try to synchronise its firmware version with the network by sending the update request to the nearby anchor nodes in the network before it starts ranging.
When disabled, the tag will start ranging without checking the firmware version. This can lead to version compatibility problems and must be dealt with very carefully.
Anchor:
When enabled, before joining the network, the anchor will check the firmware version and try to synchronise its firmware version with the network by sending the update request to the nearby anchor nodes. After having joined the network, the anchor will respond to nearby nodes’ requests to update their firmware.
When disabled, before joining the network, the anchor will directly send the join request and not check the firmware version. This can lead to version compatibility problems and must be dealt with very carefully. After having joined the network, the anchor will ignore the firmware update requests from the nearby nodes.