Could someone please explain how to solve the dreaded error/warning code -115 that I am getting when I execute the setting parameters in nRFConnect Serial Terminal? I have connected the nRF9160 DK board, and the SIM card was added successfully on the nRF Cloud website. I get the following in repeated message in the terminal output log file:
golioth_system: Starting connect
golioth_system: Failed to connect: -22
golioth_system: Failed to make CoAP request: -115
golioth_system: Failed to send sensor data to Golioth: -115
app_work: process_rmc_frames _thread: GPS Position: ************.
I have followed the “Setup Nordic nRF Connect SDK (NCS)” and I was able to finish. However, I was not able to finish the “Flash Firmware” instruction because of the in the “Build hello example” fails with the following error message:
error: Aborting due to Kconfig warnings
– Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -DWEST_PYTHON=/Users//golioth-zephyr-workspace/.venv/bin/python3.12 -B/Users//golioth-zephyr-workspace/modules/lib/golioth-firmware-sdk/build -GNinja -DBOARD=nrf9160dk/nrf9160/ns -S/Users/******/golioth-zephyr-workspace/modules/lib/golioth-firmware-sdk/examples/zephyr/hello
– west flash: rebuilding
Error: could not find CMAKE_PROJECT_NAME in Cache
FATAL ERROR: re-build in /Users/*********/golioth-zephyr-workspace/modules/lib/golioth-firmware-sdk/build failed (no --build-dir given)
I am using a MacOS Ventura with the command line prompt as my environment.
golioth_system: Failed to connect: -22
golioth_system: Failed to make CoAP request: -115
golioth_system: Failed to send sensor data to Golioth: -115
Unable to flash the hello example due to CMake errors
For the first issue, there could be multiple underlying causes. One possible reason is that if you are using a pre-shared key (PSK) for authentication, the PSK ID may have exceeded the default maximum length in the Golioth Firmware SDK. Please verify if your PSK ID is longer than 32 characters and, if so, reduce its length to see if this resolves the problem.
Based on the output log you provided, it appears that you are using the Can Asset Tracker Reference Design. I recommend building and flashing the reference design by following the instructions provided in the Building the Firmware section of the documentation.
Regarding the second issue, the error message:
Error: could not find CMAKE_PROJECT_NAME in Cache
indicates that CMake may not have been provided with a valid build directory. This often occurs if the west flash command is executed from an incorrect directory relative to the intended build directory. Please ensure that you are running the command from the appropriate directory.
Lastly, could you confirm the architecture of your host machine? Is it a 64-bit ARM (Apple Silicon) or x86_64? If you are using Apple Silicon, when following the instructions in the Installing the Zephyr SDK Toolchain section, did you replace x86_64 with aarch64?
@rprysork, the error code -115 corresponds to ENETDOWN which means that the network is down.
Can you confirm that your nRF9160 DK connects to the network using a Nordic sample?
For instance, you can use the at_client sample, which we used in our Troubleshooting IoT Cellular Connections blog post.
I was able to confirm that there are 32 digits within the the PSK. I used the advised Building the Firmware example you provided and I was successful, until I got to the “Build the Blinky Sample”. I could not get the Blinky West to build using the board name “NRF9160” that is supported according to the Blinky website, so I used the alternative build of flashing the boards with the “Hello World” example. The Hello World example did work, however, once I changed the directory back to Zephyr and tried to flash the board with the west command I got the following error message:
(.venv) @**-iMac zephyr % west flash
– west flash: rebuilding
ninja: no work to do.
FATAL ERROR: no runners.yaml found in /Users/********/zephyrproject/zephyr/build/zephyr. Either board qemu_x86/atom doesn’t support wes
I cannot get past this error, because it appears to be a requirement to west flash the board. Please advise the best course of action.
The architecture of my host machine is a x86_64.
Since you’ve already been working with the Zephyr training website and have access to an nRF9160 DK, it would be beneficial to complete the entire training and utilize Codespaces for building the projects.
Please note that the normal workflow of using west flash with a local development environment won’t work because the Codespaces container doesn’t have access to your local USB port. Use the workflow for downloading the image from Codespaces to your local machine as described in step 4 of Build in the Codespaces container.
I was able to flash the at_client, however, in the trouble shooting document it doesn’t tell me what “successful” is, only if the flash fails. The next part of the instructions " LTE Link Monitor" just tell me how to switch from LTE-M to NB-IoT with the configuration files. Does this step apply to what I need to accomplish. I was under the impression is for when the device is in a region where LTE-M is not supported. Sorry if I’ve gotten that wrong. I am able to run the commands in the Serial Terminal as instructed at this point.
I have browsed through the training, but I was unable to completely follow the steps as I am still not able to connect the LTE modem to Golioth. Should I just read through it before that issue is resolved.
As a side note I have been in contact with Nordic and opened a ticket for getting an error message when attempting to add the LTE Modem to their site. The representative just wanted my IMEI and PIN, but they haven’t responded since I opened the ticket last week.
I also failed to mention that I purchased this board and had an electrical engineer set it up and he didn’t have these issues. Could the information he used to set up the board somehow be interfering with my setup?
Hi Marko,
Is it possible that since I’m running this on an iMac Quad Core 3.4GHz I5 and the command is using the QEMU emulator (which includes Linux, Windows, Solaris, DOS, etc.) that it may be incompatible with my machine?
Is it possible that since I’m running this on an iMac Quad Core 3.4GHz I5 and the command is using the QEMU emulator (which includes Linux, Windows, Solaris, DOS, etc.) that it may be incompatible with my machine?
It is possible, but with limited information, it is hard to tell. Zephyr applications can be run using QEMU on macOS.
For example, you can build and run the Hello World sample using the x86 emulation board configuration (qemu_x86), with:
# From the root of the zephyr repository
west build -b qemu_x86 samples/hello_world
west build -t run
Regarding the nRF9160 DK issue, were you able to connect to a cellular tower and establish an internet connection? Can you confirm you have activated the SIM card?
Can you share more information on the work the electrical engineer did to set up the nRF9160 DK board?
Zephyr has a community Discord server where you can ask questions. Since your issues aren’t specifically related to Golioth, it’s better to seek help in a more relevant forum.
I am able to connect with to a cellular tower as of yet. I do have an internet connection and I also have activated the iBasis SIM card. However, the issues seems to be with Nordic looking into why I cannot add the nRF9160 DK to the nRF Connect website.
As for the engineer’s work. According to him he set up the device using the same follow-along instructions OBD-II / CAN Asset Tracker - nRF9160 DK Follow-Along Guide | Golioth Projects. Aside from that he told me that he only registered the device and SIM card with Nordic. Hope this helps.