Closed RobMeades closed 10 months ago
Hmmm, seems that, if this happens, you have to delete the previously-cloned nrfconnectsdk-v2.5.0
directory before trying to install again: looks like an nrfconnectsdk-v2.5.0\.west\manifest-tmp
is created inside it as part of the [failed] installation process which somehow doesn't play will with version 0.12
of west
?
Anyway, deleting and re-cloning fixed it for me.
I don't know anything about nrfConnect and its installation process but for future reference I can summarize the failure shown in this stack trace.
What happened there is that west
looked for a manifest as part of an initialization process. It didn't find any. It looked for:
[manifest]
path = ...
inside the file: workspace/.west/config
but there was no such file.
This type of error usually looks better ("FATAL ERROR: no west workspace found") but initialization/bootstrap creates some interesting chicken-and-egg challenges.
looks like an nrfconnectsdk-v2.5.0.west\manifest-tmp is created inside it as part of the [failed] installation process
This looks like:
somehow doesn't play will with version 0.12 of west?
I could be wrong but I doubt the west version matters that much.
We are trying to move from nrfConnect 2.3.0/Zephyr 3.2.99 to nrfConnect 2.5.0/Zephyr 3.5.99.
The new version requires
west
0.13 instead of thewest
0.12 that we had previously, which is fine, we have updatedwest
to 0.13.However, after doing that, the installation process fails with
west
saying "RuntimeError: local configuration file not found" (full dump below). There is nowest
,.west
or.westconfig
directory anywhere that I can find on my disk; this is on Windows (10) and I have specifically checked my user directory, theProgramData
directory and the directory where I happen to be running the installation from. I have tried uninstalling and reinstallingwest
but that doesn't seem to have helped.How can I make
west
happy?