Hello CircuitDojo Community,
I am working on a Zephyr based application targeting both sparkfun_thing_plus_nrf9160 dev board, and thingy91_nrf9160 dev board. My starting point for this application is Nordic Semi’s aws_iot sample app, from among the sample apps in their nrf-sdk code repository.
Following @jaredwolff recommendations in a post a couple of days ago (2021-Sept-14) I have created a west.yml manifest file and placed this along side a stand alone copy of aws_iot sample app. Before cloning this small project to my workstation I create a local directory named
aws-iot-stand-alone. I clone my mentioned project to this directory. In the parent dir of this directory I run
west init -l aws-iot-stand-alone. Next I change directories into
aws-iot-stand-alone and I run
git clone and
west set up steps, I try to build the project with this invocation:
`west build -b thingy91_nrf9160ns`
And I get the error message:
west: error: argument <command>: invalid choice: 'build' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate')
Strange thing is, I am able to build another small Zephyr based project of my own on the same workstation. I installed Nordic’s Zephyr toolchain a few weeks ago and have been building sample apps and custom apps over this span of time. I can still build them in certain west workspaces, but not the ones I have tried to create via fresh
git clone ... west init steps for this latest personal project.
Is there a clue here I am missing, as to why
west cannot find Zephyr’s extending commands, specifically ‘build’ and ‘flash’? As I understand,
west init initializes a cloned project as a west workspace. Therefore I am calling
west build ... inside a valid west workspace. But somehow
west in the newly created workspace cannot “see” its Zephyr project command extensions.
Help on this issue much appreciated!