if (fih_not_eq(fih_rc, FIH_SUCCESS)) { BOOT_LOG_ERR("Unable to find bootable image"); mcuboot_status_change(MCUBOOT_STATUS_NO_BOOTABLE_IMAGE_FOUND); FIH_PANIC; } BOOT_LOG_INF("Bootloader chainload address offset: 0x%x", rsp.br_image_off);
if (fih_not_eq(fih_rc, FIH_SUCCESS)) { BOOT_LOG_ERR("Unable to find bootable image"); mcuboot_status_change(MCUBOOT_STATUS_NO_BOOTABLE_IMAGE_FOUND); FIH_PANIC; } BOOT_LOG_INF("Bootloader chainload address offset: 0x%x", rsp.br_image_off);
Hi
Where do you set breakpoints that result in this FIH_PANIC? I think you're setting breakpoints that interferes with the check where this is from (the init of the boot console and waiting for the boot image check to finish). You shouldn't set breakpoints before the image is booted and application is up and running properly.
Best regards,
Simon
Hi
Where do you set breakpoints that result in this FIH_PANIC? I think you're setting breakpoints that interferes with the check where this is from (the init of the boot console and waiting for the boot image check to finish). You shouldn't set breakpoints before the image is booted and application is up and running properly.
Best regards,
Simon
There didn't seem to be any specific points, sometimes breakpoints in the same points that used to work before also started to cause this behaviour. However, it somehow seems to be fixed for me (perhaps because I since migrated to version 2.2.0).
Hm, sounds strange, but I'm glad it's no longer an issue for you, let us know if you see it again and how to reproduce it on our end so we can investigate if necessary.
Best regards,
Simon