This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NordicPlayground vs Rallare git repos

Can somebody explain the differences between the 2 git repos at NordicPlayground and Rallare regarding the nRF9160DK? Rallare has more samples of interest to me but I've setup everything using NordicPlayground and the 2 repos don't seem to play nicely together.

Parents
  • Hi,

     

    I'm glad to hear that the samples are of interest to you. Most of them are made based on what people in this forum struggles with when it comes to running NCS and zephyr on the nRF9160.

    So, what's the difference between these two repo's?

    I have forked the fw-nrfconnect-nrf repo, then added commits on top (each commit being one sample). I try to rebase it now-and-then, just to keep in sync with the original repo, but there's some open issues inherited over time, with this one being a crucial one:

    https://github.com/Rallare/fw-nrfconnect-nrf/issues/1

     

    Simplest way to use the samples:

    * Clone NCS as per the documentation

    * Clone my fork in a different location

    * Copy the sample of interest to the NCS structure and build it like any other sample in "nrf" repo.

    The more advanced and the "git way" of adding forks:

    * Clone NCS as per the documentation

    * Add my fork as a remote (see here for details)

    * git fetch <whatever-you-named-my-fork-remote>

    * git checkout nrf9160_samples

     

    The going-forward plan is to create pull-requests to contribute the samples back to the original nrf repo.

     

    Cheers,

    Håkon

Reply
  • Hi,

     

    I'm glad to hear that the samples are of interest to you. Most of them are made based on what people in this forum struggles with when it comes to running NCS and zephyr on the nRF9160.

    So, what's the difference between these two repo's?

    I have forked the fw-nrfconnect-nrf repo, then added commits on top (each commit being one sample). I try to rebase it now-and-then, just to keep in sync with the original repo, but there's some open issues inherited over time, with this one being a crucial one:

    https://github.com/Rallare/fw-nrfconnect-nrf/issues/1

     

    Simplest way to use the samples:

    * Clone NCS as per the documentation

    * Clone my fork in a different location

    * Copy the sample of interest to the NCS structure and build it like any other sample in "nrf" repo.

    The more advanced and the "git way" of adding forks:

    * Clone NCS as per the documentation

    * Add my fork as a remote (see here for details)

    * git fetch <whatever-you-named-my-fork-remote>

    * git checkout nrf9160_samples

     

    The going-forward plan is to create pull-requests to contribute the samples back to the original nrf repo.

     

    Cheers,

    Håkon

Children
  • Thanks for the explanation. I have already had some success with option #1 (copy files), though I often encounter various errors with either cmake or ninja, just in general. I suspect it's related to the git tag I have checked out. How do I know which combination of tags to use for the various ncs components? The latest info I found is in the v0.3.0 release notes which tells me the tags, but they don't have the newer things I want to play with (modem_info is my latest stumbling block)

  • Without knowing the errors that you see, it is always good to clear your build folder prior to reconfiguring (cmake .. -DBOARD=nrf9160_pca10090ns, or nrf9160_pca10090 if you're using the v0.3 tag).

    What errors are you seeing?

     

    miked531 said:
    How do I know which combination of tags to use for the various ncs components?

    If you are using the v0.3 tag, you should checkout the different repos (nrf, zephyr, nrfxlib) with the tags described in the nRF getting started assistant.

    For the future, there's a tool called "west" that will ensure that you pull the correct revisions.

     

    Kind regards,

    Håkon

Related