Overlay file not included in the build

[Akshay]

Hi, 

I'm working on a custom project and I was able to add and edit the overlay file according to my need till yesterday. Today when I tried to build the project I observed that my overlay file is not getting attached to the build. 

The same problem exist when I tried to create a fresh project base on the peripheral_lbs example and tried to create an overlay file.

See here, the devicetree doesn't show the overlay file I created. And yes I did the pristine build after creating the overlay.

[Vidar Berg]

Hi,

Can you please post a picture of te APPLICATIONs view that shows which context you have selected in addition to the build log printed to the terminal after a pristine build? 

Best regards,

Vidar

[Akshay]

Hi,

Like this?

My build configuration

While opening the visual editor for the overlay file

[Vidar Berg]

The extension indicates that it is included here:

 

But the overlay is empty. What is the problem you are observing, are changes in the overlay not applied to the generated zephyr.dts file?

[Akshay]

The changes are not getting applied to zephyr.dts and I can't open the visual editor for that overlay file.

[Vidar Berg]

It looks like this feature may have been broken for applications not using sysbuild in the last update of the extension (was released yesterday). Either way, sysbuild should be enabled by default in your west workspace when using SDK v2.7.0 and above (see Configuring sysbuild usage in west). With sysbuild enabled, you should be able to open the overlay in the DT UI editor as long as you've selected the 'build' folder in the 'APPLICATIONS' view first. This is not an issue with the SDK itself. In other words, if you manually edit the overlay file, the changes will be applied.

[Akshay]

My collegue has the same issue with 2.6.2 version of the ncs, that version doesn't use the sysbuild, right?!

And even with sysbuild enabled I still have this issue.

[Vidar Berg]

This is related to the version of the nRF connect extension in VS code, not the SDK. I new version of the extension got released yesterday. I'm currently discussing with the extension team to find out what the issue is. In the meantime, you may try downgrading to the previous version.

[Akshay]

Hi Vidar,

downgrading the extension version solved the issue. Thank you very much

[Vidar Berg]

Thank you for confirming. I'll inform the team about this regression.

[EdSwarthout]

I am also seeing the issue opening the "Compiled devicetree output" with the latest version (v2024.11.22).  I see this message:

  "/* Unable to resolve path devicetree:
/home/ed/packages/hw/nrf/code/l3_e1/Compiled%20devicetree%20output%20%28nrf5340dk_nrf5340_cpuapp_ns%29?%2Fhome%2Fed%2Fpackages%Fhw%2Fnrf%2Fcode%2Fl3_e1%2Fnrf5340dk_nrf5340_cpuapp_ns.overlay */"

The Actions tab does not show the Devicetree overlay file, but it is correctly included in the build.  The Actions tab and Visual Editor works fine with the older v2024.9.87.