The conf file of ncs2.8.0 is always unrecognized

[llly]

This is the normal kconfig menu.

But it often happens that the following picture does not recognize anything in kconfig

and there is no devicetree option in the action menu, and the content displayed in the nrf kconfig GUI is also incomplete,even the nrf kconfig GUI cannot be opened like this

The solution I have found so far is to manually open the prj.conf file once. After opening it, the menu bar will display the animation being loaded, and all the above problems will be resolved. However, after modifying the code or compiling it several times, it will appear again. I need to manually open the prj.conf file again.

I only encountered these issues in the ncs2.8.0 version, and everything worked fine when using 2.6.1 before

[Marte Myrvold]

Hi,

This happens when you have the sysbuild build directory selected. If you instead selected the build directory of the application image, which is located inside the sysbuild directory, the Kconfig files should show up:

When the sysbuild build directory is selected, only the sysbuild Kconfig files will show up.

Best regards,
Marte

[llly]

I have found that there is still an issue that has not been resolved. When opening the nrf kconfig GUI, it will prompt 'unable to find kconfig information'，like the third screenshot, Can you help me take another look at this issue？

[Marte Myrvold]

Hi,

I am not able to reproduce the issue. Do you see it regardless of the sample and/or board, or only with specific samples and/or boards?

Which versions are your nRF Connect for VS Code and nRF Konfig extensions in VS Code?

Best regards,
Marte

[llly]

The version I am using is this

This problem is likely to occur in many samples, but not every time. I can't figure out the pattern of its occurrence now. What I can confirm is that I encountered this issue on the 9160 SLM sample. Yesterday, when I was using SLM for testing, I tried to open the kconfig GUI but couldn't open it

It's not really a big problem, but occasionally not being able to open it can be quite uncomfortable

If possible, could you please help investigate what caused it, thanks

[Marte Myrvold]

Hi,

I was able to reproduce the issue on my side. It seems to happen with the sysbuild configuration in projects that include more than one additional sysbuild image, for example, both MCUboot and b0 instead of only MCUboot.
I have reported it internally and will update you when I hear back from the VS Code team.

Best regards,
Marte

[llly]

ok thank you

[Marte Myrvold]

Hi,

The developers have not yet found the root cause of the issue, but I wanted to update you on what they have found so far.

It seems like the build system thinks the build is stale, which is causing the nRF Kconfig GUI to not work. However, doing an incremental build by clicking the "Build" action while the sysbuild directory is selected will fix this issue and make the nRF Kconfig GUI work.

Please note that doing a pristine build, that is, clicking on the arrow next to the Build action, will cause the issue to recur, and you will have to do a new build using the Build action to fix it again.

This issue does not seem to happen on the main branch, only v2.8.0.

Best regards,
Marte

[llly]

Okay, thank you very much. At least it's better than having no solution. Isn't 2.8.0 a stable version? I currently need to use 54l15, which is why I upgraded from 2.6.1 to 2.8.0

[Marte Myrvold]

Hi,

The official releases have been tested and are considered stable, but sometimes bugs appear in them as well.

There is currently a release candidate for v2.9.0, tagged as v2.9.0-rc1, so you can also use that if you do not want to use the workaround where you have to build a second time.

Best regards,
Marte