SDK Setup (Windows) west update dies

K2AAE

This is embarrassing, on step 9 in the remotes section I do not ‘get’ the '‘So it looks like:’ part. Below in the Projects section that works, the '‘So it looks like’ section does look like your example after I add.

Running west update:

Kevin@Aorus MINGW64 /d/ncs/v1.4.1/nrf ((v1.4.1))
$ west update
FATAL ERROR: can't load west manifest
  Malformed manifest file: D:\ncs\v1.4.1\nrf\west.yml
  Schema file: D:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\west\manifest-schema.yml
  Hint: Schema validation failed:
 - Cannot find required key 'url-base'. Path: '/remotes/7'.
 - Key 'path' was not defined. Path: '/remotes/7'.
 - Key 'revision' was not defined. Path: '/remotes/7'.
 - Key 'remote' was not defined. Path: '/remotes/7'.
 - Cannot find required key 'url-base'. Path: '/remotes/8'.
 - Key 'repo-path' was not defined. Path: '/remotes/8'.
 - Key 'revision' was not defined. Path: '/remotes/8'.
 - Key 'path' was not defined. Path: '/remotes/8'.
 - Key 'remote' was not defined. Path: '/remotes/8'.

I ‘restored’ the west.yml and ran update, it worked.
from my west.yml.mod

    - name: circuitdojo
      url-base: https://github.com/circuitdojo
    - name: Alexa-Gadgets-Embedded-Sample-Code
      path: modules/alexa-embedded
      revision: face92d8c62184832793f518bb1f19379538c5c1
      remote: alexa
    - name: nfed
      repo-path: nrf9160-feather-examples-and-drivers
      revision: v1.4.x
      path: nfed
      remote: circuitdojo

————
I got rid of everything in remote but:

    - name: circuitdojo
      url-base: https://github.com/circuitdojo

then did west update:

=== updating nfed (nfed):
--- nfed: initializing
Initialized empty Git repository in D:/ncs/v1.4.1/nfed/.git/
--- nfed: fetching, need revision v1.4.x
remote: Enumerating objects: 157, done.
remote: Counting objects: 100% (157/157), done.
remote: Compressing objects: 100% (109/109), done.
remote: Total 157 (delta 49), reused 137 (delta 33), pack-reused 0
Receiving objects: 100% (157/157), 44.15 KiB | 1.34 MiB/s, done.
Resolving deltas: 100% (49/49), done.
From https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers
 * branch            v1.4.x     -> FETCH_HEAD

It looks like that is the issue, the ‘So it looks like’ confused me. (not hard to do these days)

jaredwolff

K2AAE Looks like you put the url entry in the wrong place/ put the repos in the wrong place. Here’s what a working manifest should look like:

# The west manifest file (west.yml) for the nRF Connect SDK (NCS).
#
# The per-workspace west configuration file, ncs/.west/config,
# specifies the location of this manifest file like this:
#
#     [manifest]
#     path = nrf
#
# See the west documentation for more information:
#
# https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/west/index.html

