Running the OTA bootloader GUI & BlueNRG SW

package demo applications

AN4486

18/29

DocID026293 Rev 2

OTA bootloader service. As an example, in our demo platform we use an LED blinking

at higher frequency when connection is established, and this can be used as visual

feedback to obtain confirmation related to the device being addressed. If we realize we

have connected the wrong device, we can simply press the 'Force Disconnection'

button and return to device selection within the combo box. After device selection and

connection through the “Connect” button, we can read the related free memory range

that it advertises, which constrains us to provide an image file compiled with a base

address and size within the expected range on the slave device.

a.

As a next step, we need to provide the “Base address” and press the browse

button to select the location of the file containing the image that we plan to

send over-the-air to the slave device. For that purpose, the user can open the

BlueNRG IAR workspace SensorDemo, LowPower_HigherApp_OTA and

build the related DFU_OTA_Higher_SensorDemo.bin image (available in the

SensorDemo\EWARM\LowPower_HigherApp_OTA\Exe folder) containing a

version of the Sensor Demo that is compiled with base address equal to

0x800e000. Apart from the memory offset, the only difference from

LowPower_LowerApp_OTA is the color of the flashing LEDs (LowerApp

blinks LED_D1, Higher_App blinks LED_D2). Alternatively, user can open the

BlueNRG-MS IAR workspace SensorDemo, LowPower_HigherApp_OTA and

build the related DFU_OTA_Higher_SensorDemo.bin image (available in the

SensorDemo\EWARM_BlueNRG-MS\LowPower_HigherApp_OTA\Exe

folder).

Figure 6: BlueNRG GUI: OTA bootloader search for devices and connect

7

Once we have browsed to the application image

(SensorDemo\EWARM\LowPower_HigherApp_OTA\Exe\DFU_OTA_Higher_SensorDe

mo.bin or SensorDemo\EWARM_BlueNRG-

MS\LowPower_HigherApp_OTA\Exe\DFU_OTA_Higher_SensorDemo.bin) built with