MCUBoot stuck after 'Jumping to first image slot'

RE: MCUBoot stuck after 'Jumping to first image slot'

ClemensG — Thu, 01 Dec 2022 01:55:51 GMT

Might be I had the same with ncs 2.1.2 (same symptoms - didn't checked source or debugged).

Sadly your solution leads to:

*** Booting Zephyr OS build v3.1.99-ncs1-1 ***
I: Starting bootloader
W: Failed reading sectors; BOOT_MAX_IMG_SECTORS=256 - too small?
W: Cannot upgrade: not a compatible amount of sectors
E: Unable to find bootable image

Due to time reasons I switched to SPM.

RE: MCUBoot stuck after 'Jumping to first image slot'

allard.p — Fri, 11 Nov 2022 10:08:22 GMT

I managed to track down the issue, with help of this topic, and further debugging.

The problem is FPROTEXT, mcuboot locks sectors. When TF-M boots it tries unlock all sectors in spu_regions_reset_all_secure. This is not possible and causes the system to hang in an assertion.

The solution is to add an overlay for MCUboot where FPROTECT is disabled. Add the following to CMakeLists.txt:

# Use custom MCUBoot definitions
if (EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/mcuboot.conf")
    list(APPEND mcuboot_OVERLAY_CONFIG "${CMAKE_CURRENT_SOURCE_DIR}/mcuboot.conf")
endif()

Then add mcuboot.conf in the same directory, containing the following:

CONFIG_BOOT_MAX_IMG_SECTORS=256
CONFIG_FPROTECT=n

I think Nordic needs to set CONFIG_FPROTECT to n by default in MCUboot now SPM is replaced by TF-M?

RE: MCUBoot stuck after 'Jumping to first image slot'

allard.p — Thu, 10 Nov 2022 15:13:28 GMT

I managed to debug this further. The application is successfully booted by MCUBOOT, but is stuck in TFM initialization.

It is stuck on the following assert inside nrf_spu_flashregion_set:

NRFX_ASSERT(!(p_reg->FLASHREGION[region_id].PERM & SPU_FLASHREGION_PERM_LOCK_Msk));

The function is called with the following arguments:

p_reg: 0x500030000

region_id: 0

secure_attr: true

permissions: 7

lock_conf: false

and p_reg->FLASHREGION[0].PERM is 277

The call stack is the following:

nrf_spu_flashregion_set

spu_regions_reset_all_secure

spu_init_cfg

tfm_hal_set_up_static_boundaries

tfm_core_init

main

Any ideas what is going on here? Solutions given in this topic do not work.

RE: MCUBoot stuck after 'Jumping to first image slot'

allard.p — Thu, 10 Nov 2022 10:11:26 GMT

Hi,

Any news on this?

RE: MCUBoot stuck after 'Jumping to first image slot'

Susheel Nuguru — Thu, 27 Oct 2022 04:52:51 GMT

it seems like they have fixed it in NCSv2.1.0 but seems like you are seeing the issue still. I need to ask my colleague to check if this is still an issue in the latest sdk.

RE: MCUBoot stuck after 'Jumping to first image slot'

allard.p — Wed, 26 Oct 2022 15:00:27 GMT

SPM is an option, but it is deprecated, so TF-M is preferred.

RE: MCUBoot stuck after 'Jumping to first image slot'

livetsMozell — Mon, 24 Oct 2022 09:49:17 GMT

You can try to use SPM instead of TF-M

RE: MCUBoot stuck after 'Jumping to first image slot'

allard.p — Mon, 24 Oct 2022 06:45:26 GMT

I've seen this topic. The link given points to the latest documentation where I can not find anything that looks like my issue. It seem that the problem this topic is referring to is fixed.

RE: MCUBoot stuck after 'Jumping to first image slot'

livetsMozell — Fri, 21 Oct 2022 09:47:20 GMT

There was a known issue regarding this. Below is a link to earlier answer.

devzone.nordicsemi.com/.../9160dk-boot-stuck-at-jumping-to-the-first-image-slot-sample-http_update-with-ncs-2-0-0