This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF Connect for VS Code (Windows) - missing west

Hi,

I've installed VS Code 162.3 on Windows 10 machine via Toolchain Manager. I've also installed nRF Connect extensions for SDK v1.7.1.
The build system works under NCS v1.7.1, but if I open a PS terminal "west --version" is not recognized as a valid command.
Isn't VS Code using west for building ?
How to get west installed ? 
Another miss is the "Debug with Ozone" icon under ACTIONS pane.

Thankx
 

Parents
  • Hi,

    When you install the toolchain using the toolchain manager the tools are not in the path (which is intentional to keep things separated). However, you can for instance open a terminal window with this in the path from the Toolchain Manger like this:

  • I see.

    If I run the power shell by right-click over the application icon, west is recognized.


    If I run the power shell by clicking the "+" button in the terminal window, west is not in scope.


    This is funny.

    As for Ozone, I needed to download and install it.
    Unfortunately I do not have the plugin file for Zephyr awareness ("ZephyrPlugin_CM4.js").
    Without this file I cannot watch the threads.

    BR

Reply
  • I see.

    If I run the power shell by right-click over the application icon, west is recognized.


    If I run the power shell by clicking the "+" button in the terminal window, west is not in scope.


    This is funny.

    As for Ozone, I needed to download and install it.
    Unfortunately I do not have the plugin file for Zephyr awareness ("ZephyrPlugin_CM4.js").
    Without this file I cannot watch the threads.

    BR

Children
  • Hi,

    Gabriele said:
    This is funny.

    Perhaps, but it is expected. In the first case, you use the specified NCS toolchain environment. in the seconds, you use your normal environment (whatever is in the path).

    I forgot to comment about Ozone. You need to open the VS Code settings and specify the path to the Ozone executable. In the same way, you need to specify the path to the plugin for Zephyr thread awareness. This is part of the SEGGER J-Link installation, and you should find it under /path/to/jlink/GDBServer/. Specify the full path to the file.

  • I've installed newest SEGGER J-Link v7.58d.
    Issuing the specific command in Ozone does not enable any Zephyr specific view or window.

  • Hi,

    I am lacking context here as. Can you explain what you are doing with Ozone here and what you ant? Also,  please make separate questions for separate topics in the future.

  • Can you explain what you are doing with Ozone here and what you ant?

    Sorry Einar, I took for granted you know. I'm trying to enable the so called RTOS-awareness feature in Ozone, as shown in the Nordic produced VS Code debugging video tutorial (link)

  • Hi,

    I was reading these earlier questions in VS Code context, and my previous answer about Zephyr thread awareness was about adding it for debugging in VS Code.

    In Ozone version >= 3.26 you use the following command to make it Zephyr thread aware:

    Project.SetOSPlugin("ZephyrPlugin");

    For older versions you should use:

    Project.SetOSPlugin("ZephyrPlugin_CM4");

Related