Re-installing nRF Connect SDK

RE: Re-installing nRF Connect SDK

turboscrew — Fri, 08 Apr 2022 12:36:10 GMT

OK, thanks. I'll line with the errors for now. I'll check things again, when(/if) I start, actually, using it for a project.

I've just been getting ready.

RE: Re-installing nRF Connect SDK

Simonr — Fri, 08 Apr 2022 06:58:51 GMT

Hi again

To get the NCS master, you will have to install NCS manually as explained here and get the code from our git repo, as the master branch haven't been included in the toolchain manager yet. I think the Z_FOR_LOOP_1 errors should be taken care of in the next release of the nRF Connect SDK for the Toolchain manager.

Best regards,

Simon

RE: Re-installing nRF Connect SDK

turboscrew — Thu, 07 Apr 2022 10:28:13 GMT

Looks like some update (probably windows update) fixed the changes watcher. It doesn't seem to crash anymore.

AFTER noticing that, I, once again, removed the SDK and desktop, downloaded the latest desktop version and installed everything again. The Z_FOR_LOOP_1 errors are still there.

RE: Re-installing nRF Connect SDK

turboscrew — Thu, 07 Apr 2022 06:32:17 GMT

No. The only thing it gives me is "copy text".

BTW, how do you update that "NCS master"?

I did

PS C:\ncs\v1.9.1> west update

and I still got the Z_FOR_LOOP_1 errors.

MINGW64 /c/ncs/v1.9.1/zephyr ((v2.7.99-ncs1-1))
$ git fetch origin
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

AHA: even if the web pages don't tell that, there's a menu item in the toolchain manager "Update SDK".

That didn't remove the Z_FOR_LOOP_1 errors, though.

RE: Re-installing nRF Connect SDK

Simonr — Tue, 05 Apr 2022 11:30:49 GMT

Are you able to right click that notification to get information on what extension that notification comes from exactly?

Best regards,

Simon

RE: Re-installing nRF Connect SDK

turboscrew — Tue, 05 Apr 2022 04:39:48 GMT

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?

RE: Re-installing nRF Connect SDK

turboscrew — Tue, 05 Apr 2022 04:26:53 GMT

The notification in the lower right corner. If I click "reload", it does something (probably checks for changed files) and right after that, the notification emerges again. Also after some configuration changes, nothing happens until I click that "reload".

RE: Re-installing nRF Connect SDK

Simonr — Tue, 29 Mar 2022 05:33:31 GMT

One of our developers of the VS code extension has looked into these issues and have come with the following comments.

We have merged a PR into the latest main branch that addresses these multiple errors/warnings in the problems tab to only show them for the open file(s). We might add more filtering later as that likely will be useful.

Fhe Z_FOR_LOOP_1 issue you've seen is fixed in the NCS master, and is not actually a VS code issue. It was due to an abuse of the preprocessor in the logging macros.

Best regards,

Simon

RE: Re-installing nRF Connect SDK

Simonr — Mon, 28 Mar 2022 06:48:27 GMT

Both the problem tab and the "previous install path" issue are being looked at, but they shouldn't be necessary to create a working .hex or .elf file.

Can you explain more about the issue you have with the watcher crashing?

I'm afraid there's not too much we can do with the Intellisense config.

Best regards,

Simon

RE: Re-installing nRF Connect SDK

turboscrew — Wed, 23 Mar 2022 11:54:04 GMT

It works (compiles and generates the elf and hex files), but not properly.

The main issues:

- wrong C code parser the VS Code (Intellisense?) uses (being studied, I understood - the problems tab)

- configuration defaults from previous installs (wrong SDK version, etc.)

- changes watcher crashing (if I restart it, it checks the changes OK, and crashes after that)

- the Intellisense configuration (c_cpp_properties.json) seldom gets generated.

The changes watcher wakes up all kinds of configurations. If you add a file, the IDE won't notice, and doesn't run cmake, unless you restart the changes watcher (which crashes after that).

