Kconfig failed: [Errno 22] Invalid argument

[MontanaEE]

Kconfig failed: [Errno 22] Invalid argument: 'c:/users/user/zephyr/kconfig"' is an error that appeared this morning.  What is supposed to be in the Kconfig file.  I have been trying to solve this most of the day.  Prj.conf is the file the error originates from on the first line.

[Menon]

Hello,

Could you please check the terminal to view the complete log while building? This might provide more details on the error message. Please share the full log here. Also, what happens when you try building a sample application from the SDK?

Kind regards,
Abhijith

[MontanaEE]

Also, if I try building a sample application from the SDK, I get the same error.  Sorry for the delay, just wanted to confirm that first

[Johnny Nguyen]

Hi Stephen,

the conf looks fine, as well as the terminal bar the warnings below the build message.

Did it ever build without error? Is this a fresh install?

Seems like a bad install or VSC being misconfigured. (HOME variable for instance, given the Kconfig gui not opening up) 

Can you try updating to the latest vsc extensions and installing latest sdk/toolchain versions?

[MontanaEE]

Johnny,

Doesn't look like my reply went through yesterday. I checked for updates on VSC.  It says I'm up to date, but at this point I will re-install and see.  I was using 2.7, but when this problem started,.I went back to 2.4.1 on both toolchain and SDK simply because that was the original recommended by the DVK.   I will go back to 2.7.

[MontanaEE]

Just ran on to this.  None of the GUIConfig and MenuConfig can launch either and all state "Unable to find Kconfig information to display. Please select a Kconfig file first."  I think I may be a victim of an auto-update..... I am not sure how to fix this. See below:

  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\User\AppData\Roaming\Python\Python311\Scripts\west.exe\__main__.py", line 4, in <module>
  File "C:\ncs\toolchains\ce3b5ff664\opt\bin\Lib\site-packages\west\app\main.py", line 34, in <module>
    from west.commands import WestCommand, extension_commands, \
  File "C:\ncs\toolchains\ce3b5ff664\opt\bin\Lib\site-packages\west\commands.py", line 24, in <module>
    import pykwalify
  File "C:\ncs\toolchains\ce3b5ff664\opt\bin\Lib\site-packages\pykwalify\__init__.py", line 7, in <module>
    import logging.config
  File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\logging\config.py", line 30, in <module>
    import logging.handlers
  File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\logging\handlers.py", line 26, in <module>
    import io, logging, socket, os, pickle, struct, time, re
  File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\socket.py", line 51, in <module>
    import _socket
ImportError: Module use of python39.dll conflicts with this version of Python.

 

[Johnny Nguyen]

Hi Stephen, I've reached out via e-mail.

[Johnny Nguyen]

Just following up:

Issue was with the toolchain and the way Ezuro/Laird wants the Pinnacle-100 firmware environment set up, and how it interacts with the VSC environment.

For reference: LairdCP/Pinnacle_100_Sample_Applications_Manifest: Manifest repo for Pinnacle 100 sample applications

LairdCP/Pinnacle-100-Firmware: Common repository for MG100 and Pinnacle 100 DVK firmware.

Looking at OP, when toolchain was adjusted it started trying to reference things that simply weren't in the SDK. (Such as CONFIG_LCZ)

Resolved by adjusting toolchain and making sure it played nice with that manifest repo.