nRF Connect SDK + MCUBoot fails to load the application

RE: nRF Connect SDK + MCUBoot fails to load the application

ovrebekk — Tue, 16 Nov 2021 14:23:42 GMT

Good to hear you figured it out. We test with JLink only, so that is what I would recommend (if you buy a DK it comes with a built in JLink programmer that you can also use to flash your external board).

Best regards
Torbjørn

RE: nRF Connect SDK + MCUBoot fails to load the application

yosmoc — Tue, 16 Nov 2021 10:50:43 GMT

Hi,

Thanks for your answer.

I switch to using the nrfjprog (jLink), it starts working.

I didn't dig into what is the problem in the black magic probe, but it seems to skip to write the bootloader area in the merged.hex file.

Thanks for your support.

RE: nRF Connect SDK + MCUBoot fails to load the application

ovrebekk — Thu, 11 Nov 2021 15:43:46 GMT

I tried to reproduce the issue here, but for me it works fine.

I simply copied the blinky sample from Zephyr, and set CONFIG_BOOTLOADER_MCUBOOT=y. After flashing the nRF52DK I can see that the program starts as expected, and I see the standard output from mcuboot (the "Example started" message I added to the example myself, just to make it clear that the application was running):

*** Booting Zephyr OS build v2.6.99-ncs1-1  ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0xc000
ÿ*** Booting Zephyr OS build v2.6.99-ncs1-1  ***
Example started...

Could you try to flash the board using nrfjprog instead?

To do so simply run the following commands from the command line:

nrfjprog --recover
nrfjprog -e
nrfjprog --program merged.hex
nrfjprog -r

Best regards
Torbjørn

RE: nRF Connect SDK + MCUBoot fails to load the application

yosmoc — Wed, 10 Nov 2021 15:52:14 GMT

I would strongly recommend getting an nRF52DK in case you are planning to do extended development for the nRF52832.

I assume you have been able to run some standard examples without MCUBoot running?

Yes, we have already had production-ready firmware without MCUBoot. I have also tested some standard examples (hello, dtm, NFC and so on) and works well.

I will try to reproduce the issue you are seeing tomorrow and get back to you.

Thanks. I will wait your answer.

And as a side note, if you haven't checked out Jimmy Wong's blog on MCUBoot already, I would highly recommend it.

I will check, thanks.

RE: nRF Connect SDK + MCUBoot fails to load the application

ovrebekk — Tue, 09 Nov 2021 21:22:51 GMT

I would strongly recommend getting an nRF52DK in case you are planning to do extended development for the nRF52832.

I assume you have been able to run some standard examples without MCUBoot running?

I will try to reproduce the issue you are seeing tomorrow and get back to you.

And as a side note, if you haven't checked out Jimmy Wong's blog on MCUBoot already, I would highly recommend it.

[quote user=""] supposed merged.hex includes the bootloader. Is it correct?[/quote]

That is correct.

Best regards
Torbjørn

RE: nRF Connect SDK + MCUBoot fails to load the application

yosmoc — Fri, 05 Nov 2021 15:03:27 GMT

Hi,

Yes, I use the custom board based on nRF52832 QFAA, but I don't think this is due to the custom board. Unfortunately, I don't have a standard board now.

The procedure I create the custom board are

1. Create the custom board in VSCode + nRF Connect for VS Code version v2021.11.109

2. modify nrf52832.dts. I just add uart0 for debugging.

// Copyright (c) 2021 Nordic Semiconductor ASA
// SPDX-License-Identifier: Apache-2.0

/dts-v1/;
#include <nordic/nrf52832_ciaa.dtsi>

/ {
	model = "nrf52832";
	compatible = "nrf52832";

	chosen {
		zephyr,console = &uart0;
		zephyr,shell-uart = &uart0;
		zephyr,uart-mcumgr = &uart0;
		zephyr,bt-mon-uart = &uart0;
		zephyr,bt-c2h-uart = &uart0;
		zephyr,sram = &sram0;
		zephyr,flash = &flash0;
		zephyr,code-partition = &slot0_partition;
	};
};

&uart0 {
	status = "okay";
	compatible = "nordic,nrf-uart";
	current-speed = <115200>;
	tx-pin = <12>;
	rx-pin = <11>;
	rts-pin = <14>;
	cts-pin = <13>;
};

&flash0 {
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x0 0xc000>;
		};
		slot0_partition: partition@c000 {
			label = "image-0";
			reg = <0xc000 0x32000>;
		};
		slot1_partition: partition@3e000 {
			label = "image-1";
			reg = <0x3e000 0x32000>;
		};
		scratch_partition: partition@70000 {
			label = "image-scratch";
			reg = <0x70000 0xa000>;
		};
		storage_partition: partition@7a000 {
			label = "storage";
			reg = <0x7a000 0x6000>;
		};
	};
};

I can run the application without a MCUBoot bootloader with this board.

Here is my custom board configuration.

devzone.nordicsemi.com/.../nrf52832.tar.gz

Thanks,

RE: nRF Connect SDK + MCUBoot fails to load the application

ovrebekk — Fri, 05 Nov 2021 14:19:22 GMT

You mention that you use a custom board based on the nRF52832?

Do you have a standard nRF52DK available so you can compare?
If so, is the issue the same?

Best regards
Torbjørn