• State Not Answered
  • Replies 2 replies
  • Subscribers 24 subscribers
  • Views 98 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 290294
Options

Visual Studio Code nRF Connect SDK improvements

user94606

Hello !

I'm currently discovering the VS code extension for nRF Connect SDK and I whish to give some feedbacks of missing / odd features. I hope this is the best place !

I am used to work with Segger Embedded Studio when developing with nordic. So this is basically a "missing features overview" regarding SES.

1) With VS Code, there is no "Code Outline". In fact there is something similar with VS Code "Ctrl + Shift + O" but this is really less clear.

2) When bulding / Flashing, it is never clear if you "rebuild all" or just "build". Same for flashing : you do not have the choice to rebuild or not direclty.

3) When using "Debug" feature (step by step). Every time I lauch a new session, I receive an error message that gdb has failed... But in fact it succeeds ^^

4) Error and warning are strangely erased : I am never sure if messages come from last build or current build

5) Naviguating in files is a mess : when I use "Ctrl + click" on a function or variable, I drop in the correct file but sometimes not to the correct line at all ! Moreover with SES you can "find in files" even for files of the nRF Connect SDK. This does not seem to work the same way with Visual Studio Code.

6) Creating a new project from sample with west workspaces does not work for me : it always fail on one of the repository. And after this point, the VS Code extension just give up.

7) I do not understand why nordic is pushing the community so hard on VS Code while it is obivously less clear and misses features that are already here with SES (even if it is not perfect).

I guess some of these points are a misunderstanding of VS Code or the extension but I hope these are useful feedbacks ! Smiley

Best regards !

Parents
  • 0

    Hi, 

    From the team:

    1. There's an outline available at the bottom of the explorer sidebar. You can also press the "bread crumbs" at the top (the file path > symbol name row right between the tab list and the editor
    2. VS Code will always run a normal "build" unless the user explicitly requests otherwise - OR if the build system deems it necessary because of changes that affect CMake. See http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/develop/application/index.html#rebuilding-an-application
    3. That is odd, we'll check whether we can reproduce this.
    4. I think I would need some more info to understand what's going wrong here. There are several sources of errors - live editing error checking for the different languages as well as the build itself. When do errors appear and disappear? Is it related to editing, or building, or neither? Is it limited to specific languages, or does it happen in any file?
    5. Unfortunately, we rely on Microsoft's solution for Go To Symbol in C files, which has been a bit spotty for us too. In Kconfig and DeviceTree, we're expecting this to work as it should, but we'd be interested in hearing about it if the problem occurs in those files too. In VS Code, you can only search in files that are part of the VS Code workspace. I'd recommend using "nRF Connect: Add nRF Connect SDK to workspace" to create a multi root workspace. Now, the search button in the source files in the sidebar works for the SDK as well.
    6. We'll look into this. Any details on which repo fails would be appreciated.

    We highly appreciate feedback like this. There are still parts of the user experience that was clearer with Segger Embedded Studio, but we rely on users telling us what works and what doesn't, as our own internal usability testing can't uncover all workflows and configurations.

    -Amanda

Reply
  • 0

    Hi, 

    From the team:

    1. There's an outline available at the bottom of the explorer sidebar. You can also press the "bread crumbs" at the top (the file path > symbol name row right between the tab list and the editor
    2. VS Code will always run a normal "build" unless the user explicitly requests otherwise - OR if the build system deems it necessary because of changes that affect CMake. See http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/develop/application/index.html#rebuilding-an-application
    3. That is odd, we'll check whether we can reproduce this.
    4. I think I would need some more info to understand what's going wrong here. There are several sources of errors - live editing error checking for the different languages as well as the build itself. When do errors appear and disappear? Is it related to editing, or building, or neither? Is it limited to specific languages, or does it happen in any file?
    5. Unfortunately, we rely on Microsoft's solution for Go To Symbol in C files, which has been a bit spotty for us too. In Kconfig and DeviceTree, we're expecting this to work as it should, but we'd be interested in hearing about it if the problem occurs in those files too. In VS Code, you can only search in files that are part of the VS Code workspace. I'd recommend using "nRF Connect: Add nRF Connect SDK to workspace" to create a multi root workspace. Now, the search button in the source files in the sidebar works for the SDK as well.
    6. We'll look into this. Any details on which repo fails would be appreciated.

    We highly appreciate feedback like this. There are still parts of the user experience that was clearer with Segger Embedded Studio, but we rely on users telling us what works and what doesn't, as our own internal usability testing can't uncover all workflows and configurations.

    -Amanda

Children
No Data
Related
Terms of service