Example of CONFIG_MCUBOOT_BUILD_STRATEGY_USE_HEX_FILE usage

[flaik-wayne]

Hi,

I have read the thread here:  specify MCUBOOT project or build out of ncs repo which implies that this config option might not work?

Does it work? I would like to build mcuboot and then always use the same binary for future releases - this way, all our devices will be using the same copy of mcuboot.

I first built using the default strategy, then I copied build/mcuboot/zephyr/zephyr.hex to eg my home directory.

Then I set

CONFIG_MCUBOOT_BUILD_STRATEGY_USE_HEX_FILE=y
CONFIG_MCUBOOT_HEX_FILE="/home/wayne/mcuboot.hex"

Then I deleted build directory and rebuilt it as before - it "builds", but the resulting build is broken.

Does this work? How should it be setup? I am using NCS v1.8.0 due to AT&T compliance.

[AHaug]

Hi,

Based on some feedback after discussing this with my colleague we landed on a couple of points we need to get more information about

which implies that this config option might not work?

The configuration exists here, so it should work.

Does it work?

It should work yes, but how to do it is not straight forward.  As stated in the case you linked, it is stated "the partition manager requires to know a bit more than just the .hex location". As far as I can see you've only given the pm the hex location and some more setup is required.

Then I deleted build directory and rebuilt it as before - it "builds", but the resulting build is broken.

Could you explain what you mean by "broken" by supplying a build log?

How should it be setup?

I've asked around and we do not have any samples available for this, other than using either similarly looking cases on devzone and our doc-api. 

Kind regards,
Andreas