Cannot build new image for FOTA through MCUboot

RE: Cannot build new image for FOTA through MCUboot

Amanda Hsieh — Mon, 11 Dec 2023 22:05:52 GMT

Hi,

Please create a new support case for the new issue which is away from the original scope.

-Amanda H.

RE: Cannot build new image for FOTA through MCUboot

jswcomkr — Mon, 11 Dec 2023 05:05:37 GMT

Thank you for reply.

I checked again and applied it to my project.

So, I finally got the app_update.hex and bin file.

I want to write it to memory slot 1 by manually, because LTE modem cannot send any SMP messages.

So, my plan is as follow.

1. LTE modem download new binary or hex file(maybe app_update.bin or app_update.hex ??) from our server, and it will be stored in LTE Modem's internal flash.

2. Read downloaded file LTE modem through UART one by one byte using AT Command and Write it into the slot 1 flash(Maybe from 0x45000)

3. After write all data, reboot using NVIC_SystemReset(); function.

4. MCUboot will check new firmware in slot1 automatically.

5. If it is valid, MCUboot will copy new firmware from slot1 to slot 0.

6. After the copy is complete, device will reboot and start with new firmware.

Is it possible?

RE: Cannot build new image for FOTA through MCUboot

Amanda Hsieh — Thu, 07 Dec 2023 16:59:35 GMT

Hi,

[quote user="jswcomkr"]I modified prj.conf in ncs/v2.5.0/nrf/samples/bootloader, but I didn't set this path by myself.[/quote]

I would not suggest you modify prj.conf of ncs/v2.5.0/nrf/samples/bootloader directly. You can add the NSIB as a child image to your application by enabling CONFIG_SECURE_BOOT=y. Here is an command example.

[quote user="jswcomkr"]1. How can I modify s1 image configuration file path?[/quote]

When adding the NSIB as a child image by enabling CONFIG_SECURE_BOOT=y, you can create child_image\create b0.conf under the application to overwrite the configuration.

[quote user="jswcomkr"]2. What is the B0, S0, S1 Image(Its meaning)[/quote]

B0 is nRF Secure Immutable Bootloader (NSIB). S0 and S1 are updateable MCUboot. See https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/nrf/samples/bootloader/README.html#pre-signed-variants

[quote user="jswcomkr"]3. Which image can be used as upgrade image? I got lots of hex files.(Plz see below image)[/quote]

We have https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/nrf/config_and_build/config_and_build_system.html#output-build-files which describes signed_by_mcuboot_and_b0_s0_image_update, which is the image you will want to use. Also, see this post.

[quote user="jswcomkr"]4. Finally, How can I set the start / end address of each image? I want to use MCUboot-Primary Slot-Secondary Slot structrue.[/quote]

It would be handled by partition manager which would be enabled automatically with muti-build.

[quote user="jswcomkr"]5. I want to design my MCU's partition as follow:(pm_static.yml in project folder)[/quote]

Remove the pm_static.yml. Let the partition manager handle it for you.

[quote user="jswcomkr"]My intend is that s0 is primary slot, s1 is secondary slot for new firmware, and mcuboot is for bootloader.[/quote]

S0 and S1 are for updating the mcuboot instead of app. See https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/nrf/samples/bootloader/README.html#pre-signed-variants

[quote user="jswcomkr"]As you know, nRF52832 has 512KB internal flashes, so I divided it in 3 pieces. but it is not work.[/quote]

Do you want to update mcuboot or just the app?

If you just want to update the app image, you can just enable the DFU as my colleague suggested in this post. Then, the memory layout would look like this

-Amanda H.

RE: Cannot build new image for FOTA through MCUboot

jswcomkr — Thu, 07 Dec 2023 07:24:56 GMT

Thank you for reply.

I managed to build s1 image for upgrade.

I modified prj.conf in ncs/v2.5.0/nrf/samples/bootloader, but I didn't set this path by myself.

So, my question is as follow.

1. How can I modify s1 image configuration file path?

2. What is the B0, S0, S1 Image(Its meaning)

3. Which image can be used as upgrade image? I got lots of hex files.(Plz see below image)

4. Finally, How can I set the start / end address of each image? I want to use MCUboot-Primary Slot-Secondary Slot structrue.

5. I want to design my MCU's partition as follow:(pm_static.yml in project folder)

mcuboot:
  address: 0x00
  end_address: 0x8000
  size: 0x8000
  region: flash_primary
s0:
  address: 0x8000
  end_address: 0x44000
  size: 0x3C000
  region: flash_primary
s1:
  address: 0x44000
  end_address: 0x80000
  size: 0x3C000
  region: flash_primary
sram_primary:
  address: 0x20000000
  end_address: 0x20010000
  region: sram_primary
  size: 0x10000

But it makes error. What is the probielm?

My intend is that s0 is primary slot, s1 is secondary slot for new firmware, and mcuboot is for bootloader. As you know, nRF52832 has 512KB internal flashes, so I divided it in 3 pieces. but it is not work.

RE: Cannot build new image for FOTA through MCUboot

Amanda Hsieh — Wed, 06 Dec 2023 17:28:37 GMT

Could you create child_image\create b0.conf under the application to include "CONFIG_SECURE_BOOT_DEBUG=n" to disable debugging NSIB function?

If you still have the issue, please upload the project and board file.

RE: Cannot build new image for FOTA through MCUboot

jswcomkr — Wed, 06 Dec 2023 16:27:46 GMT

Thank you for reply.

I checked that postings, but not work for me.

I still got same message

warning: UART_NRFX (defined at drivers/serial/Kconfig.nrfx:6) has direct dependencies (DT_HAS_NORDIC_NRF_UART_ENABLED || DT_HAS_NORDIC_NRF_UARTE_ENABLED) && SERIAL with value n, but is currently being y-selected by the following symbols:
 - SECURE_BOOT_DEBUG_UART (defined at C:/ncs/v2.5.0/nrf\subsys\bootloader/Kconfig:222), with value y, direct dependencies <choice SECURE_BOOT_DEBUG_BACKEND> (value: y), and select condition <choice SECURE_BOOT_DEBUG_BACKEND> (value: y)

warning: UART_CONSOLE (defined at drivers/console/Kconfig:43) has direct dependencies SERIAL && SERIAL_HAS_DRIVER && CONSOLE with value n, but is currently being y-selected by the following symbols:
 - SECURE_BOOT_DEBUG_UART (defined at C:/ncs/v2.5.0/nrf\subsys\bootloader/Kconfig:222), with value y, direct dependencies <choice SECURE_BOOT_DEBUG_BACKEND> (value: y), and select condition <choice SECURE_BOOT_DEBUG_BACKEND> (value: y)

error: Aborting due to Kconfig warnings

How can do?

RE: Cannot build new image for FOTA through MCUboot

Amanda Hsieh — Wed, 06 Dec 2023 14:17:42 GMT

Hi,

Check out this post and this post.

Regards,
Amanda H.