NCS 2.0 custom child image + mcuboot build

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Wed, 14 Aug 2024 13:21:11 GMT

1) The patch works with the multi-image build.

2) Yes. I was trying to clarify if a fix got into an NCS release because back then, I was told that an official fix was going to be in the NCS 2.4 release.

RE: NCS 2.0 custom child image + mcuboot build

Sigurd Hellesvik — Wed, 14 Aug 2024 12:41:32 GMT

I think maybe I misunderstand your question, so let me try to clarify:

If you use the patch I linked, does this work?
Are you really trying to clarify if the fix got into NCS officially?

If so, the answer is: No the issue to custom child images with MCUboot with Multi-Image builds is not fixed in NCS, and will not be fixed. Either use the patch as a workaround, or upgrade to Sysbuild.

The reason to why this was not fixed is that we prioritized to implement Sysbuild instead.

RE: NCS 2.0 custom child image + mcuboot build

Sigurd Hellesvik — Tue, 13 Aug 2024 13:40:00 GMT

Ah, I will look for the other patch tomorrow then

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Tue, 13 Aug 2024 13:36:18 GMT

Hi Sigurd,

The patch that you pasted is currently what we are using.

RE: NCS 2.0 custom child image + mcuboot build

Sigurd Hellesvik — Tue, 13 Aug 2024 13:34:50 GMT

Aight.

I did some digging and I think I found a patch:

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

@@ -425,7 +425,9 @@ def parse_modules(zephyr_base, modules=None, extra_modules=None):
            sys.exit(f'{project}, given in ZEPHYR_EXTRA_MODULES, '
                     'is not a valid zephyr module')

    for module in all_modules_by_name.values():
    for module in {**{x: all_modules_by_name[x] for x in all_modules_by_name if
        x != 'mcuboot'}, **{x: all_modules_by_name[x] for x in
            all_modules_by_name if x == 'mcuboot'}}.values():
        if not module.depends:
            start_modules.append(module)
        else:

Can you give it a try and see if it works?

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Tue, 13 Aug 2024 13:26:16 GMT

Hi Sigurd,

Yes. We can upgrade to v2.7.0 but that won't happen for a couple of months. In the meantime, we'll just use our existing patch to build with v2.6.1.

Thanks,

Ronald

RE: NCS 2.0 custom child image + mcuboot build

Sigurd Hellesvik — Tue, 13 Aug 2024 11:03:22 GMT

Hi Ronald,

Would it be possible for you to upgrade to v2.7.0?

The reason I ask is that in v2.7.0, we are moving away from the old Multi-image build to Sysbuild.

With Sysbuild you should be able to add a custom image without any build order issues. Aka this will be the good fix for the issue.

See https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_sysbuild.html

Regards,
Sigurd Hellesvik

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Fri, 26 Jul 2024 18:32:16 GMT

Hi Torbjørn,

Did this fix get into v2.4.0?

I'm testing v2.6.1 and I still see the wrong build order. Can you send me that patch that was done? The link to the patch you gave me doesn't work anymore.

Thanks,

Ronald

RE: NCS 2.0 custom child image + mcuboot build

ovrebekk — Tue, 31 Jan 2023 08:30:06 GMT

You welcome Ronald, only wish I had better news to share ;)

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Mon, 30 Jan 2023 16:56:32 GMT

Hi Torbjørn,

Thanks for the update.

RE: NCS 2.0 custom child image + mcuboot build

ovrebekk — Mon, 30 Jan 2023 12:27:23 GMT

Hi Ronald

It seems this patch will not be included after all.

Instead another fix which makes it possible to configure the build order of the various images will be included.

Unfortunately it is doubtful it will make it for the v2.3.0 release since this is coming out shortly, most likely it will be included in the v2.4.0 release instead.

You can check out the new patch here.

Best regards
Torbjørn

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Fri, 27 Jan 2023 21:09:02 GMT

Hi Torbjørn,

When do you think this patch will get into an NCS release? I don't see this patch in the NCS 2.2.0 release.

RE: NCS 2.0 custom child image + mcuboot build

