After installing SDK 2.7 I am unable to get nRF Connect SDK to function in VS Code.

[Thomas]

After I installed nRF Connect SDK 2.7 and tried to run the pre-release version of VS Code extension, I am now compleatly unable to make nRF Connect for VS Code function. 

When using the menu to select toolchains, I get nothing to select installed SDK or toolchain. I see an error dispolayed by VS Code "command 'nrf-connect.mangeWestWorkspace' not found" or "command 'nrf-connect.mangeToolchains' not found".

I have uninstalled everything two times (both VS Code extensions (all) and the SDK and reinstalled again. One time from within VS Code extension and one time through the nRF Connect for Desktop Toolchain Manager.

None of the reinstallation have brought my installation back to a functional state.

I am sure it is a simple thing, but I do not know where to look....

[Menon]

Hello,

Usually, it doesn't take much time (less than 1 minute) to generate support information. Can you try using View --> Command Palette --> Generate Support Information (see my screenshot below)? If that doesn't work, open the developer tools, look at the console, and share the output here. A screenshot would be helpful.

Kind Regards,

Abhijith

[Thomas]

Well I killed it again. From within VS Code I selected to install toolchain and SDK version v2.7.0.

I created a new application from a sample, was able to build a prestine build. But then trying to flash to my DK board, I get an error. I think my problems started the same way earlier. When trying to flash the newly successfully build application i get:

west flash: using runner nrfjprog
runners.nrfjprog: reset after flashing requested
runners.nrfjprog: Flashing file: d:\Workspaces\pmi8004i\build_1\zephyr\merged.hex
[error] [ Client] - Encountered error -102: Command read_device_info executed for 142 milliseconds with result -102
[error] [ Worker] - An unknown error.
[error] [ Client] - Encountered error -102: Command read_memory_descriptors executed for 31 milliseconds with result -102
Failed to read device memories.

[error] [ Worker] - An unknown error.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 33: nrfjprog --program 'd:\Workspaces\pmi8004i\build_1\zephyr\merged.hex' --sectorerase --verify -f NRF91 --snr 960090542

The terminal process terminated with exit code: 33.
Terminal will be reused by tasks, press any key to close it.

And unfortunately after goiing back to 2.6.1 the problem persists.