RE: CANT use all 4 peripherals at the same time (peripheral-1 is causing BUS FAULT when enabled)

Atameemi — Mon, 18 Aug 2025 07:09:27 GMT

Hello Nuguru, thank you for your answer. However, the issue persists after disabling UART1 in MCUBOOT overlay and performing a pristine build.

Adding the "CONFIG_TFM_LOG_LEVEL_SILENCE=y" in mcuboot.conf gives the following warning: "CONFIG_TFM_LOG_LEVEL_SILENCE was assigned the value y, but got the value n. Missing dependencies:
((y || y || n || n || n || n || n) && BUILD_WITH_TFM) || BUILD_WITH_TFM || (BUILD_WITH_TFM && 0) || (BUILD_WITH_TFM && SOC_FAMILY_NORDIC_NRF)"

which again, still leads to BUS FAULT after a pristine build and erasing then flashing.

EDIT: "CONFIG_TFM_LOG_LEVEL_SILENCE=y" MUST be placed in prj.conf and NOT in mcuboot.conf! Disabling UART1 in MCUBOOT overlay is not necessary (and in app overlay too).

RE: CANT use all 4 peripherals at the same time (peripheral-1 is causing BUS FAULT when enabled)

Susheel Nuguru — Mon, 04 Aug 2025 07:08:02 GMT

SPIM1 and UARTE1 share the same hardware instance on the nRF9151. By default, the secure firmware (TF-M/MCUBoot) grabs UARTE1 for its own logging, so the moment our app tries to enable SPIM1 it faults out. The fix is simply to disable or silence TF-M’s use of UART1, by setting CONFIG_TFM_LOG_LEVEL_SILENCE=y or by adding a UART1-disable overlay in MCUBoot, so SPIM1 can be initialized without conflict. This workaround is also discussed in this thread. The compile issue when setting this config should have been already fixed in SDK later than v2.4.0