I am using the MCUboot SDK example project mcuboot_opensource on the i.MX RT1052 EVKB board.
To verify that the bootloader correctly jumps to the application image, I performed the following steps:
I built the mcuboot_opensource bootloader example and flashed it at 0x60000000 (QSPI flash base address).
I then built the Hello World application with the linker start address 0x60040000, which is the primary slot address used when MCUboot is present.
I signed the application image using the imgtool command as mentioned in the MCUboot README.
I flashed the signed image at 0x60040000 using SEGGER J-Link.
When running the bootloader, I get the following logs:
Bootloader Version 2.1.0
Non-optimal sector distribution, slot0 has 6 usable sectors (8 assigned) but slot1 has 8 assigned
Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
Boot source: none
Image index: 0, Swap type: none
Bootloader chainload address offset: 0x40000
Reset_Handler address offset: 0x40200
Jumping to the image
According to the log, the bootloader attempts to jump to the application image. However, the application does not start, and the expected output ("Hello World!") is not printed.
I also tried the LED blinky application, but the behavior is the same.
What could be the possible reasons why the bootloader jumps to the image but the application does not run?
Hi @Bhumika18 ,
Thank you so much for your interest in our products and for using our community.
Please open the keys.c file in your mcuboot_opensource project and check which signing algorithm is defined there.
If the issue is caused by an incorrect signing method, update the signing command accordingly as described in the README file of the project.
Wish it helps you
Best Regards
MayLiu