Hi,
I am using an STM32N6570-DK running in XIP mode with XSPIM configured in multiplex mode.
Setup:
XSPIM in multiplex mode
XSPI1 / XSPI2 → Port 2 → external flash
XSPI3 → Port 1 → PSRAM
XSPI2 memory-mapped at 0x70000000
FSBL configures external flash and jumps to the application at 0x70100400
(VTOR = 0x70100400, MSP = 0x34200000, PC = 0x7010BA01)
Everything works correctly in direct XSPIM mode, but in multiplex mode the application HardFaults or hangs immediately after the FSBL jump.
The faults occur during early HAL initialization (e.g., in HAL_MspInit() or MX_GPIO_Init()), specifically when executing functions such as:
- HAL_PWREx_EnableVddIO3();
- __HAL_RCC_GPIOO_CLK_ENABLE();
- HAL_RCCEx_PeriphCLKConfig();
If I comment out these lines, the application runs, but then I face issues whenever adding new peripherals (like UART).
It seems that reinitializing power domains or clocks related to XSPI pins while executing from external flash triggers a crash. I am using STM32Cube FW_N6 V1.2.0 and STM32CubeMx v 6.15.0.
Is there an official or recommended method to prevent the application from reinitializing hardware already configured by the FSBL (such as XSPI, XSPIM, VddIO2/3, or related GPIOs/clocks) when running in XIP multiplex mode?
