• State Not Answered
  • Replies 6 replies
  • Subscribers 26 subscribers
  • Views 157 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 290725
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

west build is invalid choice

user4461

Hi,

I have installed the nRF Connect SDK v2.0.0 with Visual Studio and can now successfully, build, flash and run the nrf9160 at_client sample application. But when I try to build it from the command line west says that 'build' is an invalid choice. When building from the command line, I select "Open Terminal" from the nRF Connect SDK line in the toolchain manager. Then when I try to build, I get this:

at_client [master●] % west build -b nrf9160dk_nrf9160_ns
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')
Any ideas why this is happening?
Thanks
Greg
Parents
  • 0

    I'm pretty sure ZEPHYR_BASE just tells west where Zephyr is installed. I've followed Nordic's instructions and used their Tool Chain Manager GUI to install the SDK. And it appears that if you do that, you need to add the ZEPHYR_BASE env variable so west can find it.

    It looks like as an alternative, we maybe could use a manifest and do west init/west update. Perhaps that will be the better solution in the end. Thanks for your sample manifest, that will save me a bunch of time as I experiment with this.

    I do think there is still an issue here for Nordic. I would think that when you use "Open Terminal" from the Toolchain Manager SDK drop down, that the ZEPHYR_BASE env variable should have been set. If Nordic agrees, maybe you can add that to their TODO list.

Reply
  • 0

    I'm pretty sure ZEPHYR_BASE just tells west where Zephyr is installed. I've followed Nordic's instructions and used their Tool Chain Manager GUI to install the SDK. And it appears that if you do that, you need to add the ZEPHYR_BASE env variable so west can find it.

    It looks like as an alternative, we maybe could use a manifest and do west init/west update. Perhaps that will be the better solution in the end. Thanks for your sample manifest, that will save me a bunch of time as I experiment with this.

    I do think there is still an issue here for Nordic. I would think that when you use "Open Terminal" from the Toolchain Manager SDK drop down, that the ZEPHYR_BASE env variable should have been set. If Nordic agrees, maybe you can add that to their TODO list.

Children
No Data
Related
Terms of service