How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Thu, 24 Mar 2022 20:19:40 GMT

Øyvind,

Understand, but would still like to pursue a solution to the issues I have with the SES IDE from my side. Can you point me at:

SES documentation on how extensions like "File | Open nRF Connect Solution..." menu command are implemented. (Didn't find that info on a quick scan of the SES user guide.)
The files in the v1.9.1 SDK that implement this specific extension. (Are they open source or proprietary?)

Thanks,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Øyvind — Thu, 24 Mar 2022 09:16:40 GMT

Hi Mike, I'm afraid there isn't much we can do without any method to reproduce.

[quote user="mikew67"]Pending that, I'll do my code development with the VS Code IDE (new to me).[/quote]

Yes, please do. We think that the VS Code extension is a better solution compared to SES, and is easier/quicker to fix from our side.

Kind regards,
Øyvind

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Thu, 24 Mar 2022 07:57:57 GMT

Øyvind,

I can report that the nRF Connect Extension for VS Code appears to work fine with the automatically installed SDK v1.9.1. I was able to build, flash and execute sample apps. This, with my correction of a Python installation/asdf-virtual-environment error on my side (which caused west launch problems) leaves only one issue unsolved from all of the discussions in this ticket, i.e., the red Script Error (unable to parse JSON string) popup while initializing the nRF Connect Options window.

Any ideas on how to make progress on this remaining issue?

Pending that, I'll do my code development with the VS Code IDE (new to me).

Thanks for the help thus far,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Øyvind — Wed, 23 Mar 2022 08:54:18 GMT

Our nRF Connect for Desktop developers answers that this looks like a bug with SES. They are not able to reproduce on their MacOS setup.

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Wed, 23 Mar 2022 00:32:20 GMT

No joy. There is no output in the SES Output window (see below). Note that, in order to execute the SES View | Output menu command, I need to click OK to close the red Script error popup, and Cancel to close the nRF Options window.

HTH,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Øyvind — Tue, 22 Mar 2022 09:15:46 GMT

Can you please go to View --> Output. There should be some sort of output giving the path/name of what script is failing.

Thanks!
-Øyvind

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Tue, 22 Mar 2022 08:07:19 GMT

Nope, Here are all 3 windows/panes (split onto two displays so you can see more of the SES desktop)

Note that the script hasn't gotten far enough to initialize any of the Options fields. There all dead.

HTH,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Øyvind — Tue, 22 Mar 2022 07:05:26 GMT

Mike,

do you get anything in the output pane of SES when you get this script error popup?

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Tue, 22 Mar 2022 06:53:17 GMT

Øyvind,

Thanks for the suggestion to add to my PATH variable, presumably to fix west access. Since my last message, I added Python 3.10.3 to my set of installed Python versions, all under control of asdf. Being careful with the new install appears to have fixed my asdf configuration issue.

I removed my last v1.9.1 SDK installation and reinstalled using nRF Connect for Desktop/Toolchain Manager. The installation went without error. And west is now accessible from the command line in a terminal session opened from the Toolchain Manager pane | downward triangle button.

That's the good news. But I still get the red Script Error popup in the nRF Connect Options window in SES (exactly as reported in the very first message that created this ticket).

Asking again, can you give me the pathname of the script file that produces the JSON error? Knowing that, I try to diagnose where that file is being corrupted.

Thanks,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Øyvind — Tue, 22 Mar 2022 06:05:04 GMT

Hi Mike, thanks for pointing the issue with West out. I agree that west does exist/is installed correctly, but it looks like the path to your python packages have not been added to your PATH variable. Could you try running the following PATH=$PATH:${HOME}/.local/bin

I see that you had a similar issue here, is this the same issue?

Kind regards,
Øyvind

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Mon, 21 Mar 2022 08:54:13 GMT

Results of Further Testing:

My Windows 10 VM was broken. Built a new, clean Win10 VM (64-bit), installed nRF Connect for SDK Desktop app, Tool Manager, SDK 1.91. All went without error!
From an "Open Terminal" window, it is possible to demonstrate that the west.exe stub does exist and west can be invoked directly from the command line, both of which can be seen from this screen shot.

SES launches properly from clicking the "Start SES" button in Tool Manager.
The Project Options pane opens without error from the "File | Open nRF Project..." SES menu command.
Solution nrf_ dm on nrf52840dk_ nrf52840 generated and built OK
Solution nrf_ led matrix on bbc_ microbit v2 generated and built OK

In other words, everything worked as it should on Windows 10.

In contrast, I should note:

Here's the corresponding terminal output regarding the configuration of the west module on my MacBook Pro running macOS Monterey:
Note that a "west.exe" doesn't exist (That's a Windows app), but a "west" file does exist at pathname "../../../west"
Converting to an absolute path, that's: /Users/mike/.asdf/installs/python/3.10.0/bin/west
That's inside a directory controlled by the asdf virtual environment system I'm using to control multiple Python versions (a multi-language tool more general than env) and, unfortunately, not in the right place to be executed directly from the command line.

