Fatal error occurs when enabling flash through CONFIG_FLASH

I have a custom NRF9151 board with Windbond W25Q32JV flash, and some other peripherals connected. It also has GPS and LTE which I have tested and work. My UART console is connected over UART0 which I have tested separately as well. I'm trying to test the SPI flash now but when I add CONFIG_FLASH=y to the hello_world sample and flash it on my board, nothing would show up on the console. Without CONFIG_FLASH=y, a hello world message would show up expected. 

I tried debugging the micro through west debug and saw the following stack trace:

#0  arch_system_halt (reason=25) at /.../zephyr/kernel/fatal.c:30
#1  0x00017756 in k_sys_fatal_error_handler (reason=<optimized out>, esf=<optimized out>) at /.../zephyr/kernel/fatal.c:44
#2  0x000138d4 in z_fatal_error (reason=<optimized out>, esf=<optimized out>) at /.../zephyr/kernel/fatal.c:119
#3  0x0001561a in z_arm_fatal_error (reason=<optimized out>, esf=esf@entry=0x2000d380 <z_interrupt_stacks+2008>) at /.../zephyr/arch/arm/core/fatal.c:86
#4  0x00012732 in arm_fault (exc_return=<optimized out>, esf=esf@entry=0x2000d380 <z_interrupt_stacks+2008>) at /.../nrf/modules/trusted-firmware-m/fault.c:283
#5  0x00012776 in tfm_ns_fault_handler_callback () at /.../nrf/modules/trusted-firmware-m/fault.c:337
#6  0xfefffffe in ?? ()

Parents Reply Children
No Data
Related