I don't have a board yet, so that's how far I have been able to try.

RE: Re-installing nRF Connect SDK

Simonr — Wed, 23 Mar 2022 11:36:06 GMT

Yes, that should be possible, I have both SEGGER and Keil µVision and I'm able to get VS code up and running. There is an issue with the "Problems" tab that we're looking into, but you should be able to build and flash sample projects anyway.

If a new install of the nRF Connect SDK for VS code is not working for me, it usually fixes the issue to just uninstall the SDK from the Toolchain manager and reinstalling it (I personally have used the same path all along), but changing it should be okay too. Is the compiling, building and flashing of projects not working properly on your end?

Best regards,

Simon

RE: Re-installing nRF Connect SDK

turboscrew — Wed, 23 Mar 2022 11:19:27 GMT

I just wonder...

Is there a way to get he VS Code version to work properly? I don't seem to be able to clean my systen to be able to do clean (re-)install.

And I wonder if the fact that I have other development environments installed too, that use the VS Code in a different way, somehow messes with the nRF Connect SDK VS Code settings?

RE: Re-installing nRF Connect SDK

turboscrew — Tue, 22 Mar 2022 08:44:02 GMT

I guess, the nRF Connect for Desktop configures the nRF Connect SDK Toolchain manager wrong?

And some Nordic SW somewhere generated those Visual Studio Code configurations.

And after cleaning up all the stuff listed, the nRF Connect to VS Code finds (and keeps offering) the old nRF Connect SDK version (and some other old settings as well).

I think that means, that the install/uninstall doesn't quite work. And since you are encouraged to use nRF Connect for Desktop for installing the environment, I think that makes the nRF Connect Desktop, nRF Connect SDK Toolchain manager and nRF Connect SDK sort of bundled. A new user (probably), like me, can't really make a difference about which installer/SDK is responsible of what.

Anyway, I guess, I just need to ignore all errors shown by the VS Code and just look at the error in the compilation terminal window, or use SES.

(And the file changes watcher still keeps crashing.)

RE: Re-installing nRF Connect SDK

Simonr — Tue, 22 Mar 2022 08:12:00 GMT

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

RE: Re-installing nRF Connect SDK

turboscrew — Tue, 22 Mar 2022 08:10:55 GMT

Any idea what's wrong in my setup? Or what more do I need to clean up to make a clean re-install?

RE: Re-installing nRF Connect SDK

turboscrew — Mon, 21 Mar 2022 07:44:52 GMT

I try to add the files here.

devzone.nordicsemi.com/.../nRF_5F00_Connect_5F00_cap_5F00_1_2D00_6.zip devzone.nordicsemi.com/.../nRF_5F00_Connect_5F00_cap_5F00_17_2D00_21.zip devzone.nordicsemi.com/.../nRF_5F00_Connect_5F00_screen_5F00_captures.txt

RE: Re-installing nRF Connect SDK

Simonr — Mon, 21 Mar 2022 07:30:41 GMT

The .zip file can be uploaded here on DevZone, by choosing Insert -> Image/Video/File, and then pressing the Upload button to upload a file from your computer.

If the .zip file is too large try to upload, try splitting it up into multiple files. A lot of these error messages you report seem to be error codes produced by VS code that can be ignored, and we are already working on improving the nRF Connect extension to not report many of these, as it more than anything causes a lot of confusion.

Best regards,

Simon

RE: Re-installing nRF Connect SDK

turboscrew — Fri, 18 Mar 2022 08:56:09 GMT

Hmm, maybe the stuff left after uninstall can be better listed in text.

These are listed after 1.9.1 was installed, but the same stuff was left behind when the 1.9.0 was uninstalled.

I removed manually everything that looked like something to do with nRF Connect Desktop or nRF Connect SDK, but when I installed 1.9.1, it still found some old settings. I, obviously, didn't find them all.