Not sure how to correct this yet, but it certainly points to a problem with west execution in my particular macOS environment.

Not sure yet if all of the issues I've encountered are due to this one cause, but fixing it is certainly a good place to start. I've noted that your online docs now(?) include some comments about use of venv in the Mac environment. Would be great if you could get together with one of your Python experts to sort out what the proper nRF SDK installation procedures are in a complex Python environment. I suspect this isn't just a macOS problem, just where we've first encountered it.

I'll work from my end, but I'm neither a venv or asdf expert. Just give me some suggestions and I'll try them out. I suspect this will result in some extra cautions in the documentation or even changes to the installation code.

Thanks,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Sun, 20 Mar 2022 21:44:58 GMT

I have started. to install nRF Connect for Desktop on another MacBook Pro. It's an older 5,3 model, but running a clean installation of macOS Monterey. Hopefully, installation here, if it's different from my MBP 10,1 will help me diagnose the problems I'm seeing.

Installation on the MBP is not yet complete. Here are two issues encountered along the way:

Automatic SDK installation cannot be done. When a newly installed nRF Connect app is installed and launched, the plugins selector window opens, but, is totally blank/gray. This is probably due to a graphics patch in macOS to allow it to run on this older machine. So ignoring this problem for the moment.

But it does mean that I needed to revert to the manual SDK installation instructions for this test. Did so. All proceeded correctly and a full set of repositories, and tools were installed -- all the way to the end of installation instructions, just before first use of SES or VS Code.

Except for one item, which has been experienced on all macOS installations. Despite what's (implied?) in the documentation, there is no command line launcher for west. West is not an app, but a Python module. Normally in such cases, there is a small executable app, a stub, which when started launches the module. I've found no such stub in the west directory or related files. Am I missing something?

As noted in the attached terminal log, "west" is not a recognized command, but "python -m west" (i.e., invoking it as a module) works everywhere.

mike@Mikes-MBP-53 ~ % west --help
zsh: command not found: west
mike@Mikes-MBP-53 ~ % python -m west --help
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...

The Zephyr RTOS meta-tool.

optional arguments:
  -h, --help            get help for west or a command
  -z ZEPHYR_BASE, --zephyr-base ZEPHYR_BASE
                        Override the Zephyr base directory. The default is
                        the manifest project with path "zephyr".
  -v, --verbose         Display verbose output. May be given multiple times
                        to increase verbosity.
  -V, --version         print the program version and exit

built-in commands for managing git repositories:
  init:                 create a west workspace
  update:               update projects described in west manifest
  list:                 print information about projects
  manifest:             manage the west manifest
  diff:                 "git diff" for one or more projects
  status:               "git status" for one or more projects
  forall:               run a command in one or more local projects

other built-in commands:
  help:                 get help for west or a command
  config:               get or set config file values
  topdir:               print the top level directory of the workspace

Cannot load extension commands; help for them is not available.
(To debug, try: "west manifest --validate".)

Run "west help <command>" for help on each <command>.
mike@Mikes-MBP-53 ~ %

Surprising that this issue doesn't cause more extensive problems. At the moment it has halted my progress with the manual SDK next step, setting up SES. I need to enter the pathname of the west executable in the SES configuration, but there is no such file apparent.

FYI, here's the structure of the west package, as reported by pip:

