Unable to find bootable image

[Learner]

Hello,

From time to time I am getting the error "Unable to find bootable image" when I start a debug session in SES-NE v5.60.

FIH_CALL(boot_go, fih_rc, &rsp);
if (fih_not_eq(fih_rc, FIH_SUCCESS)) {
BOOT_LOG_ERR("Unable to find bootable image");
FIH_PANIC;
}

So, I deleted the whole content of the build folder and re-built the solution and produced a new merged,hex file. But the error persists. If I keep erasing/rebuilding the solution eventually I can start the debug session. Sometimes it takes many retries before it starts working again. I am wasting a lot of precious time that I cannot afford to waste.

Could someone please help sort this problem out ?

Why is this happening randomly?

What can be done to prevent it from happening?

If it cannot be prevented then how can it be fixed without wasting a long time on rebuilding the solution many times?

Thank you.

Kind regards

Mohamed

[liteyear]

Oh boy, there goes a couple of days. This is still an issue with ncs 2.5.2 in VSCode.

The root cause is indeed the extra breakpoints. Thank you, thank you for reporting that. It was so elusive!

I can confirm that adding CONFIG_BOOT_VALIDATE_SLOT0=n to child_image/mcuboot.conf eliminates the issue. Seems to me to be only upside to using that over the _ONCE variant. Now to ensure I don't forget to remove it for non debug builds! If only the "file suffixes" feature was as useful as build configurations used to be for every other IDE...