how to Switch between over-the-air and uart bootloader mode?

[balaji]

Hi, How to integrate both over-the-air and uart bootloader application for an device? We have a custom board with nrf51822 chipset, and we need to implement the firmware update process, which can support both over-the-air and usb to uart type firmware update. Since we not yet tested the uart bootloader application, we dont have clear idea on it (like, how to make it enter into the bootloader mode). Can anyone suggest us how to handle this?

our requirement as follows, If the device is connected through the usb, and if the user want to update the firmware, the device should enter into dfu_dual_bank_hci (uart) bootloader mode, and do the firmware update.

And if the device is connected through ble, user should make it enter into the dfu_dual_bank_ble (over the air) bootloader mode by writing some value through the special characteristics created for it, and should do the firmware update.

Regards, Balaji

[balaji]

Thanks for the sample code Hung Bui,

I only tested the ble-bootloader, it is working fine. Before testing the uart-bootloader, i need to confirm, how the bootloader select button works. Since i only have the evaluation board with me(which has two buttons conneccted through gpio 16 & 17) i configured the button0(16) as bootloader select button.

After flashing your application it is entering into the uart-bootloader mode(default), even if i press the bootloader select button it is not entering into the ble-bootloader mode. But if i press after sometime (i didnt calculate the time) it enters into the ble-bootloader mode. I totally confused on it, so i need to confirm it with you that, am i doing anything wrong.

I need one more help regarding USB - SPI firmware update, can i get sample application for this?

Regards, Balaji.

[Hung Bui]

Hi Balaji,

I am afraid that we don't have SPI firmware update soon. It's in the plan but I don't know when we will actually implement it. My suggestion that you can base on the HCI transport layer and port it to SPI. They maybe a little bit different but I don't see any big obstacle here to implement one.