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

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

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

    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

Related