FOTA Sample

Nwre

Hi! I am using the http application update sample. I have seen several threads on this issue on the forum but no solution. The update is downloaded but not flashed on reset. I have added one of my favorite cursewords to the print out at the start of the program to make sure it is indeed the old program that is being loaded.

Anyone have any idea how to do this? I have been stuck with this for far too long. When looking at the partition layout for the feather it differs from the nrf9160DK, maybe that is the problem? I am a novice in all of this so excuse me if my thoughts are completely wrong.

Regards
Nwre

jaredwolff

Hey @Nwre

One thing that I’ve seen is that they’ve modified their scripts for the partition layout over the different versions of the SDK. So as I’ve been upgrading SDKs older bootloaders stopped working.

One thing you can try is if you can load the .bin file over USB first to see if it takes. If it doesn’t it’s likely that conflict. If it does then there’s something else afoot here.

Nwre

Hi Jared! Thank you for an incredible device!

To load over usb you would need a special connector no? I can flash over usb when I build projects so should I replace the app_update.bin in a active project with the one that the http app update sample is using, would that work? Does the sample work for you?

Regards and thank you for your patience with me 🙂

jaredwolff

Nwre Hi Jared! Thank you for an incredible device!

You’re welcome. 🙂

Nwre To load over usb you would need a special connector no?

All you need is a USB C cable to connect to your computer. Here’s more info on that: https://docs.circuitdojo.com/nrf9160-programming-and-debugging.html#bootloader-use

Nwre I replace the app_update.bin in a active project with the one that the http app update sample is using, would that work? Does the sample work for you?

It can be any app_update.bin file as long as it’s built for the nRF9160 Feather. I also have pre-built binaries on the Github Repo when I push changes to the samples repository. You can certainly try those as well.

Build page:

https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers/actions/runs/5909295811

Download link:

https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers/suites/15252732310/artifacts/871482004

Nwre

I see what you mean. I have tried this using my own versions of the .bin for the feather. It works via usb but not when downloading via aws. Not the sample nor my own code (which works on the dk) with a tested feather .bin. It downloads but upon reset, the old program is run.

jaredwolff

Hmm I know if you don’t call boot_write_img_confirmed somewhere it will fall back to the previous code. You should have a line in the application you’ve loaded in the main function that looks like:

err = boot_write_img_confirmed();
if (err) {
	LOG_ERR("Failed to confirm image: %d", err);
}

Nwre

jaredwolff I do and it is confirmed. I thought maybe it was looking at the wrong memory address when loading the new .bin since this is the only difference I have been able to find between the feather and the DK pertaining to this situation

AchimKraus

Do you call boot_request_upgrade? That offers you two options BOOT_UPGRADE_TEST and BOOT_UPGRADE_PERMANENT? And you need the “build/zephyr/app_update.bin”, no hex or something else.

Nwre

AchimKraus I am looking through the sample but I cant find that specific part. I am using the http application update sample. I have my own SPI config overlay but that shouldnt affect the sample? I tried following a thread on this forum on creating your own signing key but that didnt seem to work either.

Edit: This thread:

https://community.circuitdojo.com/d/109-aws-fota-download-successful-but-do-not-load-with-new-binary-file/33

AchimKraus

the sample

Do you have an link for me?

FOTA is in many cases split into phases.
The first is the download. Usually that’s done in a few minutes but sometimes it may take longer.
The second one is to apply the download. In order to tell the McuBoot to apply the download from the 2 slot as update to slot 1, that boot_request_upgrade and a reboot is needed.

Not sure, what you sample includes/shows, maybe only the download.

boot_request_upgrade