• State Verified Answer
  • Replies 4 replies
  • Subscribers 74 subscribers
  • Views 2166 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 305167
Options

KConfig Vscode Extension Warning/Error For Zephyr/Matter

vindicator

I've built and flashed MCUBOOT(Zephyr) without any issues.

Now that I've moved onto Matter/ConnectedHomeIp(Zephyr), I've noticed that I'm getting squiggles...

CONFIG_CHIP=y
##^Red error squiggle: "Unknown Symbol CONFIG_CHIP"
CONFIG_POSIX_API=y
##^Fine
CONFIG_STD_CPP17=y
##^Yellow warning squiggle: "CONFIG_STD_CPP17 was assigned the value y, but got the value n. Missing dependencies:
<choice>"
I don't know if the "CHIP" one was a red-herring though because of deprecation warnings by zephyr: github.com/.../25808
Parents
  • 0

    Hi, 

    Which NCS version are you using?

    Is it possible ty with the latest version, v2.3.0?

    Regards,
    Amanda H.

  • 0 in reply to Amanda Hsieh

    I'm not using NCS. I'm just using bits and pieces of things like manually working with zephyr/mcuboot/matter. All the modules I'm cloning myself from mainline and adding necessary bits like the zephyr dir to make it work (and so far it has with me building and flashing a working mcuboot and zephyr app in Slot0).  

    Same with extensions, I'm selectively using your Kconfig (v2022.11.50) and DeviceTree extensions which I see is still all the latest versions.

  • 0 in reply to Amanda Hsieh

    ? How is that meant to correct the incorrect squiggles?  

    ".config" in the build-dir is even showing "CONFIG_CHIP".  

    What is "Missing dependencies: <choice>"? 

    It wasn't an issue with using the same kind of environment when building mcuboot(zephyr-based) or a zephyr app.  

    I've already got like 15 environment variables in my CMakePresets.json, some of which include ZEPHYR_BASE, ZEPHYR_MODULES, ZEPHYR_TOOLCHAIN_VARIANT, CROSS_COMPILE, CHIP_ROOT, PW_ROOT.  

    I think what I'm looking for here is why, even though the CONFIG_ entries exist, your extension seems to not want to acknowledge them. Most are acknowledged. Like I said, no issues with mcuboot.  

    Like "CONFIG_BOOT_SIGNATURE_KEY_FILE" has NO squiggles, and it's from the mcuboot module, just like connectedhomeip is a module.  

    So again, why no issues with mcuboot "CONFIG_"s, but apparently so for matter?  

    I'd think if it's getting it's values, checking for validity from zephyr and the modules' kconfigs (eg "connectedhomeip/config/zephyr/chip-module"), it shouldn't be an issue at all considering the build-dir gets the ".config" built in it.

    EDIT0: This can be closed now. I see that "ZEPHYR_MODULES" and "ZEPHYR_EXTRA_MODULES" differ in that "EXTRA" requires the modules dir.

    With "ZEPHYR_MODULES", I can have them wherever I want. While I had most things I'd use for a project in "ZEPHYR_MODULES", I'd put "extras" like matter in "ZEPHYR_EXTRA_MODULES".

    Once I moved them to "ZEPHYR_MODULES" instead, the "incorrect" squiggles went away. Again, weird that the "CONFIG_" values would still be shown in the ".config" in build-dir.

    For future reference for anyone else that encounters similar issues when using "ZEPHYR_EXTRA_MODULES".

Reply
  • 0 in reply to Amanda Hsieh

    ? How is that meant to correct the incorrect squiggles?  

    ".config" in the build-dir is even showing "CONFIG_CHIP".  

    What is "Missing dependencies: <choice>"? 

    It wasn't an issue with using the same kind of environment when building mcuboot(zephyr-based) or a zephyr app.  

    I've already got like 15 environment variables in my CMakePresets.json, some of which include ZEPHYR_BASE, ZEPHYR_MODULES, ZEPHYR_TOOLCHAIN_VARIANT, CROSS_COMPILE, CHIP_ROOT, PW_ROOT.  

    I think what I'm looking for here is why, even though the CONFIG_ entries exist, your extension seems to not want to acknowledge them. Most are acknowledged. Like I said, no issues with mcuboot.  

    Like "CONFIG_BOOT_SIGNATURE_KEY_FILE" has NO squiggles, and it's from the mcuboot module, just like connectedhomeip is a module.  

    So again, why no issues with mcuboot "CONFIG_"s, but apparently so for matter?  

    I'd think if it's getting it's values, checking for validity from zephyr and the modules' kconfigs (eg "connectedhomeip/config/zephyr/chip-module"), it shouldn't be an issue at all considering the build-dir gets the ".config" built in it.

    EDIT0: This can be closed now. I see that "ZEPHYR_MODULES" and "ZEPHYR_EXTRA_MODULES" differ in that "EXTRA" requires the modules dir.

    With "ZEPHYR_MODULES", I can have them wherever I want. While I had most things I'd use for a project in "ZEPHYR_MODULES", I'd put "extras" like matter in "ZEPHYR_EXTRA_MODULES".

    Once I moved them to "ZEPHYR_MODULES" instead, the "incorrect" squiggles went away. Again, weird that the "CONFIG_" values would still be shown in the ".config" in build-dir.

    For future reference for anyone else that encounters similar issues when using "ZEPHYR_EXTRA_MODULES".

Children
No Data
Related
Terms of service