building mcuboot as a separate .hex / .bin file

Hi

The MCUBoot child image build can be found in the folder build/mcuboot.
The hex file for only mcuboot is therefore located at build/mcuboot/zephyr/zephyr.hex.

Is this what you were looking for?

Regards,
Sigurd Hellesvik

Hello Sigurd Hellesvik,

Thanks, Actually this is what I was looking at.

In the attached project I am building DFU sample app provided by nordic for BL653: devzone.nordicsemi.com/.../ncs-dfu

I have 4 more questions:

1. In this project, at path "peripheral_lbs_BL653\build\zephyr", I am to understand that application build file is present at this location, Does this application build file have mcuboot code as well.?

2. At the path "peripheral_lbs_BL653\build\mcuboot\zephyr", I am to understand that mcuboot build file is present as you said..?

user106736 said:

build/mcuboot/zephyr/zephyr.hex

3. mcuboot zephyr.hex is being generated separately at the aforementioned path, Is it getting integrated into the application build file at path "peripheral_lbs_BL653\build\zephyr"...?

4. How can I flash this mcuboot build file found at the path "peripheral_lbs_BL653\build\mcuboot\zephyr" separately into the board..?

Thanks,

Ubaid

Hi

The merged.hex file is the file referenced in Multi-image builds, Default configuration:
"When building the child image from the source or using a prebuilt HEX file, the build system merges the HEX files of both the parent and child image, so that they can be programmed in one single step. This means that you can enable and integrate an additional image just by using the default configuration."

So:

build/zephyr/zephyr.hex: only application

build/mcuboot/zephyr/zephyr.hex: only mcuboot

build/zephyr/merged.hex: mcuboot+application

The "west flash" command will flash "build/zephyr/merged.hex" for multi-image builds, and "build/zephyr/zephyr.hex" for single image builds.

For images used for MCUBoot, see Using MCUboot in nRF Connect SDK.

Regards,
Sigurd Hellesvik

Hi

The merged.hex file is the file referenced in Multi-image builds, Default configuration:
"When building the child image from the source or using a prebuilt HEX file, the build system merges the HEX files of both the parent and child image, so that they can be programmed in one single step. This means that you can enable and integrate an additional image just by using the default configuration."

So:

build/zephyr/zephyr.hex: only application

build/mcuboot/zephyr/zephyr.hex: only mcuboot

build/zephyr/merged.hex: mcuboot+application

The "west flash" command will flash "build/zephyr/merged.hex" for multi-image builds, and "build/zephyr/zephyr.hex" for single image builds.

For images used for MCUBoot, see Using MCUboot in nRF Connect SDK.

Regards,
Sigurd Hellesvik

Hi Sigurd Hellesvik,

Thanks, that clears things for me.

My follow up question is can I flash mcuboot zephyr.hex on the board...?

user106736 said:

build/mcuboot/zephyr/zephyr.hex: only mcuboot

How do I update the mcuboot file on the board..?

Thanks

Hi

To make sure that I do not misunderstand your intention, I have a return question for this:

Why do you need to flash the bootloader alone?

Regards,
Sigurd Hellesvik

Hello Sigurd Hellesvik,

user106736 said:

Why do you need to flash the bootloader alone?

Simply put, It is the way my product is supposed to work, There is an architecture already laid out.

As per that I need to flash mcuboot file independently when the requirement is so.
Likewise flash application file independently when the requirement is so.

Hence kindly suggest how I can flash mcuboot build file on my nordic board.

Thanks, 

Hello Sigurd Hellesvik,

user106736 said:

Why do you need to flash the bootloader alone?

Simply put, It is the way my product is supposed to work, There is a software architecture already laid out.

As per that I need to flash mcuboot file independently when the requirement is so.
Likewise flash application file independently when the requirement is so.

Hence kindly suggest how I can flash mcuboot build file on my nordic board.

Thanks, 

Hi

You can update the bootloader in multiple ways:

1, Using nrfjprog via an attached debugger

2. Using serial recovery

3. Using an SMP Server

For alternative 2 and 3, you will need another bootloader to run before MCUBoot. This is the nRF Secure Immutable Bootloader (NSIB).
Then you must add MCUBoot as an Upgradable Bootloader.

I made a sample on how to do this using the SMP server for this case.

Regards,
Sigurd Hellesvik