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

Re-installing nRF Connect SDK

How do I remove nRF Connect SDK from Windows before re-installing?

And are there something that needs to be done, if you have used cmake and Visual Studio Code for other projects?

I installed the tools via nRF Connect Desktop / Toolchain Manager in a project directory, but it looked like the paths got too long. Then I uninstalled the stuff via nRF Connect Desktop / Toolchain Manager, uninstalled the nRF Connect Desktop, removed the stuff from the project directory and rebooted. Then I re-installed everything at C:/ncs, but when I try to do something, it still defaults to the deleted project directory.

Also, when I tried (after re-install) to create the shell_bt_nus from an example and into another folder, I got the ELF-files (ARM code), but the Visual Studio Code shows errors:

[{
    "resource": "/C:/Users/ett15110/Documents/Projects/xxxy/test/shell_bt_nus/src/main.c",
    "owner": "C/C++",
    "code": "1696",
    "severity": 8,
    "message": "cannot open source file \"alloca.h\" (dependency of \"logging/log.h\")",
    "source": "C/C++",
    "startLineNumber": 17,
    "startColumn": 1,
    "endLineNumber": 17,
    "endColumn": 25
},{
    "resource": "/C:/Users/ett15110/Documents/Projects/xxx/test/shell_bt_nus/src/main.c",
    "owner": "C/C++",
    "code": "1696",
    "severity": 8,
    "message": "cannot open source file \"alloca.h\" (dependency of \"zephyr.h\")",
    "source": "C/C++",
    "startLineNumber": 11,
    "startColumn": 1,
    "endLineNumber": 11,
    "endColumn": 20
},{
    "resource": "/C:/Users/ett15110/Documents/Projects/xxx/test/shell_bt_nus/src/main.c",
    "owner": "C/C++",
    "code": "1696",
    "severity": 8,
    "message": "#include errors detected. Consider updating your compile_commands.json or includePath. Squiggles are disabled for this translation unit (C:\\Users\\ett15110\\Documents\\Projects\\xxx\\test\\shell_bt_nus\\src\\main.c).",
    "source": "C/C++",
    "startLineNumber": 11,
    "startColumn": 1,
    "endLineNumber": 11,
    "endColumn": 20
}]

The first two seems to happen, because __GNUC__ seems to not been defined.

And in the target folder it generated .vscode-file with this content:

{
    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [
                "_DEBUG",
                "UNICODE",
                "_UNICODE"
            ],
            "windowsSdkVersion": "10.0.19041.0",
            "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/BuildTools/VC/Tools/MSVC/14.29.30037/bin/Hostx64/x64/cl.exe",
            "cStandard": "c17",
            "cppStandard": "c++17",
            "intelliSenseMode": "windows-msvc-x64",
            "compileCommands": "${workspaceFolder}/build/compile_commands.json",
            "configurationProvider": "nrf-connect"
        }
    ],
    "version": 4
}

I don't think it should use that compiler for anything.

It also found some errors from code for other HW!

Is there a way to "make clean"? I didn't find any.

Parents
  • Hi again

    The files you have listed in text:

    In .nrfconnect-apps/ this only seems to be data from the nRF Connect for Desktop apps, so these aren't related to the nRF Connect SDK Toolchain manager. The /nrfconnect-updater/ includes files for the nRFConnect for Desktop application itself, like the installer and probably uninstaller. Same goes for /Roaming/nrfconnect/.

    The files in /.vscode/extensions/ are extensions installed by Visual Studio code, and are not managed by the toolchain manager either. Same goes for the CachedExtensionVSIXs and workspace folders you've added. These are not affected by the toolchain manager.

    Regarding the error codes from your screenshots, these seem for the most part okay to ignore. The way you'll see that something is wrong while compiling/building you'll get an error message in the terminal where the building is done, and it should refer to what problems in the "Problems" tab to look at.

    Best regards,

    Simon

  • So whom should I contact about those? I'm quite convinced that it wasn't Microsoft that came up with the idea of adding these:

    nordic-semiconductor.nrf-connect-2022.3.104/
    nordic-semiconductor.nrf-devicetree-2022.3.68/
    nordic-semiconductor.nrf-kconfig-2022.1.78/
    nordic-semiconductor.nrf-terminal-2022.3.16/
    trond-snekvik.gnu-mapfiles-1.1.0/

    to the /.vscode/extensions/

    Or should I whine about some of these things to Zephyr project?

    Also, is there a separate forum for nRF Connect for Desktop?

Reply
  • So whom should I contact about those? I'm quite convinced that it wasn't Microsoft that came up with the idea of adding these:

    nordic-semiconductor.nrf-connect-2022.3.104/
    nordic-semiconductor.nrf-devicetree-2022.3.68/
    nordic-semiconductor.nrf-kconfig-2022.1.78/
    nordic-semiconductor.nrf-terminal-2022.3.16/
    trond-snekvik.gnu-mapfiles-1.1.0/

    to the /.vscode/extensions/

    Or should I whine about some of these things to Zephyr project?

    Also, is there a separate forum for nRF Connect for Desktop?

Children
No Data
Related