"Couldn't find Zephyr root" both SEGGER and VsCode

[Mr.Newlove]

Hello all,

Lost my VM that had a working installation and just setting everything back up.

After installing SDK 1.8.0 and all of the extensions for VsCode. Now both SEGGER and VSCode cannoot find the Zephry root and I cannot find it on disk?

This was not a problem in the past, any ideas?

Thanks

Edit: Another problem... like all of the examples are missing?? searched for serial_lte_modem and it comes up with nothing. Even just searching serial, or application comes up with nothing useful?

Edit2: I installed the most recent 3 releases and none have a zephyr folder anymore?!?!?

[Albrecht Markus Schellenberger]

Thanks Kyle!

Mr.Newlove said:

If I compile in bash as you asked it works as well:

Point 1:

It looks like you are able to build the Serial LTE modem application with you general toolchain setup, then.

Mr.Newlove said:

Sorry I didn't know you wanted to see the output for the build that does work for the basic DK board, in VSCode I get:

And it even seems to me that it works in VS Code as well, based on the build log you shared.

Point 2:

Mr.Newlove said:

Just for some more data, trying the same west command but for circuitdojo_feather_nrf9160ns:

However, that you are not able to build the Serial LTE modem for the circuitdojo_feather_nrf9160_ns is a completely different issue, which has nothing to do with VS Code. First of all, from NCS v1.7.x all non-secure boards are written as “_ns”.

Officially, only the nRF9160 DK is supported for the Serial LTE modem. But you can modify the application and thus make it buildable for the circuitdojo_feather_nrf9160_ns as well. To do so, you have to create a file named circuitdojo_feather_nrf9160_ns.overlay in the root folder of the Serial LTE modem application and fill it with the following content:

&uart0 {
    rts-pin = < 0x1b >;
    cts-pin = < 0x1a >;
};

The pin assignment is taken from the nRF9160 DK, so the values do not necessarily have to make sense.

Regards,

Markus

[Mr.Newlove]

Albrecht Markus Schellenberger said:

However, that you are not able to build the Serial LTE modem for the circuitdojo_feather_nrf9160_ns is a completely different issue, which has nothing to do with VS Code. First of all, from NCS v1.7.x all non-secure boards are written as “_ns”.

Well, that is embarrassing, i remember reading that but never even noticed I was missing the "_" out of habit. Now it compiles with my backup overlay file. I will start working on the GPS and cellular location functioning with our board.

Furthermore, for the basic custom board I was trying to get working, I was trying to define uart0 in the dts file. But I was curious if it was just the fact I didn't add the "_ns" to the end of it, but that didn't work either.

Error is quite different though...

> Executing task: nRF Connect: Build serial_lte_modem_simpletest/build (active) <

Building serial_lte_modem_simpletest
west build --build-dir c:\ncs\MyApps\serial_lte_modem_simpletest\build c:\ncs\MyApps\serial_lte_modem_simpletest

ninja: error: loading 'build.ninja': The system cannot find the file specified.

FATAL ERROR: command exited with status 1: 'c:\ncs\v1.8.0\toolchain\opt\bin\cmake.EXE' --build 'c:\ncs\MyApps\serial_lte_modem_simpletest\build'
The terminal process terminated with exit code: 1.

Terminal will be reused by tasks, press any key to close it.

I will continue working with the feather board config for now since it worked fine with our custom board up until now.

THANKS!

[Mr.Newlove]

Bit infuriating, after screwing around most of the day... there is something wrong with the VS Code plugin for loading the nrf9160 device?

If I click erase and flash in VS Code the FW never works, but loading the same hex file into the stand-alone programmer works just fine. I bet this was my entire day wasted on trying to figure out what I have wrong in my config files just to find out the programmer in the VS Code extension is just broken for loading the board? I tried even removing all build configs and starting over with just 1 and it still fails.

https://youtu.be/VRO4jweSwBY

Think I might be ok now, can you report the problem with the programming extension?

Thanks,

Kyle

[Albrecht Markus Schellenberger]

Hello Kyle,

Mr.Newlove said:

Think I might be ok now, can you report the problem with the programming extension?

I’m not able to reproduce the problem you are facing and my best guess at the moment is, that it probably is more of an interface than VS Code issue. Could you do me a favour and run the following command in the bash?

usern@user-ubu:~$ nrfjprog --version
nrfjprog version: 10.15.1 external
JLinkARM.dll version: 7.58b

It would be interesting to know for me which version of the nRF Command Line Tools you are currently operating with.

Mr.Newlove said:

Furthermore, for the basic custom board I was trying to get working, I was trying to define uart0 in the dts file. But I was curious if it was just the fact I didn't add the "_ns" to the end of it, but that didn't work either.

Error is quite different though...

Regarding this problem: that is a little bit hard to say as “The system cannot find the file specified” unfortunately doesn’t tell us to much (I love this error message ;-)). Where are you storing the board files and how does the structure in the root folder of the board look like?

Regards,

Markus

[Mr.Newlove]

PS C:\ncs\MyApps\serial_lte_modem_uart0_gps> nrfjprog --version
nrfjprog version: 10.15.1 external
JLinkARM.dll version: 7.58b

Albrecht Markus Schellenberger said:

Regarding this problem: that is a little bit hard to say as “The system cannot find the file specified” unfortunately doesn’t tell us to much (I love this error message ;-)). Where are you storing the board files and how does the structure in the root folder of the board look like?

Yea, pretty non-specific. What I have been doing is creating a folder in the same project called "Boards" and then creating a new board called "basic_serial_modem_ns" using the board wizard. I can record a video of this whole process tomorrow if that helps?

Another issue I ran into today is I can't seem to get the GPS to actually report a location, but I was waiting until our fully assembled boards to show up since the one I am working with I hand-assembled and I have had nothing but issues because its really hard to get a perfect solder job by hand with the 9160 chip