"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]

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