My VS Code NRF extension cannot build an application and it cannot also detect my device

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Simonr — Wed, 22 Nov 2023 11:14:56 GMT

You can change the nrf-connect.device provider from the VS Code settings page as Abhijith suggested by changing the provider from nRF Util to nrfjprog. The documentation explaining it is found here. What version of nrfutil are you running in your application?

Best regards,

Simon

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Fri, 17 Nov 2023 13:41:36 GMT

Hello I think the issue is with nrfutil. How can I change "nrf-connect.deviceProvider" configuration value to "nrfjprog"

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Menon — Wed, 25 Oct 2023 09:22:09 GMT

Hello,

Since you are able to find the device inside nrfjprog, I guess there is some issue with the vscode extension, as the extension uses nrfutil as a device backend. As a workaround, you can change the "nrf-connect.deviceProvider" configuration value to "nrfjprog", and then the devices should show up.

Please see this page for instructions.

Could you also try running "nrfutil device list" in the command line and see if that picks up the devices? This will help to figure out whether the issue lies in nrfutil or in the vscode extension.

Kind Regards,

Abhijith

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Fri, 20 Oct 2023 10:51:35 GMT

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Menon — Fri, 20 Oct 2023 05:58:55 GMT

Hello,

I am not sure if this is a nRF-connect VSCode extension issue. Whether you are able to detect your device from the command prompt Try running the command nrfjprog --deviceversion and see whether your device is getting detected there (please share a screenshot of the same).

Kind Regards,

Abhijith

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Wed, 18 Oct 2023 13:25:53 GMT

Hello I was able to use a sample application and create a build configuration but my device does not appear in the connected devices view, my j-link commander, and my nrf programmer can detect the device but vscode does not

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Menon — Sat, 14 Oct 2023 02:43:06 GMT

Hello,

Were you able to solve your initial problem? Can you see your device inside the VScode? Could you share a screenshot of the interface you are working with? Where are you able to locate all the files after installing the SDK? I am asking this to make sure that you have a proper installation of sdk. Please see the below screenshot and make sure you also have all the files inside the SDK (ncs/2.4.2):

Kind Regards,

Abhijith

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Thu, 12 Oct 2023 12:56:28 GMT

When I tried to create a new application on vscode I did not get the option copy from sample

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Thu, 12 Oct 2023 12:54:18 GMT

I tried to build an application the at_client on the command prompt but got an error

C:\ncs\v2.4.2\nrf\samples\nrf9160\at_client>west build -b nrf9160dk_nrf9160
[2/56] Building C object modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/nrf_modem_os.c.obj
FAILED: modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/nrf_modem_os.c.obj
C:\ncs\toolchains\31f4403e35\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -DKERNEL -DNRF9160_XXAA -DNRF_SKIP_FICR_NS_COPY_TO_RAM -DUSE_PARTITION_MANAGER=0 -D_ANSI_SOURCE -D_FORTIFY_SOURCE=1 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -IC:/ncs/v2.4.2/zephyr/include -Izephyr/include/generated -IC:/ncs/v2.4.2/zephyr/soc/arm/nordic_nrf/nrf91 -IC:/ncs/v2.4.2/zephyr/lib/libc/newlib/include -IC:/ncs/v2.4.2/zephyr/soc/arm/nordic_nrf/common/. -IC:/ncs/v2.4.2/zephyr/subsys/net/lib/sockets/. -I../../../../include -I../../../../tests/include -IC:/ncs/v2.4.2/modules/hal/cmsis/CMSIS/Core/Include -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx/drivers/include -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx/mdk -IC:/ncs/v2.4.2/zephyr/modules/hal_nordic/nrfx/. -IC:/ncs/v2.4.2/nrfxlib/nrf_modem/include -isystem C:/ncs/v2.4.2/nrfxlib/crypto/nrf_cc310_platform/include -fno-strict-aliasing -Os -imacros C:/ncs/v2.4.2/nrf/samples/nrf9160/at_client/build/zephyr/include/generated/autoconf.h -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m33 -mthumb -mabi=aapcs --sysroot=C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi -imacros C:/ncs/v2.4.2/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=C:/ncs/v2.4.2/nrf/samples/nrf9160/at_client=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/ncs/v2.4.2/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/ncs/v2.4.2=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=c99 -MD -MT modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/nrf_modem_os.c.obj -MF modules\nrf\lib\nrf_modem_lib\CMakeFiles\..__nrf__lib__nrf_modem_lib.dir\nrf_modem_os.c.obj.d -o modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/nrf_modem_os.c.obj -c C:/ncs/v2.4.2/nrf/lib/nrf_modem_lib/nrf_modem_os.c
C:/ncs/v2.4.2/nrf/lib/nrf_modem_lib/nrf_modem_os.c:16:10: fatal error: pm_config.h: No such file or directory
   16 | #include <pm_config.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