manifest:
  # This west.yml requires west 0.7 or later, because the "import"
  # feature used below was introduced then.
  version: 0.7

  # "remotes" is a list of locations where git repositories are cloned
  # and fetched from.
  remotes:
    # nRF Connect SDK GitHub organization.
    # NCS repositories are hosted here.
    - name: ncs
      url-base: https://github.com/nrfconnect
    # Third-party repository sources:
    - name: zephyrproject
      url-base: https://github.com/zephyrproject-rtos
    - name: throwtheswitch
      url-base: https://github.com/ThrowTheSwitch
    - name: armmbed
      url-base: https://github.com/ARMmbed
    - name: nanopb
      url-base: https://github.com/nanopb
    - name: alexa
      url-base: https://github.com/alexa
    - name: circuitdojo
      url-base: https://github.com/circuitdojo

  # If not otherwise specified, the projects below should be obtained
  # from the ncs remote.
  defaults:
    remote: ncs

  # "projects" is a list of git repositories which make up the NCS
  # source code.
  projects:

    # The Zephyr RTOS fork in the NCS, along with the subset of its
    # modules which NCS imports directly.
    #
    # https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/introduction/index.html
    # https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/modules.html
    - name: zephyr
      repo-path: sdk-zephyr
      revision: v2.4.0-ncs2
      import:
        # In addition to the zephyr repository itself, NCS also
        # imports the contents of zephyr/west.yml at the above
        # revision. Only the projects explicitly named in the
        # following whitelist are imported.
        #
        # Note that the zephyr west extensions (like 'build', 'flash',
        # 'debug', etc.) are automatically provided by this import, so
        # there's no need to add a redundant west-commands: key for
        # the zephyr project.
        #
        # Please keep this list sorted alphabetically.
        name-whitelist:
          - canopennode
          - ci-tools
          - cmsis
          - civetweb
          - edtt
          - fatfs
          - hal_nordic
          - hal_st
          - libmetal
          - littlefs
          - loramac-node
          - lvgl
          - mbedtls
          - mipi-sys-t
          - net-tools
          - nrf_hw_models
          - open-amp
          - openthread
          - segger
          - tinycbor
          - tinycrypt

    # NCS repositories.
    #
    # Some of these are also Zephyr modules which have NCS-specific
    # changes.
    - name: mcuboot
      repo-path: sdk-mcuboot
      revision: v1.6.99-ncs1
      path: bootloader/mcuboot
    - name: mcumgr
      repo-path: sdk-mcumgr
      revision: v0.1.0-ncs1
      path: modules/lib/mcumgr
    - name: nrfxlib
      repo-path: sdk-nrfxlib
      path: nrfxlib
      revision: v1.4.1
    # Other third-party repositories.
    - name: cmock
      path: test/cmock
      revision: c243b9a7a7b3c471023193992b46cf1bd1910450
      remote: throwtheswitch
    - name: unity
      path: test/cmock/vendor/unity
      revision: 031f3bbe45f8adf504ca3d13e6f093869920b091
      remote: throwtheswitch
    - name: mbedtls-nrf
      path: mbedtls
      repo-path: mbedtls
      revision: mbedtls-2.23.0
      remote: armmbed
    - name: nanopb
      path: modules/lib/nanopb
      revision: nanopb-0.4.2
      remote: nanopb
    - name: Alexa-Gadgets-Embedded-Sample-Code
      path: modules/alexa-embedded
      revision: face92d8c62184832793f518bb1f19379538c5c1
      remote: alexa
    - name: nfed
      repo-path: nrf9160-feather-examples-and-drivers
      revision: v1.4.x
      path: nfed
      remote: circuitdojo

  # West-related configuration for the nrf repository.
  self:
    # This repository should be cloned to ncs/nrf.
    path: nrf
    # This line configures west extensions which are currently only
    # for internal use by NCS maintainers.
    west-commands: scripts/west-commands.yml

K2AAE

jaredwolff
From here:
https://docs.jaredwolff.com/nrf9160-sdk-setup-windows.html
Is were I got:

To get the nRF9160 Feather examples we’ll update /opt/nordic/v1.4.1/nrf/west.yml. First in the remotes section add:
- name: circuitdojo
  url-base: https://github.com/circuitdojo

So it looks like:

name: Alexa-Gadgets-Embedded-Sample-Code
path: modules/alexa-embedded
revision: face92d8c62184832793f518bb1f19379538c5c1
remote: alexa
name: nfed
repo-path: nrf9160-feather-examples-and-drivers
revision: v1.4.x
path: nfed
remote: circuitdojo

As I said the “So it looks like:” confused me.

jaredwolff

K2AAE Ahh ok! I’ve updated that section. It definitely wasn’t as clear as I had liked. Thanks for the input @K2AAE!