Update west manifest

[dave]

I have a project using ncs 2.7 with the nrf9160.  My west manifest file is set up to import all and it takes forever, so I am trying to narrow it down to only what is needed, but when I change the manifest file and run the west init and west update commands, then try to build in the nrf connect vs code extension like I normally do, I get an error that west build is not recognized

What is the right way to add an allow list to limit what is downloaded using west update?

Original west.yml file

manifest:
  version: "0.10"
  remotes:
    # Add the Memfault GitHub repo
    - name: memfault
      url-base: https://github.com/memfault

  projects:

    # Specify the nRF-Connect SDK as a project dependency.
    - name: sdk-nrf
      path: nrf
      url: https://github.com/nrfconnect/sdk-nrf.git
      revision: v2.7.0
      import: true

    # Add the Memfault SDK
    - name: memfault-firmware-sdk
      path: modules/lib/memfault-firmware-sdk
      revision: 1.18.0
      remote: memfault

Updated west.yml file

manifest:
  version: "0.10"
  remotes:
    # Add the Memfault GitHub repo
    - name: memfault
      url-base: https://github.com/memfault

  projects:

    # Specify the nRF-Connect SDK as a project dependency
    - name: sdk-nrf
      path: nrf
      url: https://github.com/nrfconnect/sdk-nrf.git
      revision: v2.7.0
      import:
        name-allowlist:
        - hal_nordic
        - mcuboot
        - memfault-firmware-sdk
        - nrf
        - trusted-firmware-m

    # Add the Memfault SDK
    - name: memfault-firmware-sdk
      path: modules/lib/memfault-firmware-sdk
      revision: 1.18.0
      remote: memfault

[Hakon]

Hello,

can you show what the ncs installation folder looks like, and preferably also upload it here so I can test?

[dave]

it won't upload, the zipped file is too large.  Here is a screen shot of the top level of the folder where ncs 2.7 is installed

If it matters, my project uses out of tree drivers and board files, so I init my west workspace at the root level and then navigate to my app directory  to build

My projects structure after updating west looks like this.

\
├── .west/
├── bootloader/
├── modules/
├── nrf/
├── prj/
│   ├── boards/
│   ├── CMakeLists.txt
│   ├── app/
│   │   ├── CMakeLists.txt
│   │   ├── CMakePresets.json
│   │   ├── config/
│   │   ├── docs/
│   │   ├── firmware_version.c.in
│   │   ├── app.overlay
│   │   ├── Kconfig
│   │   ├── overlay-firmware.conf.in
│   │   ├── overlay-memfault.conf
│   │   ├── prj.conf
│   │   ├── scripts/
│   │   ├── src/
│   │   ├── test/
│   │   └── version.cmake
│   ├── drivers/
│   ├── dts/
│   ├── Kconfig
│   └── west.yml
├── README.md
└── zephyr/

[Hakon]

then try to build in the nrf connect vs code extension like I normally do

Does it also happen if you build from command line, or is it just vscode that has this problem?

[dave]

I get the same error building from the command line (it usually works OK)

`usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: unknown command "build"; workspace`

[Hakon]

Have you checked if the ZEPHYR_BASE variable is set properly?