We PROTEUS-III User Manual page 195

WIRELESS CONNECTIVITY & SENSORS
User manual Proteus-III
Version of the
firmware before the
update
1.x.x
To start the bootloader, one of the following two conditions has to be satisfied:
1. send the command CMD_BOOTLOADER_REQ to the module to restart in bootloader mode
2. during a reset and while restarting, a low signal has to be present on the BOOT pin of the
module to start it in bootloader mode
The bootloader mode has started successfully if LED_1 has turned on. After the bootloader has
started successfully, the module goes into the advertising mode using the name "DFUProteus-
III". Now, any Bluetooth
the Nordic nRF52 Bluetooth
III firmware.
The DFU application of the used App (see Table 80 ) is such an application. For more details,
please refer to chapter 14.2.1 . As soon as a connection has been set up, LED_1 turns off
again and LED_2 turns on.
The implemented Nordic nRF52 Bluetooth
bank method to update the firmware. Thus, the old firmware is only replaced
once the new firmware has been transferred and authenticated successfully.
This prevents the module from being flashed with a faulty firmware.
An OTA firmware update will take several minutes to be performed, the duration
is also dependent on how much of the firmware shall be updated (application
only or complete update).
The max connection interval of the update service is set to 30ms. Please check
whether your mobile supports this speed.
This method is only applicable if the Proteus-III still contains an intact boot-
loader.
Order code 2611011024000
Version 1.8 , July 2022
Version of the new
firmware
1.x.x
Table 80: Compatibility matrix
®
LE device hosting an application that understands the commands of
®
LE DFU Bootloader can connect in order to update the Proteus-
App
Nordic nRF Toolbox 2.7.2 or newer
®
LE DFU bootloader uses a dual
www.we-online.com/wcs
193