mike@Mikes-MBP-53 ~ % pip3 show -f west 
Name: west
Version: 0.12.0
Summary: Zephyr RTOS Project meta-tool
Home-page: https://github.com/zephyrproject-rtos/west
Author: Zephyr Project
Author-email: devel@lists.zephyrproject.org
License: UNKNOWN
Location: /Users/mike/.asdf/installs/python/3.10.2/lib/python3.10/site-packages
Requires: colorama, packaging, pykwalify, PyYAML, setuptools
Required-by: 
Files:
  ../../../bin/west
  west-0.12.0.dist-info/INSTALLER
  west-0.12.0.dist-info/LICENSE
  west-0.12.0.dist-info/METADATA
  west-0.12.0.dist-info/RECORD
  west-0.12.0.dist-info/REQUESTED
  west-0.12.0.dist-info/WHEEL
  west-0.12.0.dist-info/entry_points.txt
  west-0.12.0.dist-info/top_level.txt
  west/__init__.py
  west/__main__.py
  west/__pycache__/__init__.cpython-310.pyc
  west/__pycache__/__main__.cpython-310.pyc
  west/__pycache__/build.cpython-310.pyc
  west/__pycache__/cmake.cpython-310.pyc
  west/__pycache__/commands.cpython-310.pyc
  west/__pycache__/configuration.cpython-310.pyc
  west/__pycache__/log.cpython-310.pyc
  west/__pycache__/manifest.cpython-310.pyc
  west/__pycache__/util.cpython-310.pyc
  west/__pycache__/version.cpython-310.pyc
  west/app/__init__.py
  west/app/__pycache__/__init__.cpython-310.pyc
  west/app/__pycache__/config.cpython-310.pyc
  west/app/__pycache__/main.cpython-310.pyc
  west/app/__pycache__/project.cpython-310.pyc
  west/app/config.py
  west/app/main.py
  west/app/project.py
  west/build.py
  west/cmake.py
  west/commands.py
  west/configuration.py
  west/log.py
  west/manifest-schema.yml
  west/manifest.py
  west/util.py
  west/version.py
  west/west-commands-schema.yml
mike@Mikes-MBP-53 ~ %

Do you have a quick suggestion for this west executable issue? If not, I won't be able continue testing on this alternate MacBook Pro.

Thanks,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Sat, 19 Mar 2022 21:35:53 GMT

Øyvind,

The answer to one question would allow me to do some debugging: What's the pathname of the script file which causes the red error dialog in SES: Script Error?

Thanks,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Sat, 19 Mar 2022 04:57:24 GMT

Øyvind,

Thanks for your persistence in trying to deal with the issues I've encountered. Responding to your message of 18 hrs ago, with your questions indented: (By the way, the Devzone "reply" mechanism seems clumsy, especially when there is a repeated sequence of replies and answers,). And I should note, I'm trying to act as a member of your test team, reporting issues that might cause trouble for other users and suggestions for correcting them. I hope you find this useful.

But what version of SES are you opening, the one that follows Toolchain Manager or a manually installed?

I'm using the copy of SES that is bundled in your SDK installation, at /opt/nordic/ncs/v1.9.1/toolchain/segger_embedded_studio/SEGGER Embedded Studio for ARM 5.68.app. I have noted before that manual installations of SES, either directly from Segger, or even the Nordic-configured version from your website can create problems (e.g., with licensing, and with differences in execution environment, so I've removed all SES code except the SDK-bundled version at the path above.

As an aside, even if I start with your specially configured version of SES, but follow the manual SDK instructions, I suspect it won't end up at the same path as listed above. Won't this create problems for manual-SDK-installers?

On another question, after I've done an automatic SDK installation, how am I expected to start an SES session? Can I invoke the app from the command line at the above listed path? Or do I need to go through nRF Connect app | Tool Manager plugin | "Start SES" button every time? The latter ensures certain environment variables are set. In the former case, I could have invoked SES from some random terminal session and environment. Seems like this should be in the docs.

...The Open nRF Connect Project dialog will list available projects in the nRF Connect SDK folder.

