Unable to find bootable image

RE: Unable to find bootable image

liteyear — Thu, 13 Jun 2024 15:27:08 GMT

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...

RE: Unable to find bootable image

Einar Thorsrud — Tue, 30 May 2023 13:19:40 GMT

Perhaps you can use CONFIG_BOOT_VALIDATE_SLOT0_ONCE? Then the image is only validated on the first boot, but validation is skipped after that.

RE: Unable to find bootable image

Martin — Mon, 29 May 2023 16:18:24 GMT

I have the same problems.

I think the problem is associated with the debug probe (Segger J-LInk). These probes have some number of hardware breakpoints (two?) and all other breakpoints will modify the flash with a software breakpoint.
If one starts the application with more active breakpoints than provided in hardware the hash of the application is not the same and the application is not valid and will not be loaded.

So the question is: how to compile MCUBOOT/TFM without the firmware hash check?
Or is there another way to avoid it?

RE: Unable to find bootable image

mexco — Fri, 27 Jan 2023 12:50:33 GMT

I will test in my present project on VSC and face same problem just from a week. After removing all breakpoints, I shall test and tell.

RE: Unable to find bootable image

Learner — Fri, 27 Jan 2023 11:19:21 GMT

Hi,

Sorry I have just seen your message.

Glad you found the root cause.

It is strange that the number of breakpoints can cause the bootloader problems finding the bootable image.

RE: Unable to find bootable image

Earthworn1 — Thu, 26 Jan 2023 14:44:10 GMT

Okay i fixed it. The problem are to many breakpoints

RE: Unable to find bootable image

Earthworn1 — Thu, 26 Jan 2023 14:11:15 GMT

I got the Error again.

I only get the error when using mbedtls.

I add following Configs and debugging isn't possible anymore.

CONFIG_ANJAY_COMPAT_MBEDTLS=y

CONFIG_NORDIC_SECURITY_BACKEND=n

CONFIG_OBERON_BACKEND=n

CONFIG_MBEDTLS_TLS_LIBRARY=y

CONFIG_MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG=n

CONFIG_MBEDTLS_ENTROPY_C=y

CONFIG_MBEDTLS_CIPHER_MODE_CBC=y

CONFIG_MBEDTLS_CCM_C=y

CONFIG_MBEDTLS_CTR_DRBG_C=y

CONFIG_MBEDTLS_LEGACY_CRYPTO_C=y

CONFIG_MBEDTLS_PK_WRITE_C=y

CONFIG_MBEDTLS_DHM_C=y

CONFIG_MBEDTLS_ECP_C=y

CONFIG_MBEDTLS_ECP_DP_SECP384R1_ENABLED=y

Do you also use MBEDTLS?

RE: Unable to find bootable image

Learner — Fri, 20 Jan 2023 15:10:55 GMT

Hello,

[quote userid="121883" url="~/f/nordic-q-a/95468/unable-to-find-bootable-image/405827"]I could debug for 1 Week and now i got the same issue again. [/quote]

That is exactly what I have been experiencing but it has been weeks since I have not seen the error. The only difference is I see it in Segger Embedded Studio and you and Mexco are seeing it in VS Code. So, it seems we can safely eliminate the IDE as a possible cause.

Kind regards

Mohamed

RE: Unable to find bootable image

Earthworn1 — Fri, 20 Jan 2023 12:35:06 GMT

Hi,

i have the same problem as mexco.

I Flash from Actions -> Flash and the programm works fine.

Then i use Actions->Debug and the Application cant find the bootloader image.

The merged.hex File dosen't change in between.

I had the problem in the beginning and than suddenly it fixed itself. I could debug for 1 Week and now i got the same issue again.

Any other ideas?

I read the two hex files from the memory. They are identical.

Any other ideas?

RE: Unable to find bootable image

Learner — Fri, 20 Jan 2023 10:37:55 GMT

Hi Mexco,

I understand your frustration .

[quote userid="111623" url="~/f/nordic-q-a/95468/unable-to-find-bootable-image/405003"]

