CONFIG_BOOTLOADER_MCUBOOT setting cause block in lfclk_spinwait

[taizo.kusunoki(DDDS)]

Hello I'm in trouble with nRF52833 module MDBT50Q-DB-33(with no 32kXtal)
in nrf connect sdk v2.3.0

I remove the 32k clock for new designed board and test with MDBT50Q-DB-33.
I use peripheral_sc_only and when I add

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_20PPM=y

and it's ok , can use bluetooth, can connect from nRF Connect for Desktop.

but I try DFU and I add

CONFIG_BOOTLOADER_MCUBOOT,

then it don't get out of "lfclk_spinwait". no come to main.

why this happened and how to solve it?
I trace with debugger and can not detect difference(means looks same code).

and now I noticed in "lfclk_spinwait", debugger said...

HFCLKSTARTED not 1(= not started) and LFCLKSRC =Xtal
when set CONFIG_BOOTLOADER_MCUBOOT

I just want clock setting is 

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_20PPM=y

and want use finally DFU
Could you please help me to specify correct LFCLK setting on MCUBOOT(for DFU)

thanks

[Hieu]

From the latest reply, this issue is because MCUboot doesn't get the CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC configuration applied.

If your project works with custom board files and does not have 32kHz crystal, then changing the (board)_defconfig file is a good approach.

Alternatively, you could also add the configuration to the MCUboot image. The simplest way is to add it to child_image/mcuboot.conf. Refer to the multi-image build documentation for more details and other methods.