Perhaps some confusion here. When I mention old projects appearing, that's in the SES Desktop, not the triangle selector in the "Open nRF Project" Options panel. And to add a clarification, you say "in the nRF Connect SDK folder". That's technically correct, but it would probably be useful to note that these samples are in two distinct groups, those at /opt/nordic/ncs/v1.9.1/nrf/samples and at /opt/nordic/ncs/v1.9.1/zephyr/samples. The triangle selector in the Options panel attempts to list the contents of both, but at least on my MacBook Pro, the performance of scrolling through the list is jumpy and hitting any element is problematic.

Are you able to see nRF Connect SDK Release and Toolchain versions?

I presume you mean the following:

The nRF Connect for Desktop app is v3.10.0
The Toolchain Manager plugin is v0.10.3
The nrf git repository includes the HEAD/v1.9.1 tags from March 4, and are up to date with commits up to today, the origin/main, origin/HEAD tags.
The zephyr git repository includes the ncs/V2.7.99-ncs1-1 from Feb. 28, and ncs/test-spec & ncs/main tags from today.

Are you able to see nRF Connect SDK Release and Toolchain versions? Make sure that the Segger Embedded Studio actually points to correct nRF Connect SDK folder.

Yes, as shown here:

If your SES is pointing to /opt/nordic/ncs/v1.9.1 will it still give the script error /syntax error?

