nRF Extension on VScode doesn't doesn't bring compiler errors to PROBLEMS tab

Hi, 

Why nRF Extension on VScode doesn't doesn't bring compiler errors to PROBLEMS tab? The issue appears few days ago, reinstalling of extension and vscode at all doesn't help.

PROBLEMS tab imports some issues on IntelliSense output ("online") but doesn't import compiler output as it should. 

Used nCS 2.0.0, toolchain manager was updated to ver. 1.1.3 , nRF Extension was re-installed today.

Parents
  • I had the same experience when i migrate from segger embedded studio to vscode
    not sure what helped me, try several things that day (also removing all nrf + vscode and re-installing the tools)
    but i also looked at all the settings of nordic  and  settings in vscode.

    Here just some hints & tips:

    Did you open vscode from  nRF Connect for desktop or directly from your O.S. ?
    - The correct way is from nRF Connect for desktop.

    - does you project build?  output in the terminal tab/pane?
    - is the compiler path settings correct? see File -> preferences -> Settings -> compilerpath
    - is the intellisense path settings correct? see File -> preferences -> Settings ->  IntellisenseMode
    - is the compiler selection OK in the vscode, File -> preferences -> Settings -> toolchain  (multiple settings)







  • Hi, 

    yep, 

    1. Running from nRF connect desktop / toolchain manager doesn't help

    2. Compiler path is set to default (empty). 

    3. IntellisenseMode is set to gcc-arm (as from installation)

    4. Toolchain property for nRF Extension is '${nrf-connect.toolchain:2.0.0}'

Reply Children
Related