Migrating child/parent to sysbuild - SECURE BOOT

RE: Migrating child/parent to sysbuild - SECURE BOOT

Hieu — Tue, 13 Aug 2024 21:18:18 GMT

[quote user="Udi Vahaba"]

Sorry that it took me while to respond.

Could you please check if CONFIG_CONSOLE is enabled in any of your images?

Actually there is a weird thing, in my prj.conf it is set to CONFIG_CONSOLE=n but in the .config file (build/b0/zephyr/.config) it is set to CONFIG_CONSOLE=y.

any idea why?

[/quote]

Your prj.conf configures your application. b0 is a different image, so the configuration in prj.conf isn't applied to it. See this documentation page: https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/zephyr/build/sysbuild/index.html.

[quote user=""]2. Do i use the correct folder structure and relevant files on the sysbuild?[/quote]

Regarding your folder structure, I don't think sysbuid/mcuboot/mcuboot.conf has any effect.
The idea of having it is also rather redundant, as you are reconfiguring the entire project Kconfig file with sysbuild/mcuboot/prj.conf.

What you want to do is merge your previous child_image/mcuboot.conf content into sysbuid/mcuboot/prj.conf, or do not have the sysbuild/mcuboot directory, and only use sysbuild/mcuboot.conf.

This is also discussed in the documentation page linked above.

Other than that, the project structure looks OK.

As for your configuration file content, unfortunately, I cannot provide any guarantee regarding the config file contents.
I can see that you have made modifications to MCUboot configuration, and all I can say is that the configurations that are changed are meant to be configurable.
Whether that achieve what you want or not is, however, entirely up to your own project requirements and verifying them require proper testing.

The same can be said for <application>/prj.conf. It depends largely on your project requirements and requires testing.
I have some doubt about whether you need to set CONFIG_BUILD_WITH_TFM on your own when using sysbuild. I have raised this internally and follow-up when I get a reply.
The MCUmgr configurations for the image management group, which is relevant to DFU, look OK.

Other than that, no comment about the other changes compared to your pre-sysbuild prj.conf.

RE: Migrating child/parent to sysbuild - SECURE BOOT

Udi Vahaba — Mon, 12 Aug 2024 06:19:20 GMT

Sorry that it took me while to respond.

Could you please check if CONFIG_CONSOLE is enabled in any of your images?

Actually there is a weird thing, in my prj.conf it is set to CONFIG_CONSOLE=n but in the .config file (build/b0/zephyr/.config) it is set to CONFIG_CONSOLE=y.

any idea why?

RE: Migrating child/parent to sysbuild - SECURE BOOT

Hieu — Tue, 06 Aug 2024 15:55:54 GMT

Hi Udi,

[quote user=""]1. Why do i have to set the property zephyr,chosen with sysbuild where in child/parent i could build without it(exactly same bsp)?[/quote]

Could you please check if CONFIG_CONSOLE is enabled in any of your images?

[quote user=""]Please note that in my BSP there is no use for console with uart. uart0 and uart1 are used with external modules and i can't let the console throw data into the uart lines (will it happen if zepyr,console = &uart0 is selected?).[/quote]

The console is used for a few things. printk() will output to the console unless configured otherwise, for example.

If you require that nothing is output to the console, then you might want to pay attention to the boot banner.

But of course, the safest method is to just disable console altogether.

[quote user=""]2. Do i use the correct folder structure and relevant files on the sysbuild?[/quote]

I will come back later for this. Unfortunately, I am new to sysbuild myself.

Regards,

Hieu

RE: Migrating child/parent to sysbuild - SECURE BOOT

Hieu — Mon, 05 Aug 2024 18:40:31 GMT

Hi Udi,

Let me investigate this and follow up with you in a few days.

Regards,

Hieu