nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Kelso — Wed, 04 Sep 2024 23:43:20 GMT

At this point, since forcing the build configuration to use prj.conf instead of the cache, I haven't been able to reproduce the problem I was running into. On the other hand, I've run into 3 blue screen of deaths plugging in and removing the USB cable, as well as apparently permanently locking the access port on an nRF52DK during one of those BSODs. I think we can close this issue for now, but I need to open tickets for the other things that have cropped up.

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Vidar Berg — Mon, 02 Sep 2024 10:18:59 GMT

If you open the terminal in VS Code, you can compare the west build command when it works and when it fails. I'm wondering if the extension might be appending some arguments to the build command that override the default behavior when it fails.

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Kelso — Fri, 30 Aug 2024 18:19:59 GMT

I'll clarify... the behavior implies I do not fully understand where things are being cached because the places I'm looking appear to be a symptom, not a cause.

In vscode, if I've built and I try to adjust .conf files, I find extra cmake arguments populated under "edit build configuration" that I often need to clear out. Failing to do so causes the build to fail because the conf files have been intentionally removed.

If there is another place where the cache is editable, I'm not aware of it.

Saving the build config as a preset shows mismatches from expectation with both the failing and the updated workspace.

<wk failing> is missing child_image/b0/prj.conf under b0_CONF_FILE

<wk working> is missing boards/<example>.conf under CACHED_CONF_FILE

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Vidar Berg — Fri, 30 Aug 2024 12:01:24 GMT

That's strange. I don't recall seeing or hearing about this before. Do you notice any differences in the cached configuration when it fails versus when it works?

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Kelso — Fri, 30 Aug 2024 06:07:48 GMT

This appears to be a caching issue with vscode. I was able to get a workspace that was failing to pick prj.conf up to pick it up by changing the setting for Configuration to "prj.conf" instead of "Use build system default" when adding a build configuration.

This was after cloning into a new workspace and everything. The way vscode caches configuration it has detected is surprising. Clearing out the automatically generated cmake arguments isn't always sufficient, and deleting a configuration file can break a build. Seems like this is related to that.

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Kelso — Thu, 29 Aug 2024 22:13:34 GMT

Copying my board files into your project in the new workspace picks things up correctly... I'm able to build for my board.

It's gotta be something about the workspace itself. I'm going to see if reconstructing things from scratch again helps...

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Kelso — Thu, 29 Aug 2024 21:29:35 GMT

This is bizarre.... I made a new workspace to test. Quick answer is yours works and I have no idea why.

....

You don't have a west.yml... so I created the following one:

manifest:
remotes:
    - name: ncs
      url-base: https://github.com/nrfconnect

projects:
    - name: nrf
      import: true
      remote: ncs
      repo-path: sdk-nrf
      revision: v2.6.1

Setup a fresh workspace with west update --narrow -o=--depth=1 to keep things small

Build targeting nrf5340dk_nrf5340_cpuapp_ns worked and picked up things correctly.

Merged configuration '<wk3>/peripheral_lbs_w_dfu/child_image/b0/prj.conf'
Merged configuration '<wk3>/peripheral_lbs_w_dfu/child_image/b0/boards/nrf5340dk_nrf5340_cpuapp.conf'
Merged configuration '<wk3>/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Merged configuration '<wk3>/peripheral_lbs_w_dfu/build/b0/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to '<wk3>/peripheral_lbs_w_dfu/build/b0/zephyr/.config'

Trying with <wk3>/peripheral_lbs_w_dfu and custom_* works fine

Trying with <wk3>/example/peripheral_lbs_w_dfu2 and custom_* works fine.

So far I have no idea why there's a difference...

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Vidar Berg — Thu, 29 Aug 2024 06:25:17 GMT

I'm also using VS Code, and I was building the project with SDK version 2.6.1. And to be sure, I also tried changing the compatible property in *.dts to "nordic,custom-nrf5340-cpuapp"; but it didn't seem to make any difference.

From the build log for b0:

Merged configuration '<project>/child_image/b0/prj.conf'
Merged configuration '<project>/child_image/b0/boards/custom_nrf5340_cpuapp.conf'

Did you try building the sample I uploaded as well?

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Kelso — Thu, 29 Aug 2024 04:42:04 GMT

Cleaning the build folder, rebooting vscode, and combining the two do not address this.

I've been trying to rule out other causes. I'm currently using 2.6.1 build tools and my west workspace is dependent on 2.6.1. I'm attempting to build via vscode.

Are any of these different in your workspace?

I would be surprised, but the dts files you sent list compatibility with the nrf5340dk. Is it possible this line suppresses something?

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Vidar Berg — Wed, 28 Aug 2024 18:00:23 GMT

It should not be necessary, but could you please also try deleting the build folder when you do a clean build? I was not able to reproduce the issue here. As you say, the build log should show that the prj.conf got merged.

Here is the project I tested with:

devzone.nordicsemi.com/.../peripheral_5F00_lbs_5F00_w_5F00_dfu.zip

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Kelso — Wed, 28 Aug 2024 17:38:48 GMT

While that sounds like it should fix it, I don't see the new file being picked up on a clean build:

=== child image b0 - begin ===

...

Parsing <wk>/zephyr/Kconfig
Loaded configuration '<wk>/<prj>/boards/arm/<example>/<example>_cpuapp_defconfig'
Merged configuration '<wk>/<prj>/child_image/b0/boards/<example>_cpuapp.conf'
Merged configuration '<wk>/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Merged configuration '<wk>/<prj>/build_mb/b0/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to '<wk>/<prj>/build_mb/b0/zephyr/.config'

...

=== child image b0 - end ===

I should see a line in there that reads
Merged configuration '<wk>/<prj>/child_image/b0/prj.conf'

RE: nRF Connect SDK child image per-board configuration discards associated prj.conf in 2.6.1

Vidar Berg — Wed, 28 Aug 2024 13:39:21 GMT

Hello,

When the board specific configuration is added, you also need to include the prj.conf (copy of the nrf/samples/bootloader/prj.conf) for the child-image:

child_image/
├── b0
│   ├── boards
│   │   └── <example>_cpuapp.conf
│   └── prj.conf
├── mcuboot.conf
└── mcuboot.overlay

Best regards,

Vidar