2. Programmed the nRF9160DK directly from Actions-> Flash. In this case also, program runs properly, but not possible to stop execution at any breakpoint.

Then, after above two methods, tried: Actions-> Debug.

[/quote]

So, to clarify, has your merged.hex changed between step 2 and Actions->Debug?

If this is NOT the case then there is no reason for the error. However, if the merged.hex has changed then, as Einar said, you must do Actions-> Flash followed by Actions->Debug.

I hope this helps.

Kind regards

Mohamed

RE: Unable to find bootable image

mexco — Mon, 16 Jan 2023 11:28:02 GMT

Hi. I tried following methods:

1. Programmed merged.hex using Programmer of nRF Connect. Then, program runs continuously properly. But in this, it is not possible to stop at any breakpoint.

2. Programmed the nRF9160DK directly from Actions-> Flash. In this case also, program runs properly, but not possible to stop execution at any breakpoint.

Then, after above two methods, tried: Actions-> Debug. The nRF9160DK is automatically re-programmed for Debug Configuration, but image error occurs and program never reach to main(). I got fed up of this issue and seems that will have to create whole project and add again custom code to sample code of Asset_tracker. If this issue occurs near last stage of a large project, causes wastage of too much time.

RE: Unable to find bootable image

Einar Thorsrud — Mon, 16 Jan 2023 09:02:11 GMT

Is it so that you only see this issue if you rebuild and debug without selecting Actions -> Flash first? If so, this is as expected, and the reason is that you need to program the full merged.hex as if not, the bootloader will not recognize the application as it has changed, and boot validation will fail. This is the expected behavior when using a bootloader, and the solution is to flash the merged hex file first in this case (for instance with Actions -> Flash), and then debug.

RE: Unable to find bootable image

mexco — Sat, 14 Jan 2023 15:54:41 GMT

Hi... I facing same issue with Visual Studio also. After wasting a week, I re-created the same project again, merged my files from faulty project to new.

In VSC, on left side penal, under Actions -> flash is used to run the build, then there is no issue.

But, during Actions->Debug, sometimes same issue occurs of and then. I facing this issue in Asset Tracker sample application, in which I adding custom code. Please suggest solution.

RE: Unable to find bootable image

Einar Thorsrud — Mon, 09 Jan 2023 13:13:20 GMT

I see. There is no obvious reason why it should faile sometimes, this should be consistent. Can you try to keep the application identical, and repeat testing, so that you get both a failing and working case? In both cases, dump the flash memory, and compare to see what is different. With that, we should be in a better position to understand where to look more closely.

You can easily dump the entire flash like this:

"nrfjprog --memrd 0 --n 0x80000 > flash_dump.txt"

When you got dumpts from both cases, diff the files to see where there is a difference, and what the difference is.

RE: Unable to find bootable image

Learner — Mon, 09 Jan 2023 12:49:54 GMT

Hi Einar,

Thank you for your suggestions.

I always download the merged.hex file before I start a debug session as shown below.

Target -> Download zephyr/merged.hex

Most of the time I don't get the error "Unable to find bootable image" but, as I said, from time to time I do and when I do get it, it can take a long time for me to get rid of it by restarting SES IDE many times, disconnecting the DK board, restarting my laptop etc..., hence my frustration. I am aware of VS CODE and we are planning to migrate to it but not right now. Until we do, I am looking for support from Nordic. I am hoping you will be able to provide it.

Thank you.

Kind regards

Mohamed

RE: Unable to find bootable image

Einar Thorsrud — Mon, 09 Jan 2023 12:38:58 GMT

Hi Mohamed,

When you download the application from SES NE, the image header needed by MCUBoot is missing. So it is expected that MCUBoot will not find a bootable image. When using MCUBoot, you need to flash the merged.hex file, and as this is not done automatically, you need to do it manually. Then you can subsequently debug by selecting to debug without downloading. To avoid this, you could consider testing/debugging without using MCUBoot, or migrating to nRF Connect for VS Code, which is the only IDE we recommend going forward (and also the only supported IDE for the latest nRF Connect SDK releases).

Einar