Hello,
I am currently working on implementing an External Loader (ExtMemLoader) for a custom PCB design utilizing the STM32N657 MCU and a W25Q128JV flash memory.
I have built the .stldr file from my ExtMemLoader project and registered it as an External Loader in the STM32CubeProgrammer. My current goal is to program a simple test.bin file to the address 0x70000000. However, I am facing consistent issues during this process and would appreciate some guidance.
Q1. Validation of the development process My current strategy is to prioritize the successful implementation of the ExtMemLoader to ensure reliable communication between the MCU and the external flash before moving on to FSBL and Application development. Could you please confirm if this is the correct development flow?
Q2. Programming failure and system lockup (Deadlock) When I attempt to start the "Erase & Programming" process in STM32CubeProgrammer, it fails with the errors shown in the attached logs, eventually leading to a loss of connection with the debugger.
Based on my investigation, I suspect this may be due to a bus deadlock caused by speculative execution. I have attempted to resolve this by configuring the MPU to treat the memory region as Device memory and incorporating synchronization barriers; however, the issue persists. I am certain that there are no hardware connection issues, and I am confident that the root cause lies within the software/code-level implementation.
My ultimate objective is to achieve stable communication between the W25Q128JV and the STM32N657 via the ExtMemLoader. If anyone has encountered similar issues or has insights into resolving this type of deadlock on the STM32N6, I would greatly appreciate your advice.
I have attached the relevant logs for your reference. Thank you in advance for your time and assistance.
