About the SUOTA

Hi Bean

I cant't understand how you 've created the product_header.txt.

Please follow the instructions below for working with SUOTA.

1) Create the first image: mkimage.exe single fw_1.bin fw_1.h fw_1.img enc

2) Create the second image: mkimage.exe single fw_2.bin fw_2.h fw_2.img enc (you can use the first image as well)

3) Create an image for the whole SPI memory: mkimage.exe multi spi secondary_bootloader.bin fw_1.img 0x8000 fw_1.img 0x13000 0x1F000 multipart.bin

4) Burn it into flash using smart snippets.

For the file fw_1,2.h please rename the file from \dk_apps\src\dialog\include\ ble_580_sw_version.h

Please try this and let us know.

Thanks MT_dialog

Hi Bean

Erase the FLASH first and yes, burn the multipart.bin into flash at address 0 and when windows promts you for Bootable select NO.

After that you should reset your device and it should start advertise.

Thanks MT_dialog

Hi Bean,

Are you changing the values of the db address from the nvds.c file?

Please try changing other credentials of the device, like name, also try to change the DA14580_SW_VERSION from the ble_580_sw_version and let us know what happens.

Thanks MT_dialog

Hi Bean,

You can take as example the proximity or the Smart Tag reference designs they both support SUOTA capabilities. The smart Tag is a little bit more agile. Make sure that the SPOTA profile in the da14580_config is enabled. See also Smart Tag reference application doc for further instructions.

Thanks MT_dialog.

Hi Bean

What do you mean that the values of the image bank from your example is 0 or 1?

The choices from the smartphone app are:

1)Place the new image in memory bank 1 (memory bank 1 has 0x8000 offset).

2)Place the new image in memory bank 2 (memory bank 2 has 0x13000 offset).

3)Place the new image on top of the oldest image (for instance bank number 1 which hold the oldest image).

At the offset 0x00000 is the secondary bootloader located and at the offset 0x1F000 is the product header located.

Within the next week there's going to be a new release application note about SUOTA.

Thanks MT_dialog

Hi Bean

Yes, after you select the file, and you want to download it to your device the android application will let you choose on which memory bank the image will be placed......1. memory_bank_1(0x8000), 2. memory_bank_2 (0x13000) or the default choice 0. where the new image will replace the oldest image in the memory located either in memory bank_1 or memory bank_2.

Thanks MT_dialog

Hi Bean,

Yes its normal, when you download two images (the multipart.bin) the device (after the restart)loadsthe first image (bank1), when you update the image with a new one (throught suota) it will use the first bank.Then when you update again(throught suota)a new image the device will know which is the latest downloaded image and will replace the oldest image with the new. In essence it follows the turn each image has been updated.

Thanks MT_dialog

Hi MT_Dialog,
Regarding to the post above, if we have 2 different images like img_1 in memory bank 0 and img_2 in memory bank 1. Is there a way to select the memory bank to select the appropriate img_2 for the type of application.
Thank you!

Hi iqspring,

You can have a look at the secondary_bootloader code and modify it in order to set the appropriate conditions to load the image file you want.

Thanks MT_dialog