NRF Connect SDK Builds/Pristine Builds Ignore Child Image Configuration With Custom Boards

RE: NRF Connect SDK Builds/Pristine Builds Ignore Child Image Configuration With Custom Boards

dwalks — Tue, 23 Apr 2024 15:14:36 GMT

I gave up with the child image and set the conf file via cmake flags instead. It works as expected.

RE: NRF Connect SDK Builds/Pristine Builds Ignore Child Image Configuration With Custom Boards

dwalks — Tue, 23 Apr 2024 13:27:51 GMT

To clarify, this applies for custom and non custom boards

RE: NRF Connect SDK Builds/Pristine Builds Ignore Child Image Configuration With Custom Boards

dwalks — Tue, 23 Apr 2024 13:26:43 GMT

I am also finding this to be the case.

There appear to be 2 problems with the build process.

Immediately after configure, not all flags are passed to west. For mcuboot, -Dmcuboot_OVERLAY_CONFIG is missing.

If you then run a pristine build, then project will now build correctly, however the west arguments have change subtly again.

Now, instead of supplying -DCONF_FILE, west is now given -DCACHED_CONF_FILE. This seems to be critical to getting the build to work, as a subsequent build using -DCONF_FILE does not work.

You will only notice this failing for this particular example (mcuboot) if you require the build to be minimised. When build process doesn't minimise mcuboot, but your mcuboot partition has been reduced, the image won't fit and the build will fail.

After configure:

west build --build-dir <PATH>/app/build <PATH>/app 
--pristine 
--board xxx@y.y.y 
--no-sysbuild -- 
-DNCS_TOOLCHAIN_VERSION=NONE 
-DCONF_FILE=<PATH>/app/prj_release.conf 
-DEXTRA_CONF_FILE=frag_mcuboot.conf

Pristine build:

west build --build-dir <PATH>/app/build <PATH>/app 
--pristine 
--board xxx@y.y.y 
--no-sysbuild -- 
-DNCS_TOOLCHAIN_VERSION=NONE 
-Dmcuboot_OVERLAY_CONFIG=<WORKSPACE>/nrf/subsys/partition_manager/partition_manager_enabled.conf 
-DCACHED_CONF_FILE=<PATH>/app/prj_release.conf 
-DEXTRA_CONF_FILE=<PATH>/app/frag_mcuboot.conf

RE: NRF Connect SDK Builds/Pristine Builds Ignore Child Image Configuration With Custom Boards

SJahnke — Mon, 22 Jan 2024 07:17:42 GMT

Hi Didrik Rokhaug,

is there already a solution in the pipe for the VS Code extension? I noticed, that this is still a problem in my setup. I used a custom nRF5340 development board in combination with the nRF Connect SDK version 2.5.0 and the radio_test sample. I tried to change the configuration (overlay file) in the child image, but when doing a new build, it ignores my overlay file for the build.

RE: NRF Connect SDK Builds/Pristine Builds Ignore Child Image Configuration With Custom Boards

bryan_aerel — Fri, 12 Aug 2022 17:17:56 GMT

Thank you for the quick reply!

I just tested it and can confirm it is also not working on non-custom boards. That's strange as I am almost certain it was working with them earlier. However, I did reinstall the SDK trying to get it work so maybe that's a contributing factor.

Thanks for your workaround, I had not thought about that. I'll have to figure out exactly what command line options and whatnot to use for my real application. Simply comparing the commands that the extension runs for the throughput example, on the second build it's identical except for 2 additional options. I don't understand why adding those 2 options causes the child image configuration to be excluded, or why the original build even works without them, but I'm sure you guys already have that figured out 🙂

 -DCONF_FILE:STRING="c:/Users/rapidrs/Desktop/53ble/throughput/prj_nrf5340dk_nrf5340_cpuapp.conf" -DDTC_OVERLAY_FILE:STRING="c:/Users/rapidrs/Desktop/53ble/throughput/dts.overlay"

RE: NRF Connect SDK Builds/Pristine Builds Ignore Child Image Configuration With Custom Boards

Didrik Rokhaug — Fri, 12 Aug 2022 14:19:12 GMT

Hi,

Thanks for reporting this. I have forwarded it to our developers.

Can you confirm that it only happens with custom boards for you?

Because when I tried, I was able to reproduce it without creating a custom board.

However, if I use West directly from the terminal, I am not able to reproduce it. So that might be a solution until we can fix it properly.

Best regards,

Didrik