BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Tue, 02 Jan 2024 13:22:14 GMT

Hi Sigurd,

Then I should keep the name as pm_static.yml just to make sure the memory allocated is static.

Thank you very much for the quick inputs that you have provided.

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Sigurd Hellesvik — Tue, 02 Jan 2024 12:17:33 GMT

[quote user="Aniket95"]One final question with your suggestion I have renamed the pm_static.yml to pm.yml and am really not sure if it matters. Do you still recommend to keep the name as pm.yml or change it to pm_static.yml?[/quote]

It is not recognized as pm.yml. pm.yml is only recognized and used in child images.

The Parititon Manager will only include static partitioning in your project if you name it specifically "pm_static.yml" (or include it via build options).

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Tue, 02 Jan 2024 12:00:12 GMT

Hi Sigurd,

Thank you so much for your valuable inputs. I was able to perform the DFU successfully.

One final question with your suggestion I have renamed the pm_static.yml to pm.yml and am really not sure if it matters. Do you still recommend to keep the name as pm.yml or change it to pm_static.yml?

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Sigurd Hellesvik — Fri, 29 Dec 2023 08:31:23 GMT

[quote user="Aniket95"]It seems like I need to increase the size for mcuboot I hope that could be done by pm_static.yaml, correct?[/quote]

It could.

However, you could also set CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000 in child_image/mcuboot.conf.

I recommend not using pm_static.yml for develpement. First use pm_static.yml when you are closer to deploying your project. The main use-case for static partitioning is to make sure that the partitioning does not change in-between DFUs, as changing partitioning between DFUs is not allowed.

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Thu, 28 Dec 2023 15:54:42 GMT

Here is my code developed for BL-653(nrf52833), if you get chance could you just check it and let me know what is going wrong

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Thu, 28 Dec 2023 15:43:17 GMT

Hi Sigurd,

I am trying to make my project setup according to the sample example that you have provided many thanks for that. I created a child_image folder and copied .overlay and .conf file in it. When I try to enable debug logs for bootloader the flash is overflowing. It seems like I need to increase the size for mcuboot I hope that could be done by pm_static.yaml, correct?

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Sigurd Hellesvik — Thu, 28 Dec 2023 14:21:08 GMT

[quote user="Aniket95"]Apparently I am not using any folder named as child image, I am just adding the .conf and .overlay files in build configuration. Is that a problem?[/quote]

That will not work.

Multi image build configurations will detect the folder child_image and apply configurations acordingly.

Since you do not have this, my guess to the error is that you have not configured external flash for the MCUboot child image, and therefore MCUboot can not access external flash when trying to swap the images. See the child_image folder in my external flash sample for how to configure this

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Thu, 28 Dec 2023 14:18:32 GMT

Hi Sigurd,

Apparently I am not using any folder named as child image, I am just adding the .conf and .overlay files in build configuration. Is that a problem?

...

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Sigurd Hellesvik — Thu, 28 Dec 2023 14:11:02 GMT

[quote user="Aniket95"]If there is any macro to enable boot logs please let me know.[/quote]

Indeed there is. You can enable logging in the MCUboot child image.

See here for an example of how. Remember to put it in child_image/mcuboot.conf, as is done in the sample.

[quote user="Aniket95"]Talkin about external flash yes the DFU works and the latest image gets loaded in slot-1 which is located in external flash. The only problem is am not able to copy the latest FW in slot-0 which is in internal flash or boot the FW from slot-1 itself.[/quote]

The way this works is a 2 step procedure:

1. New image is uploaded to slot-1 (also known as mcuboot_secondary)

2. Tag mcuboot_secondary as "test" or "confirm". On next boot, mcuboot will recognice this and swap slot-0 and slot-1.

Seems like 1 works. So we need to figure out if it is the Tag og Swap that fails. I hope to find this from the bootloader logs.

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Thu, 28 Dec 2023 14:00:30 GMT

