After a successful OTA operation, the succeeding OTA operation keeps giving an error message "Invalid product header" on SUOTA app with an update option to the oldest image-bank.
I would like to try running the OTA operations with two image files to update chip backwards and forwards. Please hint how to solve this situation. Thanks.
The following figures are the comparisons of the header parts between the content read from chip and the content burned to chip, after the successful OTA operation.
A difference is found starting at 0x10008, i.e. the CRC and Version and Timestamp of image. Is there any constraint on the format of the Version string?
Multipart Image Header at 0x0000
Single Image Header at 0x04000
Single Image Header at 0x10000
Product Header at 0x1F000
This is the information read from device on SUOTA app after the successful OTA operation.
Thanks,
Jim
Because the difference illustrates a timestamp of 0xFFFFFFFF, I have added a macro SDK_VERSION_DATE to user_version.h and have made single image(A) with this user_version.h, and reprogram the chip by JTAG with the original mulit image. Then, change SDK_VERSION_DATE to a newer time and again make single image(B). After the first successfully OTA operation with image(A), SUOTA keeps giving the same error message at the succeeding OTA operation with image(B). I cannot find a way to make a second OTA operation work, for in the field our customer may want to verify the functionality between older and newer version backwards and forwards. Please help to solve this situation.