ett15110@ETTRE253067 MINGW64 ~/.nrfconnect-apps
$ ls -a
./ pc-nrfconnect-linkmonitor.svg
../ pc-nrfconnect-ppk.svg
apps.json pc-nrfconnect-programmer.svg
external/ pc-nrfconnect-rssi.svg
local/ pc-nrfconnect-toolchain-manager.svg
node_modules/ pc-nrfconnect-tracecollector-preview.svg
pc-nrfconnect-ble.svg pc-nrfconnect-tracecollector.svg
pc-nrfconnect-dtm.svg updates.json
pc-nrfconnect-gettingstarted.svg

ett15110@ETTRE253067 MINGW64 ~/.vscode/extensions
$ ls -a
./
../
.obsolete
austin.code-gnu-global-0.2.2/
cschlosser.doxdocgen-1.4.0/
marus25.cortex-debug-1.2.2/
ms-vscode-remote.remote-containers-0.224.3/
ms-vscode-remote.remote-ssh-0.76.1/
ms-vscode-remote.remote-ssh-edit-0.76.1/
ms-vscode-remote.remote-wsl-0.64.2/
ms-vscode.cmake-tools-1.10.4/
ms-vscode.cmake-tools-1.9.2/
ms-vscode.cpptools-1.8.4/
ms-vscode.cpptools-extension-pack-1.1.0/
ms-vscode.cpptools-themes-1.0.0/
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/
twxs.cmake-0.0.17/

ett15110@ETTRE253067 MINGW64 ~/AppData/Local/nrfconnect-updater
$ ls -a
./ ../ installer.exe*

ett15110@ETTRE253067 MINGW64 ~/AppData/Roaming/nrfconnect
$ ls -a
./ Preferences
../ 'Session Storage'/
.updaterId TransportSecurity
Cache/ blob_storage/
'Code Cache'/ logs/
Cookies 'nRF Connect for Desktop'/
Cookies-journal pc-nrfconnect-launcher.json
Dictionaries/ pc-nrfconnect-shared.json
GPUCache/ pc-nrfconnect-toolchain-manager/
'Local Storage'/ pc-nrfconnect-toolchain-manager.json
'Network Persistent State' settings.json

ett15110@ETTRE253067 MINGW64 ~/AppData/Roaming/Code/CachedExtensionVSIXs
$ ls -a
./
../
austin.code-gnu-global-0.2.2
cschlosser.doxdocgen-1.4.0
jeff-hykin.better-cpp-syntax-1.15.13
marus25.cortex-debug-1.2.2
ms-vscode-remote.remote-containers-0.224.3
ms-vscode-remote.remote-ssh-0.76.1
ms-vscode-remote.remote-ssh-edit-0.76.1
ms-vscode-remote.remote-wsl-0.64.2
ms-vscode.cmake-tools-1.10.4
ms-vscode.cmake-tools-1.9.2
ms-vscode.cpptools-1.5.1
ms-vscode.cpptools-1.8.4-win32-x64
ms-vscode.cpptools-extension-pack-1.1.0
ms-vscode.cpptools-themes-1.0.0
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
twxs.cmake-0.0.17

ett15110@ETTRE253067 MINGW64 ~/AppData/Roaming/Code/Workspaces/1647582940206
$ cat workspace.json
{
"folders": [
{
"name": "shell_bt_nus",
"path": "C:\\ncs_test\\shell_bt_nus"
}
]
}

ett15110@ETTRE253067 MINGW64 ~/AppData/Roaming/Code/User
$ cat settings.json
{
"nrf-connect.welcome.showOnStartup": true,
"nrf-connect.topdir": "${nrf-connect.sdk:1.9.1}",
"nrf-connect.toolchain.path": "${nrf-connect.toolchain:1.9.1}",
"nrf-connect.enableTelemetry": false,
"cmake.configureOnOpen": true
}

