flashing bootloader

RE: flashing bootloader

Sigurd Hellesvik — Tue, 04 Jan 2022 12:18:22 GMT

The build system will only load configuration files following a specific naming and structure.
Generally the build system is explained in Build and configuration system documentation.
MCUboot is a secondary image, built using multi-image build. This is documented in Image-specific variables under Multi-image builds.

For the statement that says the mcuboot.conf should be named as it is:

  # Note: The folder `child_image/<ACI_NAME>` is only need when configurations
  #       files must be used instead of the child image default configs.
  #       The append a child image default config, place the addetional settings
  #       in `child_image/<ACI_NAME>.conf`.

Regards,
Sigurd Hellesvik

RE: flashing bootloader

Tushar_V — Fri, 31 Dec 2021 05:59:05 GMT

Hi,

Thank you i am able to flash the app_update.bin file via nrf_USB ,

I have a doubt on when i changed to mcuboot.conf how did it work can u explain it to me

Regards

Tushar

RE: flashing bootloader

Sigurd Hellesvik — Thu, 30 Dec 2021 11:36:50 GMT

When I flash the zephyrsamples/bluetooth/hci_usb withadded MCUBOOT bootloader and connect both the USB connectors to my laptop, I can see two ACM ports available.

One will be the debugger

The ofther is from the nRF USB
This is the one which the bootloader can be reached from.

Have you programmed the hci_usb with bootloader and plugged in both USB cables?

Regards,
Sigurd Hellesvik

RE: flashing bootloader

Tushar_V — Thu, 30 Dec 2021 11:18:25 GMT

Hi,

It's /dev/ttyACM0 .

Regards

Tushar

RE: flashing bootloader

Sigurd Hellesvik — Thu, 30 Dec 2021 11:15:00 GMT

Which available ttyACM interfaces do you have available?

ls /dev/ttyACM*

Regards,
Sigurd Hellesvik

RE: flashing bootloader

Tushar_V — Thu, 30 Dec 2021 10:50:57 GMT

Hi Sigurd Hellesvik,

With your suggestion i was able to flash the bootloader but when i come step 31 and write this command

mcumgr --conntype serial --connstring "/dev/<your_serial_port_name>,baud=115200" image list.

it gives error nmp timeout in ubuntu

Regards

Tushar

RE: flashing bootloader

Sigurd Hellesvik — Thu, 30 Dec 2021 09:00:26 GMT

I forgot that you also need to rename the file inside the child_image folder to mcuboot to mcuboot.conf.
Then your folder structure will look like this:

To check that the settings are set correctly, you can do:

west build -b nrf52840dk_nrf52840 -–pristine -t mcuboot_menuconfig

and verify that the "Flash space reserved" as explained in step 10 is already set as what you set it to in the configuration.

Regards,
Sigurd Hellesvik

RE: flashing bootloader

Tushar_V — Thu, 30 Dec 2021 06:50:41 GMT

Hi,

when i dont put argument Dmcuboot_OVERLAY_CONFIG it gets build and then i flash it successfully

so i went RUNNING DFU PROCESS i have installed mcumgr and in when i do step no 27, i dont get the image that is shown in step no 28 of the below link.

devzone.nordicsemi.com/.../device-firmware-update-dfu-with-mcuboot-bootloader

Regards

Tushar

RE: flashing bootloader

Sigurd Hellesvik — Wed, 29 Dec 2021 13:04:05 GMT

I get the same error as you.

I suspect that this is due to some changes since v1.4.1, which the tutorial was made for.

To fix this now, just make a folder named child_image in your project, and move the "usb_cdc_acm_log_recovery.conf" to this folder.
Then you do not need the "Dmcuboot_OVERLAY_CONFIG" argument any more either.

Does this fix your issue?

Regards,
Sigurd Hellesvik

RE: flashing bootloader

Tushar_V — Wed, 29 Dec 2021 11:30:51 GMT

Hi,

iam using nrf sdk :1.7.1

toolchain:gcc-arm-none-eabi-10.3-2021.10

Regards

Tushar

RE: flashing bootloader

Sigurd Hellesvik — Tue, 28 Dec 2021 14:55:11 GMT

I will try to reproduce your issue.
But first: which version of the Toolchain are you using?

Regards,
Sigurd Hellesvik

RE: flashing bootloader

Tushar_V — Tue, 28 Dec 2021 12:40:02 GMT

Hi Sigurd Hellesvik,

I performed the above steps and ive set

CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000 and ive also increase this value

but it shows same above behaviour

Regards

Tushar

RE: flashing bootloader

Sigurd Hellesvik — Tue, 28 Dec 2021 09:30:26 GMT

Hi Tushar

The error you describe looks like the error in step 8 from the guide you link to:

"8. Observe the error statement:

This error message signifies that the MCUBoot partition in flash has overflowed which means that the size of the generated MCUBoot code is too big by 14556 bytes. To remedy this, we will adjust MCUBoot’s flash partition size so that MCUBoot is able to fit."

Try to perform step 9-14 to get a successful build.

Regards,
Sigurd Hellesvik