• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 95 subscribers
  • Views 533 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 294672
Options

MCUboot from different branch

Riccardo Gaiati

Hi,

i am interested to get the MCUBoot version developed in a specific branch different from the one present in the official SDK (i have the 1.9.1).

Is there a proper way to get it via west ?

Thanks in advance !

Kind regards

Riccardo

Parents
  • 0

    Hello Riccardo,

    You may be able to change a single line in Nordic's sdk-nrf manifest file. The file I'm speaking of for me lives locally in [west_workspace]/nrf/west.yml.  I happen to be using Nordics nrf SDK version 1.6.1.  In Nordic's github repository I find this manifest file at:

      *  github.com/.../west.yml

    The older sdk-nrf manifest file I have has this excerpt to select and download 1.6.1's chosen version of MCUBoot:

    106     # NCS repositories.
107     #
108     # Some of these are also Zephyr modules which have NCS-specific
109     # changes.
110     - name: mcuboot
111       repo-path: sdk-mcuboot
112       revision: v1.7.99-ncs2

    One caveat to this suggestion, I haven't manually adjusted the manifest for either sdk-nrf nor Nordic's fork of Zephyr RTOS project.  I could do this, and then I would issue a `west update` command to upgrade or downgrade those repositories to their new versions.  But I'm not sure whether my local change to nrf-sdk manifest will persist.  That is, if I update nrf-sdk will my local changes be overwritten?  I think they may not, because I have made local changes to a couple of Zephyr fork source files, and those changes are not overwritten when I `west update`.

    And just a mention, local changes I make in Zephyr or other third party repos I am responsible to remember and keep track of them.  These are never for long term development, as I can't keep such changes under my own revision control.  They're usually just for sanity checks and short short term tests.

    Hope this can help you, Riccardo!

    - Ted

Reply
  • 0

    Hello Riccardo,

    You may be able to change a single line in Nordic's sdk-nrf manifest file. The file I'm speaking of for me lives locally in [west_workspace]/nrf/west.yml.  I happen to be using Nordics nrf SDK version 1.6.1.  In Nordic's github repository I find this manifest file at:

      *  github.com/.../west.yml

    The older sdk-nrf manifest file I have has this excerpt to select and download 1.6.1's chosen version of MCUBoot:

    106     # NCS repositories.
107     #
108     # Some of these are also Zephyr modules which have NCS-specific
109     # changes.
110     - name: mcuboot
111       repo-path: sdk-mcuboot
112       revision: v1.7.99-ncs2

    One caveat to this suggestion, I haven't manually adjusted the manifest for either sdk-nrf nor Nordic's fork of Zephyr RTOS project.  I could do this, and then I would issue a `west update` command to upgrade or downgrade those repositories to their new versions.  But I'm not sure whether my local change to nrf-sdk manifest will persist.  That is, if I update nrf-sdk will my local changes be overwritten?  I think they may not, because I have made local changes to a couple of Zephyr fork source files, and those changes are not overwritten when I `west update`.

    And just a mention, local changes I make in Zephyr or other third party repos I am responsible to remember and keep track of them.  These are never for long term development, as I can't keep such changes under my own revision control.  They're usually just for sanity checks and short short term tests.

    Hope this can help you, Riccardo!

    - Ted

Children
Related
Terms of service