ett15110@ETTRE253067 MINGW64 ~/AppData/Roaming/Code
$ cat storage.json
{
"telemetry.machineId": "9f43b368088c07bb0806bdaee446a8bcf15f6536b5a999a19a571b13c0c213d8",
"theme": "vs-dark",
"themeBackground": "#1e1e1e",
"pickerWorkingDir": "C:\\ncs_test\\shell_bt_nus",
"windowsState": {
"lastActiveWindow": {
"folder": "file:///c%3A/ncs_test/shell_bt_nus",
"backupPath": "C:\\Users\\ett15110\\AppData\\Roaming\\Code\\Backups\\abfe5d0f9e442f578000ba79076f26d5",
"uiState": {
"mode": 0,
"x": 448,
"y": 156,
"width": 1024,
"height": 768
}
},
"openedWindows": []
},
"windowSplash": {
"baseTheme": "vs-dark",
"colorInfo": {
"foreground": "#cccccc",
"background": "#1e1e1e",
"editorBackground": "#1e1e1e",
"titleBarBackground": "#3c3c3c",
"activityBarBackground": "#333333",
"sideBarBackground": "#252526",
"statusBarBackground": "#007acc",
"statusBarNoFolderBackground": "#68217a"
},
"layoutInfo": {
"sideBarSide": "left",
"editorPartMinWidth": 220,
"titleBarHeight": 30,
"activityBarWidth": 48,
"sideBarWidth": 300,
"statusBarHeight": 22,
"windowBorder": false
}
}
}

RE: Re-installing nRF Connect SDK

turboscrew — Fri, 18 Mar 2022 07:16:30 GMT

It looks like I could only upload one image file per reply.

Well, here's nRF_Studio_VSCode_17.JPG at least.

RE: Re-installing nRF Connect SDK

turboscrew — Fri, 18 Mar 2022 06:19:13 GMT

The 1.9.1 is installed, and the 1.9.0 hounts again.

After all those old stuff removal followed by reboot, it still finds that old setting somewhere.

Five more screenshots about reinstallation and creating an application from an example.

nRF_Studio_VSCode_17.JPG
Created application from an example. It offers 1.9.0, but I select 1.9.1
(Where did it find the 1.9.0?)

nRF_Studio_VSCode_18.JPG
Extension conflict

nRF_Studio_VSCode_19.JPG
I clicked "Show conflicting extensions"

nRF_Studio_VSCode_20.JPG
After restarting the change watcher, it, again, suggests using c:\ncs\v1.9.0\zephyr.
I clicked "Change" and selected v1.9.1
Had to restart the change watcher, because touching the snipping tool made
the notification disappear without selection.

nRF_Studio_VSCode_21.JPG
Then I restarted changes watcher again, and again it suggests c:\ncs\v1.9.0\zephyr.

Note, that there is no folder c:\ncs\v1.9.0 any more. Only c:\ncs\v1.9.1.

RE: Re-installing nRF Connect SDK

turboscrew — Thu, 17 Mar 2022 14:19:36 GMT

Yes. The configuration doesn't let go of the old setups even if everything is uninstalled and re-installed, and a new example is created with different version of nRF Connect SDK (tried with 1.9.0 instead of earlier 1.9.1).

I'll get back tomorrow with some screenshots.

Demo-effect hit. Now it suddenly found the right SDK-version. Let's see when I re-install 1.9.1 tomorrow...

I already removed everything, and there are quite some screenshots about stuff left behind. That might help the uninstaller writers.

I have a 1.5MB zip-file of screen captures (16 of them). I wonder how to get them to you.

nRF_Studio_VSCode_1.JPG
Initial errors

nRF_Studio_VSCode_2.JPG
Configuration errors

nRF_Studio_VSCode_3.JPG
Errors after intellisense configuration

About half the time, when you create a new application from an example, it asks if it can configure
the intellisense. When it configures, there "missing h-files" complaints mostly disappear,
but it still shows errors. The SW, however, compiles.

