Trouble updating from NCS v1.9.1 to v2.1.4: No ${ZEPHYR_BASE}/modules/hal_nordic/Kconfig.dt

RE: Trouble updating from NCS v1.9.1 to v2.1.4: No ${ZEPHYR_BASE}/modules/hal_nordic/Kconfig.dt

Øivind — Thu, 13 Apr 2023 22:38:40 GMT

Is your SDK installed using the Toolchain Manager in nRF Connect for Desktop? If so could you try installing another version and see if the remote nrf repo is found there?

If you are not installing using the Toolchain Manager, could you explain how you are setting up the SDK?

RE: Trouble updating from NCS v1.9.1 to v2.1.4: No ${ZEPHYR_BASE}/modules/hal_nordic/Kconfig.dt

Yaron Shragai — Thu, 13 Apr 2023 20:29:25 GMT

The thing is, the deeper problem is that my git can't find the remote nrf repo.

If I do what you suggested I get:

<...path redacted...>/nrf$ git checkout v2.1.4
error: pathspec 'v2.1.4' did not match any file(s) known to git

RE: Trouble updating from NCS v1.9.1 to v2.1.4: No ${ZEPHYR_BASE}/modules/hal_nordic/Kconfig.dt

Øivind — Thu, 13 Apr 2023 13:32:57 GMT

v2.1.4 is a tag, not a branch, so try checkout instead of pull:

git checkout v2.1.4

If that doesn't work you may want to reinstall the SDK from the Toolchain Manager and try with a fresh install.

RE: Trouble updating from NCS v1.9.1 to v2.1.4: No ${ZEPHYR_BASE}/modules/hal_nordic/Kconfig.dt

Yaron Shragai — Wed, 12 Apr 2023 13:52:50 GMT

Thanks, I didn't realize that you have to update the nrf repo first - I thought that when you specify the latest nrf rev in the manifest file, west update would take care of updating the repo to that revision.

I may need some help with git then. I'm not sure how to update the nrf repo to v2.1.4 from the state that my nrf repo is in right now.

Here is a session with some git commands illustrating the current state of my nrf repo.

<...path redacted...>$ cd nrf
<...path redacted...>/nrf$ git status
HEAD detached at refs/heads/manifest-rev
nothing to commit, working tree clean
<...path redacted...>/nrf$ git fetch
<...path redacted...>/nrf$ git pull origin v2.1.4
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
<...path redacted...>/nrf$ git remote show origin
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
<...path redacted...>/nrf$ git log --oneline -10
126fad0e (grafted, HEAD, tag: v1.9.1, manifest-rev) manifest: update manifest file with 1.9.1 tags
<...path redacted...>/nrf$ git branch
* (HEAD detached at refs/heads/manifest-rev)
  manifest-rev

RE: Trouble updating from NCS v1.9.1 to v2.1.4: No ${ZEPHYR_BASE}/modules/hal_nordic/Kconfig.dt

Øivind — Wed, 12 Apr 2023 11:52:00 GMT

Hi,

Could you describe exactly how you update your SDK? Normally you would first update the nrf repository to v2.1.4, using git for example, then run west update. This should update your zephyr repository to v3.1.99-ncs1-3, which contains the Kconfig.dt file.

RE: Trouble updating from NCS v1.9.1 to v2.1.4: No ${ZEPHYR_BASE}/modules/hal_nordic/Kconfig.dt

Yaron Shragai — Tue, 11 Apr 2023 14:02:03 GMT

It actually works if I create a new work area (never been built before) with the updated manifest file, rather than updating the manifest file in my existing work area.