Assertion fail on first dfu_target_offset_get() call after FW update

[dairup]

Hello,

We are using DFU target library with MCUboot (Connect SDK v2.9.0):

uint32_t offset = 0;
dfu_target_mcuboot_set_buf(mcuboot_buf, sizeof(mcuboot_buf));
dfu_target_init(DFU_TARGET_IMAGE_TYPE_MCUBOOT, 0, 0, dfu_target_callback_handler);
dfu_target_offset_get(&offset);

And we are getting assertion fail on first dfu_target_offset_get() call after FW update:

ASSERTION FAIL [handler != ((void *)0)] @ WEST_TOPDIR/zephyr/kernel/work.c:687

On second attempt, after watchdog reboots MCU, everything works fine.

What could cause this issue?

[dairup]

MCU is nrf54l15.

[Amanda Hsieh]

Hi, 

Are you using a custom board or nRF54L15DK?

Is it possible to reproduce with nRF54L15DK? If so, could you provide a simple project for us to investigate the issue?

Regards,
Amanda H.

[dairup]

Hello,

We are using custom HW. We will try to replicate this issue with DK next week.

[dairup]

Hello,

we were able to reproduce same issue on DK. Simple project is attached. If flash is erased with "nrfutil device erase" before flashing, on first startup we are getting the same assert fail:

ASSERTION FAIL [handler != ((void *)0)] @ WEST_TOPDIR/zephyr/kernel/work.c:687
[00:00:00.752,454] <err> os: r0/a1:  0x00000004  r1/a2:  0x000002af  r2/a3:  0x00000003
[00:00:00.752,462] <err> os: r3/a4:  0x00000004 r12/ip:  0x00000000 r14/lr:  0x00037fbf
[00:00:00.752,469] <err> os:  xpsr:  0x01000000
[00:00:00.752,475] <err> os: Faulting instruction address (r15/pc): 0x0003cd00
[00:00:00.752,496] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:00:00.752,512] <err> os: Current thread: 0x20004008 (unknown)
[00:00:00.812,376] <err> os: Halting system

We use sysbuild, -Os optimization and our devicetree overlay:

&cpuapp_rram {
	reg = <0x0 DT_SIZE_K(1524)>;
};

&cpuapp_sram {
	reg = <0x20000000 DT_SIZE_K(256)>;
	ranges = <0x0 0x20000000 0x40000>;
};

The issue can only be replicated if BT settings are enabled in prj.conf.

Could you inform us how to resolve this problem?

assert_fail.7z

[Amanda Hsieh]

Hi, 

What is your nRF54L15DK version on the white sticker?

Do you want to update image with DFU via Bluetooth? If so, Check FOTA updates on nRF54L Series devices.

dairup said:

The issue can only be replicated if BT settings are enabled in prj.conf.

I would suggest you use a BT sample as the basement to develop your application such as zephyr\samples\bluetooth\peripheral to enable BT without issue. Then, move to mcuboot part. I can use this test project peripheral_339380.7z base on the peripheral sample to test your code without issue. 

-Amanda H.