Hey, sorry for reply late.
Can you see that you’re updating your device using the bootloader over USB that it’s also updating to v2.0.2? It’s important to confirm this locally before you upload.
Yes, I try changing the hard-coded version to “v2.0.2” and using
printk() to verify it.
Also, how does your device know which image to pull? How you know if it’s pulling the correct one?
Hmm..that’s something I don’t fully understand, on the instruction of aws__fota sample, it says:
The sample then retrieves the firmware image over HTTP and replaces the current firmware with the downloaded firmware.
I guest it may have a way in bootloader to distinguish it?
Also, I tried in this way: instead of using v2 bootloader and
newtmgr, I use the debugger to program the device (
west flash --runner nrfjprog). Then I changed the hardcoded version, build with -p tag, upload the app_update.bin to S3 bucket, following the same process of FOTA, and in next reboot after fota download complete, it loaded with the new firmware from S3 (according to the hard-coded version using
printk()). I wonder if it is because of the v2 bootloader? Do you have any comment/suggestion on it?