Adding pcf85033a to a Nordic NCS project

schmichiel

Hi Jared,

First of all thanks for all the content you provide on YouTube and Github you have been an amazing help navigating through Zephyr for me!

I wanted to provide some feedback on your https://github.com/circuitdojo/pcf85063a.

I tried to follow your steps to add the module to Zephyr in a Nordic NCS context but with the steps provided in the readme file I was unsuccesful.

An NCS project seemingly has 2 .yml files. The regular Zephyr one and one in the /nrf sub directory. To the latter I had two add the remote for circuitdojo:
- name: circuitdojo
url-base: https://github.com/circuitdojo

and an entry underneath what Nordic describes as third-party repository information:
- name: pcf85063a
path: modules/lib/pcf85063a
revision: master
remote: circuitdojo

When I did added those 2 things to the correst west.yml file I was able to run west update correctly and use the module.

I’ll add the entire west.yml file as well.

Cheers,
Michiel

9 of 6,175
Adding pcf85063a to west.yml file
Inbox

Michiel S <michiel.scheys@gmail.com>
Attachments
Thu, Jan 26, 11:17 AM (4 days ago)
to jared

Hi Jared,

First of all thanks for all the content you provide on YouTube and Github you have been an amazing help navigating through Zephyr for me!

I wanted to give you some feedback on adding the PCF85063A module to Zephyr, specifically for Nordic NCS. The information you provided in the readme did not do the trick for me in the NCS and when asking in the Nordic devzone they also weren't able to give me the correct information. What makes matters more complicated is that in an NCS project there are multiple west.yml files unfortunately. So anyway I'll add the west.yml file (the one supposed to be in the /home/developer/ncs/v2.1.0/nrf folder) that made it work for me. 

If you prefer I could open an issue on Github, but I didn't really want to do that since this is kind of Nordic specific maybe. 

Anyway, thanks again for all the content!
Best regards,

Michiel
 One attachment
  •  Scanned by Gmail

Jared Wolff
Fri, Jan 27, 5:27 PM (3 days ago)
to me

Hey Michiel

Can you ask this on my community forum?

https://community.jaredwolff.com/

Thanks!

Jared
New live sessions every week on Youtube 📺.
Attachments:
west.yml

Will do!Sure thing!No, I can't.
# 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:
  version: "0.12"

  # "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: nordicsemi
      url-base: https://github.com/NordicSemiconductor
    - name: memfault
      url-base: https://github.com/memfault
    - 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

  group-filter: [-homekit, -nrf-802154, -find-my]

  # "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: v3.1.99-ncs1
      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 allowlist 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-allowlist:
          - TraceRecorderSource
          - canopennode
          - chre
          - cmsis
          - edtt
          - fatfs
          - fff
          - hal_nordic
          - hal_st
          - liblc3codec
          - libmetal
          - littlefs
          - loramac-node
          - lvgl
          - lz4
          - mbedtls
          - mipi-sys-t
          - nanopb
          - net-tools
          - nrf_hw_models
          - open-amp
          - picolibc
          - psa-arch-tests
          - segger
          - tinycbor
          - tinycrypt
          - tf-m-tests
          - zcbor
          - zscilib

    # NCS repositories.
    #
    # Some of these are also Zephyr modules which have NCS-specific
    # changes.
    - name: sdk-hostap
      path: modules/lib/hostap
      revision: 47399f055431513b5dfcd9d1fd1ec5dc5c96a252
    - name: mcuboot
      repo-path: sdk-mcuboot
      revision: v1.9.99-ncs2
      path: bootloader/mcuboot
    - name: mbedtls-nrf
      path: mbedtls
      repo-path: sdk-mbedtls
      revision: v3.1.0-ncs1
    - name: nrfxlib
      repo-path: sdk-nrfxlib
      path: nrfxlib
      revision: v2.1.0
    - name: trusted-firmware-m
      repo-path: sdk-trusted-firmware-m
      path: modules/tee/tf-m/trusted-firmware-m
      revision: v1.6.0-ncs1
    - name: tfm-mcuboot # This is used by the trusted-firmware-m module.
      repo-path: sdk-mcuboot
      path: modules/tee/tfm-mcuboot
      revision: v1.7.2-ncs2
    - name: matter
      repo-path: sdk-connectedhomeip
      path: modules/lib/matter
      revision: v2.1.0
      submodules:
        - name: nlio
          path: third_party/nlio/repo
        - name: nlassert
          path: third_party/nlassert/repo
        - name: nlunit-test
          path: third_party/nlunit-test/repo
        - name: pigweed
          path: third_party/pigweed/repo
    - name: nrf-802154
      repo-path: sdk-nrf-802154
      path: nrf-802154
      revision: v2.1.0
      groups:
      - nrf-802154
    - name: cjson
      repo-path: sdk-cjson
      path: modules/lib/cjson
      revision: c6af068b7f05207b28d68880740e4b9ec1e4b50a
    - name: homekit
      repo-path: sdk-homekit
      revision: v2.1.0
      groups:
      - homekit
    - name: find-my
      repo-path: sdk-find-my
      revision: v2.1.0
      groups:
      - find-my
    - name: azure-sdk-for-c
      repo-path: azure-sdk-for-c
      path: modules/lib/azure-sdk-for-c
      revision: 308c171cb4b5eed266649012a68406487ec81fb2
    # Other third-party repositories.
    - name: cmock
      path: test/cmock
      submodules: true
      revision: f65066f15d8248e6dcb778efb8739904a4512087
      remote: throwtheswitch
    - name: memfault-firmware-sdk
      path: modules/lib/memfault-firmware-sdk
      revision: 0.33.2
      remote: memfault
    - name: cirrus
      repo-path: sdk-mcu-drivers
      path: modules/hal/cirrus-logic
      revision: 9f6b3812237fbb0d4157ba3584c13f1644fcbe3a
    - name: openthread
      repo-path: sdk-openthread
      path: modules/lib/openthread
      revision: 0d19f9112101e87722ec80b3a247bc7a1c54b232
    - name: pcf85063a
      path: modules/lib/pcf85063a 
      revision: master
      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.
    west-commands: scripts/west-commands.yml`

jaredwolff

schmichiel so west update works OK. What exactly is failing?

schmichiel

jaredwolff

With the edits described above everything works fine. It’s when I followed the steps in the readme of the project the module did not show up in NCS folder and the CONFIG_PCF85063A was not found in the prj.conf. I’m not sure why.

jaredwolff

Can you provide the output from your build log? Your board overlay and configuration files?