[3/56] Building C object modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/nrf_modem_lib.c.obj
FAILED: modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/nrf_modem_lib.c.obj
C:\ncs\toolchains\31f4403e35\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -DKERNEL -DNRF9160_XXAA -DNRF_SKIP_FICR_NS_COPY_TO_RAM -DUSE_PARTITION_MANAGER=0 -D_ANSI_SOURCE -D_FORTIFY_SOURCE=1 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -IC:/ncs/v2.4.2/zephyr/include -Izephyr/include/generated -IC:/ncs/v2.4.2/zephyr/soc/arm/nordic_nrf/nrf91 -IC:/ncs/v2.4.2/zephyr/lib/libc/newlib/include -IC:/ncs/v2.4.2/zephyr/soc/arm/nordic_nrf/common/. -IC:/ncs/v2.4.2/zephyr/subsys/net/lib/sockets/. -I../../../../include -I../../../../tests/include -IC:/ncs/v2.4.2/modules/hal/cmsis/CMSIS/Core/Include -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx/drivers/include -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx/mdk -IC:/ncs/v2.4.2/zephyr/modules/hal_nordic/nrfx/. -IC:/ncs/v2.4.2/nrfxlib/nrf_modem/include -isystem C:/ncs/v2.4.2/nrfxlib/crypto/nrf_cc310_platform/include -fno-strict-aliasing -Os -imacros C:/ncs/v2.4.2/nrf/samples/nrf9160/at_client/build/zephyr/include/generated/autoconf.h -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m33 -mthumb -mabi=aapcs --sysroot=C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi -imacros C:/ncs/v2.4.2/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=C:/ncs/v2.4.2/nrf/samples/nrf9160/at_client=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/ncs/v2.4.2/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/ncs/v2.4.2=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=c99 -MD -MT modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/nrf_modem_lib.c.obj -MF modules\nrf\lib\nrf_modem_lib\CMakeFiles\..__nrf__lib__nrf_modem_lib.dir\nrf_modem_lib.c.obj.d -o modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/nrf_modem_lib.c.obj -c C:/ncs/v2.4.2/nrf/lib/nrf_modem_lib/nrf_modem_lib.c
C:/ncs/v2.4.2/nrf/lib/nrf_modem_lib/nrf_modem_lib.c:17:10: fatal error: pm_config.h: No such file or directory
   17 | #include <pm_config.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
[5/56] Building C object modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/sanity.c.obj
FAILED: modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/sanity.c.obj
C:\ncs\toolchains\31f4403e35\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -DKERNEL -DNRF9160_XXAA -DNRF_SKIP_FICR_NS_COPY_TO_RAM -DUSE_PARTITION_MANAGER=0 -D_ANSI_SOURCE -D_FORTIFY_SOURCE=1 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -IC:/ncs/v2.4.2/zephyr/include -Izephyr/include/generated -IC:/ncs/v2.4.2/zephyr/soc/arm/nordic_nrf/nrf91 -IC:/ncs/v2.4.2/zephyr/lib/libc/newlib/include -IC:/ncs/v2.4.2/zephyr/soc/arm/nordic_nrf/common/. -IC:/ncs/v2.4.2/zephyr/subsys/net/lib/sockets/. -I../../../../include -I../../../../tests/include -IC:/ncs/v2.4.2/modules/hal/cmsis/CMSIS/Core/Include -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx/drivers/include -IC:/ncs/v2.4.2/modules/hal/nordic/nrfx/mdk -IC:/ncs/v2.4.2/zephyr/modules/hal_nordic/nrfx/. -IC:/ncs/v2.4.2/nrfxlib/nrf_modem/include -isystem C:/ncs/v2.4.2/nrfxlib/crypto/nrf_cc310_platform/include -fno-strict-aliasing -Os -imacros C:/ncs/v2.4.2/nrf/samples/nrf9160/at_client/build/zephyr/include/generated/autoconf.h -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m33 -mthumb -mabi=aapcs --sysroot=C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi -imacros C:/ncs/v2.4.2/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=C:/ncs/v2.4.2/nrf/samples/nrf9160/at_client=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/ncs/v2.4.2/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/ncs/v2.4.2=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=nano.specs -std=c99 -MD -MT modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/sanity.c.obj -MF modules\nrf\lib\nrf_modem_lib\CMakeFiles\..__nrf__lib__nrf_modem_lib.dir\sanity.c.obj.d -o modules/nrf/lib/nrf_modem_lib/CMakeFiles/..__nrf__lib__nrf_modem_lib.dir/sanity.c.obj -c C:/ncs/v2.4.2/nrf/lib/nrf_modem_lib/sanity.c
C:/ncs/v2.4.2/nrf/lib/nrf_modem_lib/sanity.c:10:10: fatal error: pm_config.h: No such file or directory
   10 | #include <pm_config.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
