Multiimage build failed in NCS v2.3.0-rc1

RE: Multiimage build failed in NCS v2.3.0-rc1

Einarh — Mon, 06 Mar 2023 09:16:58 GMT

[quote user="Hiihtaja"]for some reason a lot of you samples consist of 2 cores and 2 boot loaders and able to generate updates for 2 cores as well ( and direct DFU recovery ).[/quote]

Well yes you do need a bootloader for both cores, this page gives a nice summary:

https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/nrf5340

[quote user="Hiihtaja"]May be I should reorganize my multi-image directory structure some how for be able to avoid this patch ?[/quote]

No I don't think so, if there was another way to do this then this patch wouldn't be necessary.

So as long as you're using NCS v2.3.0-rc1 with a customized netcore you'll have to use the patch.

It's worth noting that you won't need the patch if you use one of our premade netcore images.

-Einar

RE: Multiimage build failed in NCS v2.3.0-rc1

Hiihtaja — Fri, 03 Mar 2023 11:20:03 GMT

Hi Einar !

But for some reason a lot of you samples consist of 2 cores and 2 boot loaders and able to generate updates for 2 cores as well ( and direct DFU recovery ).

May be I should reorganize my multi-image directory structure some how for be able to avoid this patch ?

Regards,

Eugene

RE: Multiimage build failed in NCS v2.3.0-rc1

Einarh — Fri, 03 Mar 2023 10:25:49 GMT

It looks like only CONFIG_NCS_SAMPLE_EMPTY_NET_CORE_CHILD_IMAGE=n is required yes.

The patch you're linking to fixes a known issue related to using mcuboot in the multi-image sample. I'm not sure if this is directly related to your issue, but if you're basing your project on the multi-image sample and you're including mcuboot then you can avoid this known issue by adding the patch yes.

Best regards,

Einar

RE: Multiimage build failed in NCS v2.3.0-rc1

Hiihtaja — Fri, 03 Mar 2023 07:42:57 GMT

Hi Einar !

Thank you !

Do I undestand right and CONFIG_BOOT_IMAGE_ACCESS_HOOK_NRF5340=n no need ?

Only CONFIG_NCS_SAMPLE_EMPTY_NET_CORE_CHILD_IMAGE=n is required ?

What about this fix :https://github.com/hakonfam/fw-nrfconnect-zephyr/commit/970c4323fba917b88361dd57c47dee2f5f2a009a

Looks like it is still need for build DFU for netcore.

Regards,

Eugene

RE: Multiimage build failed in NCS v2.3.0-rc1

Einarh — Thu, 02 Mar 2023 14:07:07 GMT

It looks like your error is caused by NCS_SAMPLE_EMPTY_NET_CORE_CHILD_IMAGE being set to "y" (by default).

This option is new in v2.3.0, and doesn't have a KConfig prompt, but if you define a prompt in a KConfig file:

config NCS_SAMPLE_EMPTY_NET_CORE_CHILD_IMAGE
    bool "test"
    default n

and disable it in prj.conf:

CONFIG_NCS_SAMPLE_EMPTY_NET_CORE_CHILD_IMAGE=n

then it seems to compile successfully.

-Einar

RE: Multiimage build failed in NCS v2.3.0-rc1

Hiihtaja — Wed, 01 Mar 2023 08:07:19 GMT

Hi Einar !

Can it be another flag also ?

I have added this flag to mcuboot.conf and it is undefined in .config now.

But the build system still adds an empty network core to the project.

I also use direct recovery configuration for app and network cores and in 2.2 have used this patch

https://github.com/hakonfam/fw-nrfconnect-zephyr/commit/970c4323fba917b88361dd57c47dee2f5f2a009a

I haven't applied it yet and tried 2.3.0-rc1 as it is.

I have attached my multi-build sample for review. With 2.2 it works fine, DFU images are generated.

devzone.nordicsemi.com/.../multi_2D00_image.zip

for nrf5340

west build -p --board nrf5340dk_nrf5340_cpuapp

Regards,

Eugene

RE: Multiimage build failed in NCS v2.3.0-rc1

Einarh — Tue, 28 Feb 2023 13:19:02 GMT

Hello

Looking through the changelog since v2.2.0, it looks like this could be a likely source of your issue:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/releases/release-notes-changelog.html#id1

Maybe you'll have to set CONFIG_BOOT_IMAGE_ACCESS_HOOK_NRF5340=n in order to use your own multi-image build?

Best regards,

Einar