I had never done the minimal for v1.4.1 so I tried it, v1.4.1 mini downloaded and I ran a bash shell on my Windows 10 computer, after updating west.yml:
Kevin@Aorus MINGW64 /c/ncs/v1.4.1/nrf ((v1.4.1))
$ west update
Traceback (most recent call last):
File “runpy.py”, line 193, in _run_module_as_main
File “runpy.py”, line 86, in _run_code
File “C:\ncs\v1.4.1\toolchain\opt\bin\Scripts\west.exe__main__.py”, line 7, in <module>
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\west\app\main.py”, line 768, in main
app.run(argv or sys.argv[1:])
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\west\app\main.py”, line 98, in run
self.load_manifest()
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\west\app\main.py”, line 116, in load_manifest
self.manifest = Manifest.from_file(topdir=self.topdir)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\west\manifest.py”, line 252, in from_file
return Manifest(**kwargs)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\west\manifest.py”, line 380, in init
source_data = _load(source_data)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\west\manifest.py”, line 1586, in _load
return yaml.safe_load(data)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml__init.py”, line 162, in safe_load
return load(stream, SafeLoader)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml__init.py”, line 114, in load
return loader.get_single_data()
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\constructor.py”, line 49, in get_single_data
node = self.get_single_node()
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\composer.py”, line 36, in get_single_node
document = self.compose_document()
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\composer.py”, line 55, in compose_document
node = self.compose_node(None, None)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\composer.py”, line 84, in compose_node
node = self.compose_mapping_node(anchor)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\composer.py”, line 133, in compose_mapping_node
item_value = self.compose_node(node, item_key)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\composer.py”, line 84, in compose_node
node = self.compose_mapping_node(anchor)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\composer.py”, line 133, in compose_mapping_node
item_value = self.compose_node(node, item_key)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\composer.py”, line 82, in compose_node
node = self.compose_sequence_node(anchor)
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\composer.py”, line 110, in compose_sequence_node
while not self.check_event(SequenceEndEvent):
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\parser.py”, line 98, in check_event
self.current_event = self.state()
File “C:\ncs\v1.4.1\toolchain\opt\bin\Lib\site-packages\yaml\parser.py”, line 392, in parse_block_sequence_entry
raise ParserError(“while parsing a block collection”, self.marks[-1],
yaml.parser.ParserError: while parsing a block collection
in “<unicode string>”, line 53, column 5:
- name: zephyr
^
expected <block end>, but found ‘?’
in “<unicode string>”, line 130, column 5:
repo-path: nrf9160-feather-examp …
^
Kevin@Aorus MINGW64 /c/ncs/v1.4.1/nrf ((v1.4.1))
$ python -V
Python 3.8.2
Kevin@Aorus MINGW64 /c/ncs/v1.4.1/nrf ((v1.4.1))
I did a printenv and compared it with a ‘working’ v1.4.1 (C: and D: drives ) other than the Drive they are the same.
recap:
Follow the guide with mini install on C: of v1.4.1 dies on west update.
v1.4.1 on D: is a full version and west update worked without an issue.
FYI: the Edit west.yml was clear as a bell.
@Paddy The examples were made for v1.4.1 SDK - I have not figured out what Nordic is doing with the SDK revisions since the firmware AT&T and Verizon will allow us to use requires old SDK’s to work. A look at https://infocenter.nordicsemi.com/topic/comp_matrix_nrf9160/COMP/nrf9160/nrf9160_operator_certifications.html
is now showing that 1.2.1/1.2.3 (AT&T SDK 1.3.1/1.5.0) with 1.1.2 / 1.1.4 (Verizon SDK 1.2.1/1.5.0) all most all the firmware that now works with v1.5.0 was not what many products were certified with.