[7/56] Building C object modules/nrf/drivers/hw_cc310/CMakeFiles/..__nrf__drivers__hw_cc310.dir/hw_cc310.c.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\31f4403e35\opt\bin\cmake.EXE' --build 'C:\ncs\v2.4.2\nrf\samples\nrf9160\at_client\build'

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Thu, 12 Oct 2023 12:51:16 GMT

Hello, I ran the command west update on the command prompt and I got this error

=== updating zephyr (zephyr):
HEAD is now at 28a3fca7da [nrf fromtree] libc/picolibc: Remove -T /dev/null linker arguments
=== updating bsim (tools/bsim):
HEAD is now at 908ffde west.yaml: Namespace all projects
=== updating hostap (modules/lib/hostap):
HEAD is now at c54b1efd0 Remove verbose print
=== updating mcuboot (bootloader/mcuboot):
HEAD is now at d5d451ec [nrf noup] boot: bootutil: Fix bl_secp256r1_validate call
=== updating qcbor (modules/tee/tf-m/qcbor):
HEAD is now at b0e7033 Make option to compile with warnings on (#162)
=== updating mbedtls (modules/crypto/mbedtls):
HEAD is now at 829e3edc7 [nrf fromlist] psa_crypto: Fix psa_key_derivation_output_key ECC without builtin keys
=== updating nrfxlib (nrfxlib):
HEAD is now at 30841c2a nrf_modem: v2.4.1
=== updating trusted-firmware-m (modules/tee/tf-m/trusted-firmware-m):
HEAD is now at f0bac9349 [nrf fromtree] platform: nordic_nrf: Add nrf9161 DK and nrf9120 SoC support
=== updating matter (modules/lib/matter):
HEAD is now at b5fbf81913 [nrf noup] Fix generate zap sript on windows
Synchronizing submodule url for 'third_party/nlio/repo'
Synchronizing submodule url for 'third_party/nlassert/repo'
Synchronizing submodule url for 'third_party/nlunit-test/repo'
Synchronizing submodule url for 'third_party/pigweed/repo'
=== updating cjson (modules/lib/cjson):
HEAD is now at c6af068 [nrf fromtree] fix: potential memory leak in merge_patch() (#611)
=== updating azure-sdk-for-c (modules/lib/azure-sdk-for-c):
HEAD is now at 308c171c [nrf fromlist] Make repository a Zephyr module
=== updating cirrus (modules/hal/cirrus-logic):
HEAD is now at 9f6b381 sdk-mcu-drivers: Added build system configs and generated files
=== updating openthread (modules/lib/openthread):
HEAD is now at d5a6630a8 [mesh-forwarder] only mark Key ID Mode 0 and 1 as secure
=== updating cmock (test/cmock):
HEAD is now at f65066f Merge pull request #404 from tz18/patch-1
Synchronizing submodule url for 'vendor/c_exception'
Synchronizing submodule url for 'vendor/unity'
=== updating memfault-firmware-sdk (modules/lib/memfault-firmware-sdk):
HEAD is now at efd97b9 Memfault Firmware SDK 0.43.3 (Build 2200)
=== updating canopennode (modules/lib/canopennode):
HEAD is now at dec12fa stack: map CANopenNode crc16_ccitt() to Zephyr crc16_itu_t()
=== updating chre (modules/lib/chre):
HEAD is now at b7955c27 Merge pull request #7 from stephanosio/require_full_libcpp
=== updating cmsis (modules/hal/cmsis):
HEAD is now at 74981bf Update DSP library for additional platforms
=== updating edtt (tools/edtt):
HEAD is now at 64e5105 edttt_bsim: Avoid infinite exception loop
=== updating fatfs (modules/fs/fatfs):
HEAD is now at 427159b zephyr: fix ffconf.h override use of STRINGIZE
=== updating hal_nordic (modules/hal/nordic):
HEAD is now at 140140e nrfx: mdk: Fix handling of APPROTECT on nRF91
=== updating hal_st (modules/hal/st):
HEAD is now at 5948f7b sensor/stmemsc: Align stmemsc i/f to v2.02
=== updating hal_wurthelektronik (modules/hal/wurthelektronik):
HEAD is now at 24ca987 Initialized WE HAL module repository.
=== updating libmetal (modules/hal/libmetal):
HEAD is now at efa2ace lib: update libmetal to SHA cd4fb67a4f50
=== updating liblc3 (modules/lib/liblc3):
HEAD is now at 448f3de Merge pull request #8 from carlescufi/rename
=== updating littlefs (modules/fs/littlefs):
HEAD is now at ca583fd Merge tag 'v2.5.0' of https://github.com/littlefs-project/littlefs into zephyr
=== updating loramac-node (modules/lib/loramac-node):
HEAD is now at ce57712f Don't memset the TXRX buffer when radio is set to receive mode (#1345)
=== updating lvgl (modules/lib/gui/lvgl):
HEAD is now at 1557cb3e zephyr: update SYS_INIT calls
=== updating lz4 (modules/lib/lz4):
HEAD is now at 8e303c2 zephyr: make this repo a zephyr module
=== updating mipi-sys-t (modules/debug/mipi-sys-t):
HEAD is now at 0d521d8 mipi_syst_api.c: Change MIPI_SYST_PCFG_PRINTF_ARGBUF_SIZE macro.
=== updating nanopb (modules/lib/nanopb):
HEAD is now at 42fa8b2 Merge pull request #2 from pdgendt/zephyr
=== updating net-tools (tools/net-tools):
HEAD is now at e0828aa net-setup: Add instructions for NAT and routing
=== updating nrf_hw_models (modules/bsim_hw_models/nrf_hw_models):
HEAD is now at bad9877 TEMP: Connect at the top level
=== updating open-amp (modules/lib/open-amp):
HEAD is now at aedcc26 lib: update open-amp lib to release v2022.10.0
=== updating picolibc (modules/lib/picolibc):
--- picolibc: fetching, need revision 93b5d5f2ad44867b60267417cd6d6250dbf68983
remote: Enumerating objects: 230253, done.
remote: Counting objects: 100% (10839/10839), done.
remote: Compressing objects: 100% (403/403), done.
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
error: 3369 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
=== updating segger (modules/debug/segger):
HEAD is now at 4bfaf28 zephyr: use external Kconfig
=== updating tinycrypt (modules/crypto/tinycrypt):
HEAD is now at 3e9a49d cmake: Fix conditional in root CMakeLists.txt
=== updating TraceRecorderSource (modules/debug/TraceRecorder):
HEAD is now at bc839bf zephyr: update SYS_INIT calls
=== updating tf-m-tests (modules/tee/tf-m/tf-m-tests):
HEAD is now at 0f80a65 Merge pull request #6 from microbuilder/tfm17_limit_attestation
=== updating psa-arch-tests (modules/tee/tf-m/psa-arch-tests):
HEAD is now at 6a17330 dev-apis: platform: Increase timeout for nRF devs
=== updating uoscore-uedhoc (modules/lib/uoscore-uedhoc):
HEAD is now at e892019 Merge pull request #11 from rlubos/zephyr-integration
=== updating zcbor (modules/lib/zcbor):
HEAD is now at 0556eda Update version from 0.5.99 to 0.6.0
=== updating zscilib (modules/lib/zscilib):
HEAD is now at 0035be5 Merge pull request #45 from uLipe/feature/qrd_no_recursion
ERROR: update failed for project picolibc

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Menon — Mon, 02 Oct 2023 13:35:16 GMT

Hello,

I was checking your screenshots, and inside the first screenshot, it says SDK is missing, and when I checked the last shared screenshot, it says a west update is required as some of the files are missing. Please do the west update either by running the command "west update" inside the command prompt or using the "Run west update" tab.

I also recommend that you go through this ticket. In the last response, I suggested a few things. Please make sure you are able to see the files mentioned there and also follow the updates I mentioned there.

Kind Regards,

Abhijith

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Mon, 02 Oct 2023 11:56:53 GMT

hello

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Sat, 30 Sep 2023 06:33:10 GMT

Hello I tried following this tutorial but when I try to copy sample there are no samples to copy from

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Menon — Wed, 27 Sep 2023 13:38:20 GMT

Hello,

usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: error: argument <command>: invalid choice: 'build' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate'

This error is most likely caused by missing the zephyr base. Can you attach the whole support information inside the VScode? This looks like an installation issue. I assume you are using Toolchain Manager for installing the SDK (please confirm this). See some old threads with similar errors.

[quote user="vtechcode"]I think we should schedule for an online meeting so that I can get real time help[/quote]

Sorry, the only channel through which I can provide support is via DevZone.

Kind Regards,

Abhijith

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Wed, 27 Sep 2023 12:48:28 GMT

C:\ncs\v2.4.2\nrf\samples\nrf9160\at_client>west build -b nRF9160dk_nrf9160
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: error: argument <command>: invalid choice: 'build' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate')

C:\ncs\v2.4.2\nrf\samples\nrf9160\at_client>

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Menon — Wed, 27 Sep 2023 11:37:05 GMT

Hello,

Please see that build_target is just the parameter mentioned for the build command; you need to mention your board name instead of build_target. For example, if you are building for nRF9160dk, then your build_target would be nRF9160dk_nrf9160, see here. In the below screenshot, I am building a Hello World sample for nrf9160K.

Kind Regards,

Abhijith

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Wed, 27 Sep 2023 11:00:44 GMT

Yes I am able to see my device inside the command prompt

Yes I followed all the steps mentioned in that guide

after running the nrfjprog --deviceversion inside the command prompt i got 960036574 - NRF9160_xxAA_REV2

C:\ncs\v2.4.2\nrf\samples\nrf9160\at_client>west build -b build_target
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: error: argument <command>: invalid choice: 'build' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate')

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Menon — Tue, 26 Sep 2023 12:31:53 GMT

Hello,

Are you able to see your device inside the command prompt? If the West build is also crashing, then it is not VScode extension-related. I am not sure of the issue, but it might be because of the wrong installation. Have you followed all the steps mentioned in this guide?

Please try running the command nrfjprog --deviceversion inside the command prompt and see whether your device is getting detected or not. Also, please share the whole logs when you build or flash from the command prompt. Use the insert tab to paste the whole log here.

Kind Regards,

Abhijith

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Mon, 25 Sep 2023 18:03:04 GMT

Please can we look for a way to do this much more quickly, I really need to start building my project soon, because the submission date is near

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Mon, 25 Sep 2023 08:04:08 GMT

Yes, I am using the toolchain Manager to open VS code
I think we should schedule for an online meeting so that I can get real time help

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Fri, 22 Sep 2023 21:24:24 GMT

I have not been able to flash a program using the command-prompt even after following the instructions, I get this error:
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: error: argument <command>: invalid choice: 'build' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate')

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

vtechcode — Fri, 22 Sep 2023 21:02:40 GMT

I am using j-link v7.88j and nrf v2.4.2

RE: My VS Code NRF extension cannot build an application and it cannot also detect my device

Menon — Fri, 22 Sep 2023 12:06:46 GMT

Hello,

I am letting you know that I have been assigned to this case. Could you check and share some more details on this issue?Are you able to detect and flash the device using command-prompt? See how to do this here.
Please check and share the versions of the J-Link and nRF command-line tools (you shared this in the screenshot). I also recommend you update it to the latest.Are you opening the VS code from the toolchain manager?

Kind Regards,

Abhijith