Problem with Kconfig configuration

RE: Problem with Kconfig configuration

Hieu — Wed, 30 Oct 2024 10:29:32 GMT

If you are building multi-image, you need to look closely at which build had the error you observed. Perhaps some configurations are not compatible with mcuboot.

If you add the configs to _defconfig, it will be added to both mcuboot, application, and any other images. You will also want to check if this result makes sense.

If you want to add the default config to _defconfig file, but only for the application, you can add a Kconfig file to conditionally override the default value based on which board is being built. Refer:
https://github.com/nrfconnect/sdk-zephyr/blob/v3.7.99-ncs1-rc1/boards/nordic/thingy53/Kconfig#L12-L27
https://github.com/nrfconnect/sdk-zephyr/blob/v3.7.99-ncs1-rc1/boards/nordic/thingy53/Kconfig.thingy53#L6-L9

RE: Problem with Kconfig configuration

Bartosz22 — Tue, 29 Oct 2024 12:57:16 GMT

I'm using mcuboot, I have child and parent image which I see is deprecated and will be removed in NCS 2.9 but I don't is it a case. The board _defconfig file is included properly.

RE: Problem with Kconfig configuration

Hieu — Tue, 29 Oct 2024 12:07:58 GMT

Are you building just one application for the nRF52840, or do you also have a bootloader or some other multi-image setup?

Most of the symptoms you described suggest maybe your _defconfig file wasn't picked up in the build. Have you checked the log to see if it's included? You can run a --pristine --cmake-only build to check.

Hieu