SUOTA Android App

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
3 posts / 0 new
Last post
stanley_yeh
Offline
Last seen: 3 years 6 months ago
Joined: 2016-12-23 06:52
SUOTA Android App

Hi,
I am using DA14585 and trying the sample code named "ble_app_ota" in SDK6.0.4.
I built a hex file for OTA and I also download the Android SUOTA App(3.190.12)
After I pressing the "SEND TO DEVICE" button, it shows "invalid image header".
Is the app capable for DA14585 and SDK6.0.4?
Thanks.

Device: 
MT_dialog
Offline
Last seen: 1 year 9 months ago
Staff
Joined: 2015-06-08 11:34
Hi stanley_yeh,

Hi stanley_yeh,

Yes it is, but you need to follow a procedure (similar to the 580) in order to burn the flash properly and apply the proper headers for each image.

So you will need to create a multipart.bin file that will include two images, the bootloader, and the product header.

  • Take the secondary_bootloader project and change the PRODUCT_HEADER_POSITION definition to match the place that you would like your product header to be, build and convert the .hex file into a .bin file.
  • Use one build from the OTA project (fw_1.hex) and the sdk_version.h (fw_version_1.h) file from the SDK in order to build (warning: change the PRODUCT_HEADER_POSITION  to the corresponding value that the secondary bootloader has) the two images that you will burn into the flash. The command for making the image is mkimage.exe single fw_1.bin fw_version_1.h fw_1.img use the same command with different names in order to create the second image.
  • Use this command in order to create the multibinary mkimage.exe multi spi secondary_bootloader.bin fw_1.img 0x8000 fw_2.img 0x13000 0x1F000 multipart.bin the values 0x8000 is the 1st image offset, 0x13000 is the second image offset and the 0x1f000 is the offset of your product header.
  • After you are done with that, you should burn the image into the flash of the 585.
  • In order to create a new image in order to update the ones in the flash you should run the mkimage.exe single ...... command with the new build and then upload it to your phone.
  • By doing that you should be able to update the new image

Thanks MT_dialog

stanley_yeh
Offline
Last seen: 3 years 6 months ago
Joined: 2016-12-23 06:52
I appreciate your detail

I appreciate your detail explanation. Thank you so much.