Hi all,
Even though I have v2.1.0 nRF Connect SDK installed onto my machine, it looks like VSCode continues to build with V1.9.1 . How can I point VSCode to compile/build with V2.1.0?
Hi all,
Even though I have v2.1.0 nRF Connect SDK installed onto my machine, it looks like VSCode continues to build with V1.9.1 . How can I point VSCode to compile/build with V2.1.0?
cchoi22915 how did you install your SDK? Depending on how you organized your project, you should be able to update your project’s west.yml
to point towards the newer version of NCS. If you’re running my specific plugin you can then run the `Update Dependencies’ command which should get you to 2.1.0.
I used the toolchain manager in the nRF Connect for Desktop application (Windows)
running the “Update Dependencies” command gives the following
=== updating nrf (nrf):
HEAD is now at d29f1ddec ncs: v1.7.0
=== updating zephyr (zephyr):
HEAD is now at f19ebe4b50 [nrf fromlist] boards: rename thingy53_nrf5340_cpuappns
=== updating mcuboot (bootloader/mcuboot):
HEAD is now at b514a319 [nrf fromlist] boot_serial: Increase BOOT_SERIAL_OUT_MAX
=== updating nrfxlib (nrfxlib):
HEAD is now at a79fdc3d doc: update changelogs for NCS 1.7.0
. . .
edit: able to update and point to the right app and v2.1.0 using West and “Welcome to nRF Connect” -> “Add an existing application”.
This led to a errors:
`app/boards/circuitdojo_feather_nrf9160_ns.conf:10: warning: attempt to assign the value ‘y’ to the undefined symbol PM_EXTERNAL_FLASH’
‘app/boards/circuitdojo_feather_nrf9160_ns.conf:11: warning: attempt to assign the value ’“W25Q32JV”‘ to the undefined symbol PM_EXTERNAL_FLASH_DEV_NAME’
’app/boards/circuitdojo_feather_nrf9160_ns.conf:13: warning: attempt to assign the value ‘0×400000’ to the undefined symbol PM_EXTERNAL_FLASH_SIZE `
After commenting as I do not need the flash
# # External flash partition defintion
/# CONFIG_PM_EXTERNAL_FLASH=y
/# CONFIG_PM_EXTERNAL_FLASH_DEV_NAME="W25Q32JV"
/# CONFIG_PM_EXTERNAL_FLASH_BASE=0x0
/# CONFIG_PM_EXTERNAL_FLASH_SIZE=0x400000
I was not able to build successfully as it broke a lot of things such as:
app/src/main.c: In function 'cert_provision':
C:/Users/Chris/OneDrive/Copper/cube_nRF9160/app/src/main.c:1529:8: error: too many arguments to function 'modem_key_mgmt_exists'
1529 | err = modem_key_mgmt_exists(TLS_SEC_TAG, MODEM_KEY_MGMT_CRED_TYPE_CA_CHAIN, &exists, &unused);
app/build/zephyr/include/generated/devicetree_unfixed.h:1778:46: error: 'DT_N_S_soc_S_peripheral_40000000_S_gpio_842500_P_label' undeclared (first use in this function); did you mean 'DT_N_S_soc_S_peripheral_40000000_S_gpio_842500_P_reg'?
1778 | #define DT_N_S_leds_S_led_0_P_gpios_IDX_0_PH DT_N_S_soc_S_peripheral_40000000_S_gpio_842500
app/build/zephyr/include/generated/devicetree_unfixed.h:1778:46: error: 'DT_N_S_soc_S_peripheral_40000000_S_gpio_842500_P_label' undeclared (first use in this function); did you mean 'DT_N_S_soc_S_peripheral_40000000_S_gpio_842500_P_reg'?
1778 | #define DT_N_S_leds_S_led_0_P_gpios_IDX_0_PH DT_N_S_soc_S_peripheral_40000000_S_gpio_842500
Seems like more of a question for Nordic. I don’t use their plugin or SDK provisioning tools. The Circuit Dojo Zephyr Tools is not meant to work together with other vscode plugins.
Also, I know that the config variables you mentioned (CONFIG_PM_EXTERNAL_FLASH
) are deprecated/removed in newer versions of NCS.