This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

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?!?!?

Parents
  • 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

  • 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.

    Slight smile

    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!

Reply
  • 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.

    Slight smile

    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!

Children
No Data
Related