Fatal error occurs when enabling flash through CONFIG_FLASH

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

heisenbug — Sun, 25 Jan 2026 01:00:41 GMT

I figured it out. It's because TF-M still uses UART1 for logging even though the peripheral is disabled in the device tree. Setting CONFIG_TFM_LOG_LEVEL_SILENCE=y fixed the isse

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

heisenbug — Sun, 25 Jan 2026 00:43:11 GMT

At the time I decided to run the spi flash example without TF-M. Coming back to it, I see a clearer issue. I have my SPI flash configured on SPI1 in the device tree. Without TF-M it works as expected. With TF-M, I get the following bus fault:

[00:00:00.263,793] <err> os: ***** BUS FAULT *****
[00:00:00.263,793] <err> os:   Precise data bus error
[00:00:00.263,793] <err> os:   BFAR Address: 0x0
[00:00:00.263,824] <err> os: r0/a1:  0x00010e0c  r1/a2:  0x00000003  r2/a3:  0x40009000
[00:00:00.263,824] <err> os: r3/a4:  0x0000000a r12/ip:  0x40842500 r14/lr:  0xfffcf8f0
[00:00:00.263,854] <err> os:  xpsr:  0x01000200
[00:00:00.263,854] <err> os: Faulting instruction address (r15/pc): 0x0000b400
[00:00:00.263,885] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
[00:00:00.263,916] <err> os: Current thread: 0x2000ccd8 (unknown)
[00:00:00.325,073] <err> os: Halting system

When I check the address location, it points the following line: zephyr/drivers/pinctrl/pinctrl_nrf.c:179

When I replace SPI1 with SPI2, I don't see the problem anymore with TF-M enabled. Is SPI1 only meant to operate without TF-M?

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

Benjamin — Wed, 25 Jun 2025 11:20:52 GMT

It should not be a difference.

Internal flash: Can be partitioned and protected by the SPU.

External SPI flash: Not protected by the SPU. Accessible to both secure and non-secure code unless you implement your own software-based protections.

Have you changed any other file in the hello_world sample?

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

heisenbug — Sat, 21 Jun 2025 00:26:11 GMT

How does SPI flash functionality differ when building for insecure vs secure variant of the board?

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

Benjamin — Thu, 19 Jun 2025 08:53:25 GMT

Hi again Mian,

I created a custom board, and it works when CONFIG_FLASH=y is set.
If you haven't solved it yet, I recommend comparing the compiled Devicetree and Kconfig files with both the ns version on you custom board and the development kit version for further investigation.

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

heisenbug — Tue, 17 Jun 2025 21:24:55 GMT

That indeed made a difference! Building for nrf9151, and then flashing onto my board, I'm able to see console log output now!

I was under the assumption the ns meant no TF-M but after referencing the docs, my understanding is the opposite

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

Benjamin — Tue, 17 Jun 2025 14:44:01 GMT

Hi,

I'll look into this in more detail tomorrow. In the meantime, if you have time, you can try building without TF-M support by using nrf9151 instead of nrf9151/ns and see if that works. This will help isolate the issue.

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

heisenbug — Mon, 16 Jun 2025 19:02:40 GMT

Hi Benjamin,

Yes, I tested it on nRF9151dk with CONFIG_FLASH option and it works for me as well. I've attached the requested files. I renamed .config to config as upload of .config isn't allowed.

devzone.nordicsemi.com/.../8322.zephyr.dts devzone.nordicsemi.com/.../1488_2E00_config

RE: Fatal error occurs when enabling flash through CONFIG_FLASH

Benjamin — Mon, 16 Jun 2025 12:36:31 GMT

Hi Mian,

1. Have you tested the hello_world sample on the nRF9151DK?

It works for me both with and without the CONFIG_FLASH option.

2. If it works, can you send me these files? build/{app_name}/zephyr/zephyr.dts and build/{app_name}/zephyr/.config

Best regards,
Benjamin