Yes, indeed. When I start up SES, its Desktop appears (by double clicking the app icon at: /opt/nordic/ncs/v1.9.1/toolchain/segger_embedded_studio/SEGGER Embedded Studio for ARM 5.68.app, the desktop opens. If I then execute the File | Open nRFConnect SDK Project... command, the nRF Connect Options window opens with the Script Error dialog in the middle:

If, however, I start SES by clicking on the alias at /opt/nordic/ncs/v1.9.1/toolchain/segger_embedded_studio/SEGGER Embedded Studio.app, SES immediately follows the desktop with opening the nRF Connect Options window with the same error message, without having to execute the File menu command.

I had similar issues when trying to download the SDK via VPN or LTE connection. Are you downloading on a corporate network or using a corporate computer?

I'm on a fairly direct, domestic (non-business) connection, 1 Gbps fiber. So not much issue there.

One possible glitch: I'm running the Avast Security v15.2 antivirus software, which does examine incoming files, web pages, email, etc. It finds and filters plenty of infected spam email, but I've never had it modify a download. It should certainly tell me if it has. I can try an nRF Connect SDK auto install with it disabled to see if it makes any difference. Your recommendation?

So, no further ahead from my perspective. Will await suggestions from you.

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Øyvind — Fri, 18 Mar 2022 08:30:43 GMT

Hi Mike,
Thanks for sharing these details.

[quote user="mikew67"]Not in my experience After removing and reinstalling the SDK, old project info still persists in SES.[/quote]

First of all, this is a known issue with SES. But what version of SES are you opening, the one that follows Toolchain Manager or a manually installed? I'm not sure what you mean with list of recent projects. The Open nRF Connect Project dialog will list available projects in the nRF Connect SDK folder. This will be samples found under both nrf/samples and zephyr/samples, and you can narrow these down with the different checkboxes.

Are you able to see nRF Connect SDK Release and Toolchain versions? Make sure that the Segger Embedded Studio actually points to correct nRF Connect SDK folder. You can check this under Tools --> Options --> nRF Connect --> Directories.

From the support information you provided, I can see that you have the following SDK versions:

  "sdks": [
    {
      "version": "1.9.1",
      "path": "/Users/mike/ncs"
    },
    {
      "version": "Zephyr 3.0.99",
      "path": "/Users/mike/zephyrproject"
    },
    {
      "version": "1.9.1",
      "path": "/opt/nordic/ncs/v1.9.1"
    }

If your SES is pointing to /opt/nordic/ncs/v1.9.1 will it still give the script error /syntax error?

[quote user="mikew67"]The resulting Toolchain Manager window below shows that the final configuration Is broken in at least one way -- the Open SES button is missing.[/quote]

I had similar issues when trying to download the SDK via VPN or LTE connection. Are you downloading on a corporate network or using a corporate computer? The solution that worked for me was to use a standard WiFi connection at home or similar (non-restricted connection) to download.

[quote user="mikew67"]I don't believe I've done a recent manual installation of the SDK. I did however do a separate manual installation of the Zephyr system in order to create a testbed for working out some of my device tree and Kconfig issues without nRF SDK complications. That installation seems to work OK, and have the recommended directory structure.[/quote]

There are 3 installations. Make sure to use the correct one in e.g. VS Code and SES, i.e. /opt/nordic/ncs/v1.9.1/

[quote user="mikew67"]As an additional, possibly useful bit of information, here are the environment variables that are defined when I "Open Terminal" from with Toolchain Mgr (and I presume are active when I start SES from there as well).[/quote]

Yes, this looks correct as per my last comment above. When opening SES from the Toolchain Manager (as long as you actually have the Open SES button) it should inherit the same settings.

Kind regards,
Øyvind

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Mike Wirth — Fri, 18 Mar 2022 05:41:03 GMT

Hi, Øyvind,

I'll try to respond directly to your questions.

Here's the support info generated by the nRF Connect plugin in VSCode:

IMPORTANT: The data below could contain sensitive or confidential information about your environment.
If you do not wish this to be seen by others, please make sure to remove it before sharing.

For help and support, visit the Nordic DevZone at https://devzone.nordicsemi.com/.

{
  "platform": {
    "os": "darwin",
    "osVersion": "Darwin Kernel Version 21.4.0: Mon Feb 21 20:34:37 PST 2022; root:xnu-8020.101.4~2/RELEASE_X86_64",
    "osKernel": "21.4.0",
    "vscode": "1.65.2",
    "electron": "13.5.2",
    "node": "v14.16.0"
  },
  "system": {
    "date": "2022-03-18T04:44:28.975Z",
    "vscodeRoot": "/Applications/Visual Studio Code.app/Contents/Resources/app",
    "nrfConnectForDesktopInstalled": true,
    "vscodeUptime": "00:01:15",
    "osUptime": "31:13:56",
    "cpu": {
      "model": "Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz",
      "speed": "2700 MHz",
      "count": 4
    },
    "memory": {
      "total": "8.00 GB",
      "free": "0.02 GB"
    }
  },
  "workspace": {
    "name": "Untitled (Workspace)",
    "workspaceFile": "1647316357859",
    "folders": [
      "/opt/nordic/ncs/v1.9.1/nrf/samples/bluetooth/nrf_dm",
      "/Volumes/Archive2/foo/nrf_led_matrix"
    ]
  },
  "extensions": {
    "internal": {
      "nordic-semiconductor.nrf-connect": {
        "version": "2022.3.104",
        "path": "/Users/mike/.vscode/extensions/nordic-semiconductor.nrf-connect-2022.3.104",
        "isActive": true
      },
      "nordic-semiconductor.nrf-terminal": {
        "version": "2022.3.16",
        "path": "/Users/mike/.vscode/extensions/nordic-semiconductor.nrf-terminal-2022.3.16",
        "isActive": true
      },
      "nordic-semiconductor.devicetree": null,
      "nordic-semiconductor.kconfig": null
    },
    "external": {
      "marus25.cortex-debug": "1.2.2",
      "ms-vscode.cpptools": "1.8.4",
      "ms-vscode.js-debug": "1.65.0",
      "ms-vscode.js-debug-companion": "1.0.15",
      "ms-vscode.references-view": "0.0.85",
      "ms-vscode.vscode-js-profile-table": "0.0.18",
      "trond-snekvik.gnu-mapfiles": "1.1.0",
      "twxs.cmake": "0.0.17"
    }
  },
  "tools": {
    "/Applications/SEGGER/JLink/JLinkExe": "7.62a",
    "/usr/local/bin/nrfjprog": "10.15.3",
    "nrfutil": "Not found",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/cmake": "3.21.1",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/west": "0.12.0",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/python3": "3.9.6",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/ninja": "1.10.2",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/gperf": "3.1",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/dtc": "1.6.1",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/arm-none-eabi-gcc": "9-2019-q4-major",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/gn": "1977",
    "/opt/nordic/ncs/v1.9.1/toolchain/bin/git": "2.32.0"
  },
  "sdks": [
    {
      "version": "1.9.1",
      "path": "/Users/mike/ncs"
    },
    {
      "version": "Zephyr 3.0.99",
      "path": "/Users/mike/zephyrproject"
    },
    {
      "version": "1.9.1",
      "path": "/opt/nordic/ncs/v1.9.1"
    }
  ],
  "toolchains": [
    {
      "version": "1.9.1",
      "path": "/opt/nordic/ncs/v1.9.1/toolchain"
    }
  ],
  "connectedDevices": [],
  "deviceProviders": [
    "nrfjprog"
  ],
  "config": {
    "nordic-semiconductor.nrf-connect": {
      "topdir": "${nrf-connect.sdk:1.9.1}",
      "toolchain": {
        "path": "${nrf-connect.toolchain:1.9.1}"
      },
      "ozonePath": "",
      "applications": [
        "${workspaceFolder}",
        "/Volumes/Archive2/foo/nrf_led_matrix"
      ],
      "kconfig": {
        "interface": "kconfig"
      },
      "welcome": {
        "showOnStartup": true
      },
      "west": {
        "env": {
          "$base": "terminal"
        }
      },
      "boardRoots": [],
      "enableTelemetry": true
    },
    "nordic-semiconductor.nrf-terminal": {
      "terminalMode": "character"
    },
    "nordic-semiconductor.devicetree": {
      "modules": [
        "${zephyrBase}",
        "${zephyrBase}/../nrf",
        "."
      ],
      "zephyr": "",
      "ctxFile": "",
      "defaultBoard": ""
    },
    "nordic-semiconductor.kconfig": {
      "root": "",
      "env": {},
      "cfiles": true,
      "disable": false,
      "zephyr": {
        "base": ""
      },
      "python": "",
      "liveValue": true
    },
    "marus25.cortex-debug": {
      "armToolchainPath": null,
      "armToolchainPrefix": "arm-none-eabi",
      "gdbPath": null,
      "objdumpPath": null,
      "JLinkGDBServerPath": null,
      "openocdPath": null,
      "pyocdPath": null,
      "PEGDBServerPath": null,
      "stutilPath": null,
      "stlinkPath": null,
      "stm32cubeprogrammer": null,
      "enableTelemetry": true,
      "flattenAnonymous": false,
      "registerUseNaturalFormat": true,
      "variableUseNaturalFormat": true,
      "dbgServerLogfile": null,
      "showDevDebugOutput": "none"
    }
  },
  "environment": {
    "westExe": "/opt/nordic/ncs/v1.9.1/toolchain/bin/west",
    "westEnv": {
      "ELECTRON_RUN_AS_NODE": "1",
      "GIT_EXEC_PATH": "/opt/nordic/ncs/v1.9.1/toolchain/Cellar/git/2.32.0_1/libexec/git-core",
      "HOME": "/Users/mike",
      "PATH": "/opt/nordic/ncs/v1.9.1/toolchain/bin:/Users/mike/.asdf/shims:/usr/local/Cellar/asdf/0.9.0/libexec/bin:/usr/local/sbin:/usr/local/opt/ccache/libexec:/Users/mike/Projects/moddable/build/bin/mac/release:/Library/Frameworks/Python.framework/Versions/3.6/bin:/Library/Frameworks/Python.framework/Versions/3.9/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/Library/Apple/usr/bin:/Applications/Wireshark.app/Contents/MacOS:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/Users/mike/gn",
      "ZEPHYR_BASE": "/opt/nordic/ncs/v1.9.1/zephyr",
      "GNUARMEMB_TOOLCHAIN_PATH": "/opt/nordic/ncs/v1.9.1/toolchain",
      "ZEPHYR_TOOLCHAIN_VARIANT": "gnuarmemb",
      "USER": "mike"
    },
    "toolchainPath": "/opt/nordic/ncs/v1.9.1/toolchain",
    "toolchainBinPath": "/opt/nordic/ncs/v1.9.1/toolchain/bin",
    "toolchainVersion": "1.9.1"
  },
  "terminal": {
    "shell": null,
    "defaultProfile": null
  }
}

There are a couple curious items in this output. I'll note them below.

I have automatically installed, removed and repeated this sequence several times with SDK v1.9.1. The resulting Toolchain Manager window below shows that the final configuration Is broken in at least one way -- the Open SES button is missing.

Here's the directory structure for the installed SDK. Appears correct at this level of detail:

I don't believe I've done a recent manual installation of the SDK. I did however do a separate manual installation of the Zephyr system in order to create a testbed for working out some of my device tree and Kconfig issues without nRF SDK complications. That installation seems to work OK, and have the recommended directory structure.

As an additional, possibly useful bit of information, here are the environment variables that are defined when I "Open Terminal" from with Toolchain Mgr (and I presume are active when I start SES from there as well).

Last login: Thu Mar 17 22:30:21 on ttys000
cd /opt/nordic/ncs/v1.9.1 ; export PATH=/opt/nordic/ncs/v1.9.1/toolchain/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin ; export GIT_EXEC_PATH=/opt/nordic/ncs/v1.9.1/toolchain/Cellar/git/2.32.0_1/libexec/git-core ; export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb ; export GNUARMEMB_TOOLCHAIN_PATH=/opt/nordic/ncs/v1.9.1/toolchain ; clear
mike@Mikes-MBP-101 ~ % cd /opt/nordic/ncs/v1.9.1 ; export PATH=/opt/nordic/ncs/v1.9.1/toolchain/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin ; export GIT_EXEC_PATH=/opt/nordic/ncs/v1.9.1/toolchain/Cellar/git/2.32.0_1/libexec/git-core ; export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb ; export GNUARMEMB_TOOLCHAIN_PATH=/opt/nordic/ncs/v1.9.1/toolchain ; clear


mike@Mikes-MBP-101 v1.9.1 % printenv
TERM_SESSION_ID=A80CBA4F-62CD-47AB-B1F1-B2E6B6C76F43
__CFBundleIdentifier=com.apple.Terminal
TMPDIR=/var/folders/hp/_vddx6wx4ws6n5wsbb8793l80000gn/T/
XPC_FLAGS=0x0
TERM=xterm-256color
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.J2qSN75xT9/Listeners
XPC_SERVICE_NAME=0
TERM_PROGRAM=Apple_Terminal
TERM_PROGRAM_VERSION=444
SHLVL=2
PWD=/opt/nordic/ncs/v1.9.1
ORIGINAL_XDG_CURRENT_DESKTOP=undefined
SHELL=/bin/zsh
HOME=/Users/mike
LOGNAME=mike
USER=mike
PATH=/opt/nordic/ncs/v1.9.1/toolchain/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
OLDPWD=/Users/mike
ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
GNUARMEMB_TOOLCHAIN_PATH=/opt/nordic/ncs/v1.9.1/toolchain
ZPROFILETEST=was run
MODDABLE=/Users/mike/Projects/moddable
IDF_PYTHON_ENV_PATH=/Users/mike/.espressif/python_env/idf4.4_py3.10_env
PIP_REQUIRE_VIRTUALENV=false
ASDF_DIR=/usr/local/Cellar/asdf/0.9.0/libexec
ZSHRCTEST=was run
GIT_EXEC_PATH=/opt/nordic/ncs/v1.9.1/toolchain/Cellar/git/2.32.0_1/libexec/git-core
LANG=en_US.UTF-8
_=/usr/bin/printenv
mike@Mikes-MBP-101 v1.9.1 %

You said: "It should also be sufficient to delete the folder where you installed the environment." Not in my experience After removing and reinstalling the SDK, old project info still persists in SES.

Hope all this info helps,

Mike

RE: How to FULLY UNINSTALL nRF Connect SDK and SES on macOS?

Øyvind — Thu, 17 Mar 2022 09:49:52 GMT

Hello,

I'm really sorry to hear that you are facing these issues. Please note that the kconfig and device tree issues are not the same as SES and VS code issues.

Using VS Code extension, can you please go to your command palette (Cmd + Shift + P.) and run the following nRF Connect: Generate Support Information. This should provide an output in the Output of VS Code. Please copy and paste here.

How did you install the nRF Connect SDK? Manually or Automatically? If you have used the Toolchain Manager you should be able to remove the SDK using the dropdown menu

It should also be sufficient to delete the folder where you installed the environment.

Kind regards,
Øyvind