Visual Studio Code discovers wrong gnuarmemb folder – Nordic Q&A – Nordic DevZone

I’m using Linux 20.04.  I have been following the manual installation guide for setting up the nRF Connect SDK and also nRF Toolchain

in my .bashrc file: 

export PATH=${HOME}/gn:”$PATH”
export PATH=$PATH:$GNUARMEMB_TOOLCHAIN_PATH/bin

in my .zephyrrc 

export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
export GNUARMEMB_TOOLCHAIN_PATH=”~/gnuarmemb/gcc-arm-none-eabi-10.3-2021.10″
export PATH=$PATH:$GNUARMEMB_TOOLCHAIN_PATH/bin

Then i run source zephyr/zephyr-env.sh in my ncs folder. 

Then I opened VS Code from WITHIN the same terminal, this way VS Code is able to see these environmental variables. In the Quick Setup page I just set the nRF Connect SDK parameter to my *ncs* folder, and set nRF Connect Toolchain to PATH. This ‘Invalid Toolchain Installation’ message appears and detects an older version of gnuarmemb  ( the one installed for previous SDK from nordic). 

whereis arm-none-eabi-gcc
...../gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc

If i go to the sample folders, I’m able to build properly using the west tool on terminal using: west build -b nrf9160dk_nrf9160ns –pristine

What else could i do to fix this? 

Read more here: Source link