Hello support
I am working on SDK 1.08.
I am now working on software update over the USB implementation.
I implemented USB CDC in my project for now and it work well.
I am able to write to the NVMS_GENERIC_PART in the flash without problem, thus it should be possible to perform firmware update also.
I checked the flash partition table and use the one given for suota.
Is there some king of application note describing the whole procedure? The SDK is told to be SUoUSB compatible but i did not find information about this
Should i write the firmware directly in the NVMS_FW_UPDATE_PART ?
Should i set some flags or headers?
是新的firmaware t自动转移he NVMS_FIRMWARE_PART in the flash at start up?
Thanks for your help.
Matthieu
Device:
Hi matthieuW,
The SUoUSB is something that it is not officialy released yet, the implementation and the structure behind the SUoUSB are still under evaluation, currently there is no documentation or example application for this feature. As far as i am aware the update over USB is quite the same with the over the air procedure, the new updated image will reside in the Firmware Update Partition and then the bootloader, after the update has finished and the device has rebooted, will check for a valid application image in the fw update partition, since it will find a new image it will check the validity of the image and will copy the image from the Firmware Update Partition to the execution partition. Also the image data in the Firmware update partition they will be marked as invalid in order in order to be ignored in subsequent resets. Regarding the headers and flags for the updating version should be the same as the fw produced from the mkimage tool, which is the suota_1_1_image_header_t structure appended on the start of the image.
A valid image has the flag of 0x02 which is set by the end of the SUOTA procedure and indicates a succesfull transfer of the image, this is what the bootloader checks in order to start the copying procedure from the update part to the execution part, after the original copy is complete the header of the image in the update part is set as invalid in order to to prevent new copies in subsequent reboots.
Thanks MT_dialog