I've run into the same "image error" (I'm using the SUOTA Android app) when going through the Training_06_suota_example_v1.1_0.pdf. I've checked the Important note, and tried using the same image for both banks in memory, with no luck. Also I noticed in the app there are banks 0, 1, and 2, what is that about (i thought there were only 2)? I tried creating my own firmware image using the mkimage utility and I get this error: "Invalid Image Size". I'm assuming there is not enough room because the file is 65kB and the memory addresses 0x8000 and 0x13000 maybe only allow for 45kB. I don't understand why there are two images stored in EEPROM when creating the multi-part image bootloader. Can you explain this to me and how it is to be used in production? Do I need to adjust the memory addresses, and do I have to use 2 images in EEPROM? Thanks.
Hi JBaczuk,
Yes, there are only two Banks, if you select 0, then the fw will update the older image thats been downloaded in the flash. Two images are used as a safety measure, if something occurs with the first image (in case the device looses connection or corrupted CRC, etc) to always have a back up in order for the device to boot and execute the SUOTA procedure, i dont get the "how it is to be used in production" question as i dont get the reason for a 65kB image since you wont be able to run this image on the 58x. Yes you will have to use two images in order for the mkimage tool to work and provide the product header into the multibinary file. Adjust the memory addresses, what is the reason for that ? The addresses of each image is read through the product header, the size of each image is more than enough for 58x binary.
Please go through the AN-B-010 using SUOTA.pdf, you will find plenty of info there regarding the SUOTA scheme for your questions and for resolving the same image error.
Thanks MT_dialog