fix broken nRF Connect extension in VSCode

This should be a simple answer. I had the nordic extension loaded on my dev machine for a while.. I have since deleted manually a few SDK (2.7 and the like) . I attempted to pull up the system after a long time of not being used and it is confused.

There are incomplete references to the SDK and none of my projects will load properly.
Fine I broke something..

Uninstalling and reinstalling doesn't fix it. I am guessing there are some ghosts in the machine (a cache of data someplace) that has me all screwed up.

My question is , what should I remove, to clean the broken nrfsDK out of VSCode so I an re-install and get it back to working order? 
I imagine there are hidden folders in C:\Users\<user>\  like .nrfutil and things. Also there are pieces in .vscode that probably should be removed.
Perhaps folders in C:\Users\<used>\AppDate needs parts removed.

I am hoping there are no registry entries, that seems to be weird to use those these days.

Any help?

T

Parents
  • Hello,

    Yes, we are aware of this issue, and working on replicating it. I am sorry for the inconvenience.

    Unfortunately, we have not been able to successfully reproduce this. If any of you would be able to try a custom version of the tool with more debug output, and are able to reproduce the issue using this version, we'd be happy to see what the log output would be in that case. If so, please see the description from my reply 13th of March in this ticket:

    https://devzone.nordicsemi.com/support-private/support/358031#permalink=1136667

    Best regards,

    Edvin

  • I am not sure exactly where the break occurred. I had manually removed some versions of the SDK and the toolchains, even going through the toolchains.json and manually removing the toolchains I removed.

    At some point I attempted to pull up a project I had worked many times before however, that was many months ago. It didn't come up properly; the build would fail because it couldn't find tools, the PATH was incorrect.

    I attempted to remove the extension. And re-installed... same behavior. Tried creating a new project only for the software to not recognize where the samples were and it was listing SDKS with the
    "nRF Connect SDK ??? C:\Users\<user>\ncs\v2.9.1"

    I then tried uninstalling and removing anything under .vscode\extensions\ that had "nordic-semiconductor" in the name. I also deleted a .nfrutil directory as well. 

    Re-installing didn't fix anything. Tried the same again and deleted anything Nordic like under C:\Users\<user>\Appdata.  After a few useless attempts, I wrote to the forum here, trying to see if there were other places in the code where the "ghost of nordic tools past" was residing.

    Then Turbo J added the downgrade note, which I executed, and then everything started working. 

    There must be something hidden, perhaps in the VSCode settings and maybe something having to do with "Profiles" in VSCode.

    I suppose there might have been something in the upgrade path taken. Maybe the old version of the extension I was using months ago broke when moving to the latest. I might be going from the prior version to the current works fine but jumping from a much older version to the current looses something.

    Tony

Reply
  • I am not sure exactly where the break occurred. I had manually removed some versions of the SDK and the toolchains, even going through the toolchains.json and manually removing the toolchains I removed.

    At some point I attempted to pull up a project I had worked many times before however, that was many months ago. It didn't come up properly; the build would fail because it couldn't find tools, the PATH was incorrect.

    I attempted to remove the extension. And re-installed... same behavior. Tried creating a new project only for the software to not recognize where the samples were and it was listing SDKS with the
    "nRF Connect SDK ??? C:\Users\<user>\ncs\v2.9.1"

    I then tried uninstalling and removing anything under .vscode\extensions\ that had "nordic-semiconductor" in the name. I also deleted a .nfrutil directory as well. 

    Re-installing didn't fix anything. Tried the same again and deleted anything Nordic like under C:\Users\<user>\Appdata.  After a few useless attempts, I wrote to the forum here, trying to see if there were other places in the code where the "ghost of nordic tools past" was residing.

    Then Turbo J added the downgrade note, which I executed, and then everything started working. 

    There must be something hidden, perhaps in the VSCode settings and maybe something having to do with "Profiles" in VSCode.

    I suppose there might have been something in the upgrade path taken. Maybe the old version of the extension I was using months ago broke when moving to the latest. I might be going from the prior version to the current works fine but jumping from a much older version to the current looses something.

    Tony

Children
No Data
Related