Here are the logs I get when I try to boot the latest image from external flash, I have highlighted the logs from mcuboot. I am really not sure are these the correct one that you are referring to. If there is any macro to enable boot logs please let me know.

[quote userid="106736" url="~/f/nordic-q-a/106962/bl-653-nrf52833-failed-to-boot-the-fw-from-secondary-slot-of-mcuboot-which-is-located-in-external-flash/461946"]Can you try a couple of those and see if that works for you? Specifically the one with external flash and UART (does external flash DFU work?) and the one with BLE (does BLE DFU work?).[/quote]

The BLE DFU worked well with internal flash. And I think I have referred couple of examples from the link you have provided. The problem is most of the examples are configured for nrf52840 or nrf9160 while I am working with nrf52833. So I just copied the relevant settings from those and copied that in my project. Still I will take a look at the link.

Talkin about external flash yes the DFU works and the latest image gets loaded in slot-1 which is located in external flash. The only problem is am not able to copy the latest FW in slot-0 which is in internal flash or boot the FW from slot-1 itself.

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Sigurd Hellesvik — Thu, 28 Dec 2023 12:28:41 GMT

Do you get bootloader logs over RTT or UART from your application?
This sometimes gives hints to what went wrong.

I got some unofficial bootloader samples over at https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples. Can you try a couple of those and see if that works for you? Specifically the one with external flash and UART (does external flash DFU work?) and the one with BLE (does BLE DFU work?).

Then when you know that both features work standalone, try to add them one by one to your app. This way we hopefully can narrow down where the issue is at.

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Thu, 28 Dec 2023 11:45:08 GMT

Hi Sigurd,

I have tried with eliminating the CONFIG_FLASH_LOAD_OFFSET setting but still getting same results. The DFU package always gets loaded in slot-1(external memory partition) and I am still not able to boot the latest image.

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Thu, 28 Dec 2023 11:07:59 GMT

Hi Sigurd,

[quote userid="106736" url="~/f/nordic-q-a/106962/bl-653-nrf52833-failed-to-boot-the-fw-from-secondary-slot-of-mcuboot-which-is-located-in-external-flash/461927"]However, with MCUboot, the partition manager is used for both MCUboot and the application, making it so that they both know which addresses to use, and therefore you do not need to use CONFIG_FLASH_LOAD_OFFSET from the application.[/quote]

I will remove CONFIG_FLASH_LOAD_OFFSET from the setting and check if I get lucky. But do you think is there any other reason for this issue?

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Sigurd Hellesvik — Thu, 28 Dec 2023 10:18:42 GMT

[quote user="Aniket95"]- I just followed this from one of the example I guess. Do you think this is the culprit?[/quote]

It could be yes. It will offset the starting address of the application. It is usually used if the application does not know about the bootloader, for it to start on the correct address.

However, with MCUboot, the partition manager is used for both MCUboot and the application, making it so that they both know which addresses to use, and therefore you do not need to use CONFIG_FLASH_LOAD_OFFSET from the application.

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Aniket95 — Thu, 28 Dec 2023 09:56:28 GMT

Hi Sigurd,

Does it act different without the "MOVE_WITHOUT_SWAP" configuration?

- No I did not see any different behavior.

- I tried to compile with CONFIG_MCUBOOT_BOOTLOADER_MODE_DIRECT_XIP mode but it gives compilation errors partition manager complains about the mcuboot secondary image in external flash so I am trying with other options.

Why do you use CONFIG_FLASH_LOAD_OFFSET?

- I just followed this from one of the example I guess. Do you think this is the culprit?

RE: BL-653(nrf52833) failed to boot the FW from secondary slot of mcuboot which is located in external flash.

Sigurd Hellesvik — Thu, 28 Dec 2023 09:35:49 GMT

Does it act different without the "MOVE_WITHOUT_SWAP" configuration?

Why do you use CONFIG_FLASH_LOAD_OFFSET? This configuration is normally not needed.

Regards,
Sigurd Hellesvik