Hello,

Just trying to understand all of the toolchains & SDKs involved, quite a steep learning curve so far with all the build tools, newbie question!

My understanding is that when using the CircuitDojo VSCode extension, doing Zephyr: setup & init repo, this not only creates a directory with the feather samples, but also installs the nRF SDK (inside the nrf directory), Zephyr tools, west, etc, and some other utilities…?

After this is done, or prior to this setup, must the user also manually setup the nRF toolchain + SDK via the Connect desktop app/official nRF Connect VSCode extension (afaik this is now Nordics recommended method of installing toolchains & SDK).

The docs here https://docs.circuitdojo.com/nrf9160-sdk-setup-linux.html and https://docs.circuitdojo.com/nrf9160-nrf-connect-desktop.html don’t specifically talk about manual installs/setups of these 2 hence the curiosity. I guess my question is more around how all these things are interacting with one another so that I can try and debug things with a better understanding.

    doggylizard My understanding is that when using the CircuitDojo VSCode extension, doing Zephyr: setup & init repo, this not only creates a directory with the feather samples, but also installs the nRF SDK (inside the nrf directory), Zephyr tools, west, etc, and some other utilities…?

    Yup it installs all dependencies including a copy of NCS

    doggylizard After this is done, or prior to this setup, must the user also manually setup the nRF toolchain + SDK via the Connect desktop app/official nRF Connect VSCode extension (afaik this is now Nordics recommended method of installing toolchains & SDK).

    No. The two don’t co-exist very well. I would use either or.

    doggylizard The docs here https://docs.circuitdojo.com/nrf9160-sdk-setup-linux.html and https://docs.circuitdojo.com/nrf9160-nrf-connect-desktop.html don’t specifically talk about manual installs/setups of these 2 hence the curiosity. I guess my question is more around how all these things are interacting with one another so that I can try and debug things with a better understanding.

    Manual setups are fraught with errors and frustrations. I found it was much easier to build an extension that does everything for you (that works for all flavors of Zephyr) than to deal with all the issues that come up with different operating systems, python and all associated dependencies, etc.

            jaredwolff Ok makes sense! I was indeed running into issues with the two co-existing, but was unsure whether due to trivial config errors or something more fundamental.
            Thanks!

              Terms and Conditions | Privacy Policy