• State Verified Answer
  • Locked Locked
  • Replies 10 replies
  • Subscribers 76 subscribers
  • Views 838 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 336957
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

  • +1

    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

  • 0 in reply to Marte Myrvold

    Okay, I understand. Thank you very much

  • 0 in reply to Marte Myrvold

    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？

  • 0 in reply to llly

    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

  • 0 in reply to Marte Myrvold

    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

Related
Terms of service