nRF Connect for VSCode not showing output files when using sysbuild

[Jared]

I read some previous posts that there was limited support for sysbuild for the VSCode extension. There are two things that I noticed:

1. When creating a build  configuration for the nRF9151 Feather, the 'Build system default' says it uses sysbuild but when I actually do a build it uses the old build system.

2. When I change the selection specifically to `Use sysbuild` the output files no longer show up. (I know where they are but others may not!)

[Priyanka]

Hi jared,

Could you tell me your VSCode and nRF Connect Vscode extension version?

Regards,

Priyanka

[Jared]

Extension v2024.11.75

VSCode:

Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 6.9.3-76060903-generic

[Amanda Hsieh]

Hi Jared, 

Priyanka is out of the office, so I picked up this case. 

I cannot reproduce the issue on Windows. Do you see the command with  "--sysbuild" when using the "use sysbuild" button? Try to delete the build folder and create a new build configration to see it can help or not. 

Regards,
Amanda H.

[Jared]

Hi Amanda

I'm on Linux. With the default option checked I get: 

 *  Executing task: nRF Connect: Generate config circuitdojo_feather_nrf9151/nrf9151/ns for nfed/samples/test 

Building test
west build --build-dir /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/nfed/samples/test/build/circuitdojo_feather_nrf9151 /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/nfed/samples/test --pristine --board circuitdojo_feather_nrf9151/nrf9151/ns -- -DNCS_TOOLCHAIN_VERSION=NONE

Versus explicitly checking sysbuild:

west build --build-dir /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/nfed/samples/test/build_2 /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/nfed/samples/test --pristine --board circuitdojo_feather_nrf9151/nrf9151/ns --sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE

The default is not sysbuild.

[Amanda Hsieh]

Jared said:

With the default option checked I get: 

Do you mean using "build system default"?

Jared said:

Versus explicitly checking sysbuild:

Do you mean using "use sysbuild"?

[Jared]

Correct. Building from scratch with the Default option does not use sysbuild. I assume the default is sysbuild since it has (sysbuild) at the top. (I think it also mentions it in the tool tip but I’m away from my machine right now)

[Amanda Hsieh]

I think it is because this nRF Connect SDK v2.7.0 Release Notes:
All samples and applications in the SDK are built with sysbuild by default. Applications that are outside the SDK are not built with sysbuild by default.

[Jared]

Seems to be the case. This was with using the default build mode:

Building at_client
west build --build-dir /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/external/nrf/samples/cellular/at_client/build /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/external/nrf/samples/cellular/at_client --pristine --board circuitdojo_feather_nrf9151/nrf9151/ns --sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE

Thanks Amanda