All AT Commands time out in LTE link monitor

jaredwolff Jared,
Thanks I’ll short those pins and try again. That link you provided above downloads something called app_update.bin (not at-client) - should I load app_update.bin?
I originally loaded the at-client-v1.3.2.bin (the start of this post and saga) and when I connected LTE link monitor, every AT command I would issue would time out. At this point, getting the AT commands working, so I can evaluate the modem is really all I’m trying to do (for now)
Thanks, Kurt

jaredwolff Jared,
Thanks! That worked. So… What is different between loading this “app_update.bin” vs my original attempt loading the at-client-v1.3.2.bin? Curious what I did wrong.
Kurt

jaredwolff Jared,
Never mind - I’m guessing you just rebuilt the at-client sample and the app_update.bin was just the output of the build. I’m working my way through the development environment and building the samples.
Kurt

jaredwolff Jared
Ok, so I’ve followed the instructions to set up the SDK and when I tried to build the blinky sample it fails (see output below). Sorry to be such a pest - I usually don’t have this much trouble getting going with things…
Kurt

macair> west build –board circuitdojo_feather_nrf9160ns -p
– west build: making build dir /opt/nordic/ncs/v1.5.0/nfed/samples/blinky/build pristine
– west build: generating a build system
Including boilerplate (Zephyr base): /opt/nordic/ncs/v1.5.0/zephyr/cmake/app/boilerplate.cmake
– Application: /opt/nordic/ncs/v1.5.0/nfed/samples/blinky
– Using NCS Toolchain 1.5.0 for building. (/opt/nordic/ncs/v1.5.0/toolchain/cmake)
– Zephyr version: 2.4.99 (/opt/nordic/ncs/v1.5.0/zephyr)
– Found Python3: /opt/nordic/ncs/v1.5.0/toolchain/bin/python3 (found suitable exact version “3.8.2”) found components: Interpreter
– Found west (found suitable version “0.9.0”, minimum required is “0.7.1”)
CMake Error at /opt/nordic/ncs/v1.5.0/zephyr/cmake/zephyr_module.cmake:61 (message):
Traceback (most recent call last):

File "/opt/nordic/ncs/v1.5.0/zephyr/scripts/zephyr_module.py", line 378, in <module>
  main()
File "/opt/nordic/ncs/v1.5.0/zephyr/scripts/zephyr_module.py", line 283, in main
  manifest = Manifest.from_file()
File "/opt/nordic/ncs/v1.5.0/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py", line 1084, in from_file
  return Manifest(**kwargs)
File "/opt/nordic/ncs/v1.5.0/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py", line 1273, in __init__
  self._load(source_data['manifest'],
File "/opt/nordic/ncs/v1.5.0/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py", line 1527, in _load
  self._load_projects(manifest, url_bases, defaults, ctx)
File "/opt/nordic/ncs/v1.5.0/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py", line 1859, in _load_projects
  self._import_from_project(project, imp, ctx)
File "/opt/nordic/ncs/v1.5.0/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py", line 2047, in _import_from_project
  self._import_path_from_project(project, imap.file,
File "/opt/nordic/ncs/v1.5.0/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py", line 2059, in _import_path_from_project
  imported = self._import_content_from_project(project, path)
File "/opt/nordic/ncs/v1.5.0/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py", line 2122, in _import_content_from_project
  content = self._importer(project, path)
File "/opt/nordic/ncs/v1.5.0/toolchain/Cellar/python@3.8/3.8.2/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/west/manifest.py", line 176, in _default_importer
  raise ManifestImportFailed(project, file)

west.manifest.ManifestImportFailed: ManifestImportFailed: project <Project
zephyr (‘/opt/nordic/ncs/v1.5.0/zephyr’) at v2.4.99-ncs1> file west.yml

Call Stack (most recent call first):
/opt/nordic/ncs/v1.5.0/zephyr/cmake/app/boilerplate.cmake:183 (include)
/opt/nordic/ncs/v1.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
/opt/nordic/ncs/v1.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
CMakeLists.txt:4 (find_package)

– Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /opt/nordic/ncs/v1.5.0/toolchain/bin/cmake -DWEST_PYTHON=/opt/nordic/ncs/v1.5.0/toolchain/bin/python3 -B/opt/nordic/ncs/v1.5.0/nfed/samples/blinky/build -S/opt/nordic/ncs/v1.5.0/nfed/samples/blinky -GNinja -DBOARD=circuitdojo_feather_nrf9160ns

jaredwolff I am running this in the terminal/shell that opens from the nRF connect toolchain manager. I did make the edits to add NFED and didn’t see any errors when I ran west update after making the changes to west.yml.

I think I’ll see if there is a way to blow away the SDK and reinstall it again to see if that clears up the problem.

Kurt

jaredwolff I removed the SDK, reinstalled, modified west.yml and west update. Then tried building the sample again. Same problem. It kind of looks like the failure is because there is a ‘_default_importer’ method that is the default callback invoked when “the source file requires importing manifest data that aren’t found locally”. The default one simply throws the exception. From looking at the API, it looks like the caller of the Manifest API is supposed to provide an ‘importer’ callback if they expect to handle this case (manifest data not found locally). Apparently there isn’t one provided in this case, so the exception is thrown. I’ll keep working my way back from this info to see if I can tell why this is happening. I’m guessing this must be some sort of environmental issue on my system… Sigh.

Kurt

jaredwolff I do have make installed on my Mac; I have a /usr/local/bin/cmake which reports version 3.19.1. Likely a requirement for something else I develop with. When I do a which cmake in the terminal window created from nRF connect desktop toolchain manager, it reports: /opt//nordic/ncs/v1.5.0/toolchain/bin/cmake so I don’t think it is getting the /usr/local/bin/cmake that is installed on my Mac. A which on west and ninja also reports the same path under /opt/nordic/ncs/v1.5.0/toolchain/bin.

As for your second question - no, I’m not running any of this in an IDE, just at the shell prompt in the terminal window that is opened (with the correct environment setup) from the nRF connect desktop…

Kurt

jaredwolff also, just in case I did a chmod -x on my /usr/local/bin/cmake and tried again - same failure so we can rule out the cmake I have installed on my Mac…
Kurt

jaredwolff in case it is useful, doing a west config -l reports the following:

manifest.path=nrf
manifest.file=west.yml
zephyr.base=zephyr

jaredwolff My permissions match yours. Nothing else in my /opt except for nordic.

This is an Intel Mac.

Kurt