Multiple applications

[MichaelXlivnenko]

Hi to every one,

i have some questions,
I need to be able to update the device to the new firmware, update to the old version and update to the default firmware. for this it is necessary to switch between applications stored in the flash memory. are there any ideas how this can be implemented??.
second question.
in the application update sample, there is a way to download the firmware via http, how i can use https with a bearer token?

Thanks 

[Didrik Rokhaug]

Hi,

 

I need to be able to update the device to the new firmware, update to the old version and update to the default firmware. for this it is necessary to switch between applications stored in the flash memory. are there any ideas how this can be implemented?

 I am not quite sure what you mean here. Do you need to have three different application images on the device that you can change between?

Or are you just asking how you can do a firmware update of the device?

 

in the application update sample, there is a way to download the firmware via http, how i can use https with a bearer token?

 The application update sample uses the download_client library to download the new firmware image.

At the moment, the requests are hard-coded, but it should not be hard for your to add another field to the request along with some way to provide the token to the library.

Best regards,

Didrik

[MichaelXlivnenko]

Hi, 
thank you for fast answer.

in first question, i mean that i want to have three different application images on the device and want to change between them.

As for requests, I already found their hard-code implementation

Thanks!

[Didrik Rokhaug]

MichaelXlivnenko said:

i mean that i want to have three different application images on the device and want to change between them.

 Why do you want that?

What is the problem you are trying to solve here?

[MichaelXlivnenko]

My problem is next, I need to implement a model of the application when it is possible to update with OTA, and also reset to factory firmware, which should be stored on the controller

[Didrik Rokhaug]

Hi, and sorry for the late reply.

I don't know of any way to do that in NCS.

With MCUBoot, you can require the new image to verify that it works, otherwise it will roll back to the previous version at the next boot. Would that satisfy your requirement?

MCUBoot also has a serial recovery mode where MCUBoot can receive a new image over a serial interface, so even if the application don't work properly, it should be possible to fix the device.

If that is not enough, I imagine it would be possible to do what you want, though it will require changes to MCUBoot to make it work. You will also have to make sure that the Partition Manager reserves a partition for your default image, and that it is linked correctly.

[MichaelXlivnenko]

Thanks for your answer!

Where can I find more detailed information about MCUBoot settings for nrf9160?

[Didrik Rokhaug]

You can find the MCUBoot documentation here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.7.0/mcuboot/wrapper.html

Information on how to configure child images, such as MCUBoot, can be found here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.7.0/nrf/ug_multi_image.html#image-specific-variables

Kconfig options for MCUBoot can be found here: https://github.com/nrfconnect/sdk-mcuboot/blob/master/boot/zephyr/Kconfig