Cannot install newer SDK with nRF Connect or VS Code on macOS

Task: trying to install nRF SDK v2.7.0 on an M3 Pro Macbook Pro.

Methods attempted:

  1. Install via nRF extension in VS Code. It will let me select which SDK to install and appears to silently fail - the SDK is not available for selection even after multiple attempts to install it.
  2. Install via Toolchain Manager v1.5.1 - various errors are shown (listed below). Only a "First steps" (even though the SDK is not installed), "Open VS Code", and dropdown buttons are shown. 

Results:

  1. in VS Code - no new SDKs are ever shown for usage. No error popups or indication of failure.
  2. in nRF Connect (Toolchain Manager) -
    1. The "Open VS Code" button opens VS Code, the app asks for permission to open "/opt/nordic/ncs/v2.7.0/", then another popup opens with "

      The path '/opt/nordic/ncs/v2.7.0' does not exist on this computer."

    2. "Open Terminal" does nothing.
    3. "Open SDK directory" does nothing.
    4. "Open toolchain directory" does nothing.
    5. "Update SDK" opens a popup with "Failed to clone the repositories: Error: EACCES: permission denied, mkdir '/opt/nordic/ncs/v2.7.0'".
    6. "Update Toolchain" flashes a line on that GUI item for the version and then does nothing.
    7. "Remove" asks "Are you sure you want to remove v2.7.0 environment?" then when confirmed, reports "Failed to remove /opt/nordic/ncs/v2.7.0, no such file or directory. Please close any application or window that might keep this environment locked, then try to remove it again." despite no other apps using or accessing that directory.
Parents Reply Children
  • Yes, I am and have tried that, but this was not the issue. Somehow that directory became chowned to another user, and as far I as I know I never personally did that. I'm reasonably experienced with sudo and use it as minimally as possible, and only if I understand the outcome, and I would not have run a command to change that. Changing it back does require sudo.

    So I'm not sure how that happened but with all the recent weirdness of some of the nRF software recently I wouldn't be too surprised if some weird bug came up somehow.

Related