AN4486

Running the OTA bootloader GUI & BlueNRG

SW package demo applications

DocID026293 Rev 2

17/29

connect and play with the Sensor Demo application just loaded on the

development platform at step 2.b. Just to verify that an ordinary BLE

application has services coexisting with the OTA bootloader service which will

run next.

e.

(Optional) If actions at step 2.d were taken, disconnect the “BlueNRG app for

smart phones (IoS or Android)” enabled device from the development kit

platform. The Sensor Demo application will be disconnected and it will start

advertising. This will make this application a potential candidate for a BLE

OTA upgrade through the BlueNRG GUI.

3

Program the second platform with the required application to be used with the BlueNRG

GUI (BlueNRG_VCOM_x_x.hex file available on the BlueNRG DK SW package, on

Firmware\STM32L1_prebuilt_images folder).

4

Open the BlueNRG GUI on the PC and select the COM port related to the BlueNRG

platform configured in step 3, through the drop-

down “Port” and press “Open”.

5

Select “Tools” -> “OTA bootloader” to open the dialog box containing the OTA

bootloader actions and press “Search for devices”.

Figure 5: BlueNRG GUI: OTA Bootloader window

6

After “Search for devices”, the GUI will start the discovery process and return

information related to the address and application names of devices running the OTA

bootloader service within the radio range. Once the previous process ends, the device

list can be opened through the combo box arrow below the “Search for devices” button,

and the user is free to choose the device to connect for the bootloader process using

the “Connect” button (application address & names are displayed). In scenarios where

device address and application running are not enough to identify the right device, we

recommend to implement a connection active indicator on slave devices running the