specify MCUBOOT project or build out of ncs repo

[Varouzan]

Hello,

At this point I have been able to successfully customize and run the mcuboot procect.. Mcuboot is successfully built and linked with my app.

However I am would want to move the bootloader project out of the ncs repo and into my custom git repo. 

 

1. Is there a way to point the compiler/nrf connect SDK to a different project to build as the bootloader.

alternatively

2.I tried using configurations:

CONFIG_BOOTLOADER_MCUBOOT=y,

CONFIG_MCUBOOT_BUILD_STRATEGY_USE_HEX_FILE=y,

CONFIG_MCUBOOT_HEX_FILE="<boot-loader hex location>/zephyr.hex"

However, I get compiler errors  'PM_MCUBOOT_PRIMARY_ID' undeclared and 'PM_MCUBOOT_SECONDARY_ID' undeclared.

I would appreciate some feedback on how to go forwards with any of the two approaches.

[Håkon Alseth]

Hi,

 

the partition manager requires to know a bit more than just the .hex location (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/scripts/partition_manager/partition_manager.html#build-system), so there might be easier to either fork mcuboot (and point to your remote + repo in west.yml, see examples in west documentation), or if you only require configuration or overlay changes; this can be done in the application space.

 

What are your changes? Do you require source file changes, or is this purely on a .conf / .overlay level?

If yes, then you can add the following to your applications CMakeLists.txt, and add a mcuboot.conf file:

https://devzone.nordicsemi.com/f/nordic-q-a/66210/change-mcuboot_menuconfig-configuration/270799#270799

 

Kind regards,

Håkon

[Varouzan]

I have made some source code edits in main.c and also config edits in proj.conf.

So how would I go about setting up the partition manager to use a compiled .hex file then?

Something along these lines:

set_property(
  GLOBAL PROPERTY
  app_PM_HEX_FILE # Must match "*_PM_HEX_FILE"
  ${PROJECT_BINARY_DIR}/signed.hex
)

Do I need to add some sort of pm.yml file in my root app directory for this?

Which example in https://docs.zephyrproject.org/latest/guides/west/manifest.html#manifest-files showcases the creation of a fork? How would I go about doing that?

[Håkon Alseth]

Hi,

 

I would recommend that you fork the repo in this case.

If you create your project as per section 2.1.2 in this guide:

https://devzone.nordicsemi.com/nordic/nrf-connect-sdk-guides/b/getting-started/posts/nrf-connect-sdk-tutorial---part-2-ncs-v1-3-0

 

This is essentially copying the ncs/nrf/west.yml to your own project, and initializing it via west.

 

I'm using mcuboot upstream as an example, but you can change this to your own fork of mcuboot if desired.

You can point to a remote by first defining it in west.yml:

  remotes:
    ...
    - name: mcuboot-upstream
      url-base: https://github.com/mcu-tools
    ...

 

Then add/adjust the mcuboot under the project section:

    - name: mcuboot
      remote: mcuboot-upstream
      repo-path: mcuboot
      revision: v1.6.0
      path: bootloader/mcuboot

 

Kind regards,

Håkon