flashing bootloader

[Tushar_V]

Hi All,

i am using the below link to flash the bootloader

https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/device-firmware-update-dfu-with-mcuboot-bootloader

but it gives me this error when i build

[199/206] Linking C executable zephyr/zephyr_prebuilt.elf
FAILED: zephyr/zephyr_prebuilt.elf zephyr/zephyr_prebuilt.map /home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build/mcuboot/zephyr/zephyr_prebuilt.map
: && ccache /home/user/gnuarmemb/gnu-arm-eabi/bin/arm-none-eabi-gcc   zephyr/CMakeFiles/zephyr_prebuilt.dir/misc/empty_file.c.obj -o zephyr/zephyr_prebuilt.elf  zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj  -fuse-ld=bfd  -Wl,-T  zephyr/linker_zephyr_prebuilt.cmd  -Wl,-Map=/home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build/mcuboot/zephyr/zephyr_prebuilt.map  -Wl,--whole-archive  app/libapp.a  zephyr/libzephyr.a  zephyr/arch/common/libarch__common.a  zephyr/arch/arch/arm/core/aarch32/libarch__arm__core__aarch32.a  zephyr/arch/arch/arm/core/aarch32/cortex_m/libarch__arm__core__aarch32__cortex_m.a  zephyr/arch/arch/arm/core/aarch32/mpu/libarch__arm__core__aarch32__mpu.a  zephyr/lib/libc/minimal/liblib__libc__minimal.a  zephyr/lib/posix/liblib__posix.a  zephyr/soc/arm/common/cortex_m/libsoc__arm__common__cortex_m.a  zephyr/soc/arm/nordic_nrf/nrf52/libsoc__arm__nordic_nrf__nrf52.a  zephyr/drivers/gpio/libdrivers__gpio.a  zephyr/drivers/flash/libdrivers__flash.a  zephyr/drivers/serial/libdrivers__serial.a  modules/nrf/lib/fprotect/lib..__nrf__lib__fprotect.a  modules/nrf/lib/fatal_error/lib..__nrf__lib__fatal_error.a  modules/nrf/drivers/hw_cc310/lib..__nrf__drivers__hw_cc310.a  modules/mcuboot/boot/bootutil/zephyr/libmcuboot_util.a  modules/hal_nordic/nrfx/libmodules__hal_nordic__nrfx.a  modules/segger/libmodules__segger.a  -Wl,--no-whole-archive  zephyr/kernel/libkernel.a  -L"/home/user/gnuarmemb/gnu-arm-eabi/bin/../lib/gcc/arm-none-eabi/10.3.1/thumb/v7e-m+fp/hard"  -L/home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build/mcuboot/zephyr  -lgcc  zephyr/arch/common/libisr_tables.a  /home/user/gireesha/workspace/source/gn/ncs/nrfxlib/crypto/nrf_cc310_platform/lib/cortex-m4/hard-float/no-interrupts/libnrf_cc310_platform_0.9.11.a  -mcpu=cortex-m4  -mthumb  -mabi=aapcs  -mfpu=fpv4-sp-d16  -Wl,--gc-sections  -Wl,--build-id=none  -Wl,--sort-common=descending  -Wl,--sort-section=alignment  -Wl,-u,_OffsetAbsSyms  -Wl,-u,_ConfigAbsSyms  -nostdlib  -static  -no-pie  -Wl,-X  -Wl,-N  -Wl,--orphan-handling=warn  /home/user/gireesha/workspace/source/gn/ncs/nrfxlib/crypto/nrf_cc310_bl/lib/cortex-m4/hard-float/no-interrupts/libnrf_cc310_bl_0.9.12.a && cd /home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build/mcuboot/zephyr && /usr/bin/cmake -E echo
/home/user/gnuarmemb/gnu-arm-eabi/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/bin/ld.bfd: zephyr/zephyr_prebuilt.elf section `text' will not fit in region `FLASH'
/home/user/gnuarmemb/gnu-arm-eabi/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/bin/ld.bfd: region `FLASH' overflowed by 13864 bytes
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
[198/213] Linking C executable zephyr/zephyr_prebuilt.elf

[199/213] Generating isr_tables.c, isrList.bin
FAILED: modules/mcuboot/mcuboot_subimage-prefix/src/mcuboot_subimage-stamp/mcuboot_subimage-build mcuboot/zephyr/zephyr.hex mcuboot/zephyr/zephyr.elf /home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build/modules/mcuboot/mcuboot_subimage-prefix/src/mcuboot_subimage-stamp/mcuboot_subimage-build /home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build/mcuboot/zephyr/zephyr.hex /home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build/mcuboot/zephyr/zephyr.elf
cd /home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build/mcuboot && /usr/bin/cmake --build . --
[202/213] Generating dev_handles.c
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /usr/bin/cmake --build /home/user/gireesha/workspace/source/gn/ncs/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/build

Regards

Tushar

[Sigurd Hellesvik]

Hi

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

Regards,
Sigurd Hellesvik

[Tushar_V]

Hi,

iam using nrf sdk :1.7.1

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

Regards

Tushar

[Sigurd Hellesvik]

Hi

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

[Tushar_V]

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

[Sigurd Hellesvik]

Hi

Which available ttyACM interfaces do you have available?

ls /dev/ttyACM*

Regards,
Sigurd Hellesvik

[Tushar_V]

Hi,

It's  /dev/ttyACM0 .

Regards

Tushar

[Sigurd Hellesvik]

Hi

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

[Tushar_V]

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

[Sigurd Hellesvik]

Hi

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