nRF Studio (VC Code) don´t work with Matter Examples

[Hermannd3]

I'm using nRF Studio Visual Studio Code. (SDK and Toolchain v.2.7.0) with the nRF7002 Development Kit.
The Blinky example have worked fine and also the other things as shown in the Video tutorials.

However, I am unable to generate a Matter example (LightBulb) on this basis, both under Windows and MacOS.
The same errors always occur: Kconfig warnings and Cmake errors. What's going wrong here? I ask for help.

[Simonr]

Hi Klaus

So one thing we can try is to give you the .hex file directly so that you can flash that onto your board directly instead of having to build the sample on your end. It's very strange to me that this doesn't work out of the box to you though.

Anyways, here are the two .hex files for the Network and Application cores. The easiest way to program these onto your board will be to download the nRF Connect for Desktop Programmer application for Windows, select your nRF7002 DK there, and add these with the "Add file" button, then pressing Erase & write. I did that on my end to confirm it acts as expected. Please note that this is an as is light_bulb sample with no changes built in NCS 2.7.0.

6646.merged_CPUNET.hex5241.merged.hex

Best regards,

Simon

[Hermannd3]

Hi Simon,

with the 'Use sysbuild' option it finally worked after weeks of frustration!

Various errors (under Problems) appeared again during the build process, but they all disappeared after the flash process, which is incomprehensible to me. Is that normal? Anyway, it's confusing.

The board was then integrated into my Matter environment and works! The dimmer function does not.

However, I don't understand the differences in the three build options, it would be nice if there was a more detailed explanation.

Thank you very much so far.

Best Regards,

Klaus

[Simonr]

Yes, some warnings are unfortunately normal, but we're working to improve the user experience all the time. And if you have some constructive feedback for us I'm happy to forward that to the correct people.

As of NCS 2.7.0, sysbuild should also be the same as the "default build", but in your case something must be wrong with the default setting. The "no sysbuild" option is the option we've used in previous versions of the SDK, but are now moving to sysbuild. Sysbuild is a higher-level build system that can be used to combine multiple other build systems together. It is a higher-level layer that combines one or more Zephyr build systems and optional additional build systems into a hierarchical build system. It is mainly needed since we've launched the nRF54L15 now that has more cores and would need a more robust build system. The no sysbuild option uses west as is for building the project.

Best regards,

Simon