nRF_Studio_VSCode_4.JPG
Intellisense configuration

nRF_Studio_VSCode_5.JPG
Board error and changes watcher notification

nRF_Studio_VSCode_6.JPG
Software still compiles, suggesting that tha errors are false artefacts by the Visual Studio Code
The problem is, if it doesn't compile, how to tell which errors are the real errors and which
are false artefacts by Visual Studio Code / Intellisense.

nRF_Studio_VSCode_7.JPG - nRF_Studio_VSCode_16.JPG
Stuff left behind after uninstall

The 1.9.1-version is being installed.

RE: Re-installing nRF Connect SDK

Simonr — Thu, 17 Mar 2022 12:17:34 GMT

Hi again

It seems like you found the path to where nrfconnect stores various data at C:\Users\***\AppData\Roaming\nrfconnect.

Are you still seeing the same errors with the "old installation paths" after deleting the files "left" in \AppData\Roaming\nrfconnect ? I will report this internally so our devs can take a look at it. If you could show where these error messages are printed, maybe with a screenshot or just by explaining that would be great as well.

Best regards,

Simon

RE: Re-installing nRF Connect SDK

turboscrew — Thu, 17 Mar 2022 07:08:49 GMT

It looks like the Visual Studio Code configuration doesn't work. VSCode gets configured wrong, and configurations are hidden in places where the uninstall doesn't find and remove them. After reinstall, the new setup still defaults to some stuff from some old installation, and refuses to update those defaults.

Fortunately, Segger Embedded Studio seems to work.

RE: Re-installing nRF Connect SDK

turboscrew — Wed, 16 Mar 2022 11:21:43 GMT

When I manually created this file, the include files were found (by VSCode):

.vscode/c_cpp_properties.json:
{
    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [
                "_DEBUG",
                "UNICODE",
                "_UNICODE"
            ],
            "windowsSdkVersion": "10.0.19041.0",
            "compilerPath": "C:/ncs/v1.9.1/toolchain/opt/bin/arm-none-eabi-gcc.exe",
            "cStandard": "${default}",
            "cppStandard": "${default}",
            "intelliSenseMode": "${default}",
            "compileCommands": "${workspaceFolder}/build/compile_commands.json"
        }
    ],
    "version": 4
}

For the blinky, the IDE asked for configuring the VSCode, but not for the shell_bt_nus.

And even if shell_bt_nus compiles fine, the VSCode still gives these error messages:

[{
   "resource": "/C:/Users/ett15110/Documents/Projects/xxx/test/shell_bt_nus/src/main.c",
   "owner": "C/C++",
   "code": "54",
   "severity": 8,
   "message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
   "source": "C/C++",
   "startLineNumber": 45,
   "startColumn": 2,
   "endLineNumber": 45,
   "endColumn": 9
},{
   "resource": "/C:/Users/ett15110/Documents/Projects/xxx/test/shell_bt_nus/src/main.c",
   "owner": "C/C++",
   "code": "54",
   "severity": 8,
   "message": "too few arguments in invocation of macro \"Z_FOR_LOOP_1\"",
   "source": "C/C++",
   "startLineNumber": 147,
   "startColumn": 2,
   "endLineNumber": 147,
   "endColumn": 9
}]

RE: Re-installing nRF Connect SDK

turboscrew — Wed, 16 Mar 2022 09:43:28 GMT

Not good. It still doesn't configure the Visual Studio Code right.

Tried two examples (blinky and shell_bt_nus). Neither had the file .vscode/c_cpp_properties.json, in shell_bt_nus-example, in the file .vscode/settings.json had "nrf-connect.application" left empty.

Both examples compile and produce zephyr.elf, but in both cases Visual Studio Code complains that it can'f find the include files.

Also, this keeps happening. (It doesn't seem to work at all.)

File changes watcher stopped unexpectedly. A reload of the window may enable the watcher again unless the workspace cannot be watched for file changes.