Shared configuration in case of multiimage build

RE: Shared configuration in case of multiimage build

Charlie — Tue, 21 Feb 2023 13:34:50 GMT

Hi Eugene,

Sorry for the late reply, I did some experiments based on the multicore sample and here are my implementation and result.

1) Add a new common variable to nrf\samples\nrf5340\multicore\Kconfig and nrf\samples\nrf5340\multicore\cpunet\Kconfig(newly generated)

config TEST_VARIABLE
       int "A test variable"
       default 1

2) Add overlay-common.conf to nrf\samples\nrf5340\multicore, which set TEST VARIABLE to 2.

3) Add printk("Test valiable value: %d\n", CONFIG_TEST_VARIABLE); to nrf\samples\nrf5340\multicore\src\main.c.

3) build the project with commands:

west build --pristine --board nrf5340dk_nrf5340_cpuapp -- -DOVERLAY_CONFIG=overlay-common.conf -Dcpunet_OVERLAY_CONFIG=../overlay-common.conf

or use NCS VS code extension:

4) You would see both cores can print out Test variable value: 2 set by overlay-common.conf instead of default 1.

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Hello world from nrf5340dk_nrf5340_cpunet
Test valiable value: 2


Disconnected

Connected via Serial Port with settings COM57 115200 8n1 rtscts:off



Disconnected

Connected via Serial Port with settings COM59 115200 8n1 rtscts:off

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Hello world from nrf5340dk_nrf5340_cpuapp
Test valiable value: 2

Here is the modified multicore sample supporting common overlay configuration for both cores.

devzone.nordicsemi.com/.../0777.ncs220_5F00_multicore_5F00_commonconfig.zip

Best regards,

Charlie

RE: Shared configuration in case of multiimage build

Charlie — Tue, 21 Feb 2023 13:34:34 GMT

Hi Eugene,

Sorry for the late reply, I did some experiments based on the multicore sample and here are my implementation and result.

1) Add a new common variable to nrf\samples\nrf5340\multicore\Kconfig and nrf\samples\nrf5340\multicore\cpunet\Kconfig(newly generated)

config TEST_VARIABLE
       int "A test variable"
       default 1

2) Add overlay-common.conf to nrf\samples\nrf5340\multicore, which set TEST VARIABLE to 2.

3) Add printk("Test valiable value: %d\n", CONFIG_TEST_VARIABLE); to nrf\samples\nrf5340\multicore\src\main.c.

3) build the project with commands:

west build --pristine --board nrf5340dk_nrf5340_cpuapp -- -DOVERLAY_CONFIG=overlay-common.conf -Dcpunet_OVERLAY_CONFIG=../overlay-common.conf

or use NCS VS code extension:

4) You would see both cores can print out Test variable value: 2 set by overlay-common.conf instead of default 1.

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Hello world from nrf5340dk_nrf5340_cpunet
Test valiable value: 2


Disconnected

Connected via Serial Port with settings COM57 115200 8n1 rtscts:off



Disconnected

Connected via Serial Port with settings COM59 115200 8n1 rtscts:off

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Hello world from nrf5340dk_nrf5340_cpuapp
Test valiable value: 2

Here is the modified multicore sample supporting common overlay configuration for both cores.

devzone.nordicsemi.com/.../ncs220_5F00_multicore_5F00_commonconfig.zip

Best regards,

Charlie

RE: Shared configuration in case of multiimage build

Hiihtaja — Fri, 17 Feb 2023 13:51:09 GMT

Hi Charlie !

You mean if cpunet is included as child image, all new configs what is defined in Kconfig of multiimage build will be visible to both cores.

And prj.conf configs definitions can be taken from both cores values.

Is this so ?

Regards,

Eugene

RE: Shared configuration in case of multiimage build

Charlie — Thu, 09 Feb 2023 14:51:18 GMT

Hi Hiihtaja,

Now I understand you better.

You can refer to nRF5340: Multicore application — nRF Connect SDK 2.2.0 documentation (nordicsemi.com) sample.

In this sample, the firmware running on the application core and network core share some configurations, and even the same source codes.

Best regards,

Charlie

RE: Shared configuration in case of multiimage build

Hiihtaja — Tue, 07 Feb 2023 07:49:12 GMT

Hi Charlie !

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_multi_image.html

But all of those config lines need to be provisioned in prj.conf files and visible in menuconfig and only after that is possible to set those via overlay.

Now I'm able to have 4 independent menuconfigs;

west build -t menuconfig

west build -t mcuboot_menuconfig

west build -t cpunet_menuconfig

$ west build -t b0n_menuconfig
-- west build: running target b0n_menuconfig
ninja: error: unknown target 'b0n_menuconfig'

network bootloader dosn't work , may be I use wrong menuconfig line ?

and by this line :

-Dchildimageone_OVERLAY_CONFIG=extrafragment.conf[...]

I can add some common definitions for all chields if need.

But how to provisioned those config lines for app and network images ?

Include rsource "Kconfig.mydriver" to both KConfigs ?
In this cases they can be provisioned and by overlay have common definitions for both cores ?

Regards,
Eugene

RE: Shared configuration in case of multiimage build

Charlie — Mon, 06 Feb 2023 15:06:07 GMT

Hi Eugene,

You can create an overlay file for them, then load the same overlay file for different projects to make sure they use the same common configurations.

Best regards,

Charlie

RE: Shared configuration in case of multiimage build

Hiihtaja — Mon, 06 Feb 2023 12:51:42 GMT

Hi Charlie !

When I compile firmware for both cores, I have common settings what should be visible in both firmwares.

in Kconfig of app core there are populated.

Can I avoid dublication and set value once in prj.conf of core image and be sure if the same value and config flag will be visible for both cores during build process ?

Regards,

Eugene

RE: Shared configuration in case of multiimage build

Charlie — Mon, 06 Feb 2023 12:24:47 GMT

Hi Eugene,

[quote user=""]Is any way to define if this value can be visible to network core image ? Or how to share own config value between core and network images ?[/quote]

I am not sure if I understand this question correctly. Do you want to also use NET_L2_MY_VALUE =1 as a building time configuration for the network core? then just use it if you need it on your network core firmware.

application core and network core are basically running different firmware, they communicate through shared memory and IPC signalling.

Best regards,

Charlie