Running the OTA bootloader GUI & BlueNRG SW

package demo applications

AN4486

20/29

DocID026293 Rev 2

8

The process is complete when the status indicator reaches 100%, as shown below.

Figure 8: BlueNRG GUI: OTA Bootloader upgrade completed

If we observe the slave board, we will find a change of color in the flashing LEDs notifying

us that a new application is running. Tools such as the STM32 STLink utility can be used to

check downloaded Flash memory regions on upgraded devices against the image within

the selected binary files. After disconnection from the master, we can re-check the new

version of the Sensor Demo functions against a “BlueNRG app for smartphones (IoS or

Android)” as performed in step 2, optional items.

Note: A similar procedure can be used for the BlueNRG BLE_Chat demo application in

order to verify the BLE OTA bootloader service functions (refer to the

BLE_Chat\EWARM\BLE_Chat.eww, Server_LowerApp_OTA, Server_HigherApp_OTA

workspaces for BlueNRG device and to BLE_Chat\EWARM_BlueNRG-MS\BLE_Chat.eww,

Server_LowerApp_OTA, Server_HigherApp_OTA workspaces for BlueNRG-MS device).

4.2

BLE application built to use the BLE OTA Service Manager

The following is a step-by-step description of how to run the BlueNRG GUI OTA bootloader

using the BlueNRG OTA Service Manager and Sensor Demo, OTA_Basic workspace:

1

Plug the two developments platforms into the USB connectors on a PC.

2

Use the BlueNRG GUI to program one of the two platforms kits to be used as OTA

bootloader slave. This requires plugging the board into the USB connector on the

PC running the GUI, then pressing the platform reset button while keeping the

BUTTON_1 pressed in order to start the DFU bootloader (LED_D2 should be

blinking at this point).