Visual Studio using forked nRF SDK

[responsible_duck]

Hello,

We need to use some fixes that aren't released yet in a version yet. Specifically, an MCUBoot fix: github.com/.../303

Is there a guide as to how to use forked version of MCUBoot with Visual Studio? Or is it only possible via west?

Thanks!

[Maria Gilje]

Hello,

Please note that there could be compatibility issues between your installed NCS version and the forked MCUboot repository.

You can use the extension UI to update NCS with new sources. This is how:

• Open NCS in VS Code.
• Verify that there is a "Manage west workspace" option in the nRF Connect for VS Code extension panel.
• Left click it and select "Open west manifest".
  • Find mcuboot under projects.
  • Replace the repo-path line with url: and the url to the forked MCUboot repository.
  • Replace the revision value with the full hash for the commit with the fix or a later one.
  • Save west.yml.
• In the extension panel: click "Manage west workspace" again and select "West update" in the pop-up menu.

I have tested that west update is successful with NCS v2.6.1, but I have not tested any mcuboot applications.

Best regards,

Maria

[responsible_duck]

Is there a way to do this without creating a west workspace? For example, can I navigate to my SDK directory nordic/ncs/v2.6.1 and modify the zephyr/west.yml file?

[Maria Gilje]

No, source control with the nRF Connect for VS Code extension depends on a west workspace. See the available functionality in the extension documentation here: https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/west_about.html. Note that the method from my previous reply is not an official feature for the extension.

If you don't want to use a west workspace, please see the relevant Zephyr documentation for west manifests here: https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/develop/west/manifest.html

Best regards,

Maria