Wangshuhai — Wed, 31 Aug 2022 01:43:51 GMT

Hi Ronald,

Amazing ! It's fixed the error, it's working !

Thank you very much!

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Wed, 31 Aug 2022 00:37:09 GMT

Hi Wang,

I don't I think I got that error message before. One thing that I had to fix was the aci/CMakeLists.txt file. I had to change "DOMAIN cpunet" to "DOMAIN CPUNET".

Regards,

Ronald

RE: NCS 2.0 custom child image + mcuboot build

Wangshuhai — Tue, 30 Aug 2022 03:11:23 GMT

Hi Ronald,

I have try , i get like your same reason

error: 'PM_CPUNET_B0N_CONTAINER_SIZE' undeclared

but i define the zephyr/module.yml aci and overwrite the scripts/zephyr_module.py

How did your fixed it. Thanks!

Best regards

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Tue, 30 Aug 2022 02:30:22 GMT

Hi Wang,

I think you need to add the following config options in your mcuboot .conf file.

CONFIG_PCD=y

CONFIG_PCD_APP=y

Ronald

RE: NCS 2.0 custom child image + mcuboot build

Wangshuhai — Tue, 30 Aug 2022 01:32:51 GMT

Hi Ronald

Thank your quick reply. I add

CONFIG_SECURE_BOOT=y
CONFIG_NCS_MCUBOOT_IN_BUILD=y

in child image pj.conf it tell me undefine PCD_SRAM.

my project tree like this .

if i need write pm_static.yaml define the pcd address? thanks

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Tue, 30 Aug 2022 01:23:11 GMT

Hi Wang,

Make sure you have the following config options in your child image:

CONFIG_SECURE_BOOT=y
CONFIG_NCS_MCUBOOT_IN_BUILD=y

Regards,

Ronald

RE: NCS 2.0 custom child image + mcuboot build

Wangshuhai — Tue, 30 Aug 2022 01:15:17 GMT

Hi Ronald,

I'm working custom child image and mcuboot like your did. but i can't build child image b0n , can you give me some advice.

I can build appcore include the network core like

Best regards

Wang

RE: NCS 2.0 custom child image + mcuboot build

ovrebekk — Wed, 10 Aug 2022 05:20:50 GMT

I am currently out in travel, but I will check with the team next week. At best I think we are looking at a couple of months, but I will try to get you a more accurate estimate.

Best regards
Torbjørn

RE: NCS 2.0 custom child image + mcuboot build

variant — Fri, 05 Aug 2022 14:55:31 GMT

Which NCS version do you think this patch will be incorporated? We prefer not to patch the actual SDK.

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Fri, 05 Aug 2022 14:53:12 GMT

Hi Torbjørn,

Thanks for the patch. It fixed the problem. You can close this ticket.

Regards,

Ronald

RE: NCS 2.0 custom child image + mcuboot build

ovrebekk — Fri, 05 Aug 2022 11:59:12 GMT

Hi Ron

I got one of the developers to take a look at this, and he confirmed that the issue in your case is caused by the cmake build order not being specified, leading to situations where mcuboot might be built earlier than child images on which it depends.

At the moment the build system doesn't provide any way for the project to change this, and the only way to fix it is to make changes to the build scripts themselves.

The developer provided a patch that you can check out here.
This change should ensure that mcuboot will be built last, which should solve the dependency issue.

I will report this issue internally so we can fix this properly in a later release, but for the time being I hope the patch I shared above will allow you to proceed with your release.

Best regards
Torbjørn

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Thu, 04 Aug 2022 06:35:12 GMT

Hi Torbjørn,

I just realized that the modifications that I did to zephyr/module.yml will not work. The "aci" module doesn't depend on "mcuboot". It's actually "mcuboot" that depends on "aci".

RE: NCS 2.0 custom child image + mcuboot build

ronbo999 — Thu, 04 Aug 2022 02:19:32 GMT

Hi Torbjørn,

FYI. I tried updating the multicore zephyr/module.yml file to look like this

$ cat zephyr/module.yml
build:
cmake: aci
depends:
- mcuboot

but it didn't change the build order. MCUboot still got built first.