F769 EVAL QSPI_Executeinplace example code
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 6:28 AM - last edited on ‎2025-06-16 8:02 AM by Amel NASRI
when running the QSPI_Executeinplace example code on the stm32f769i_eval board,the program enters HardFault_handler() after executing GpioToggle().i just remove the QSPI_DummyCyclesCfg(),in GpioToggle() the GPIO Not Taking effect,so How can I solve this problem? thanks
Solved! Go to Solution.
- Labels:
-
QSPI
-
STM32F7 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 7:58 AM
Hello @andrewpei ,
Use a debugger to identify the exact instruction causing the HardFault.
Have you made any updates to the example? If yes, please share the exact modifications you made and the debugger output when the HardFault occurs?
Ensure that the QSPI and GPIO peripherals do not have conflicting configurations or resource usage.
Ensure that the dummy cycles are correctly configured as per the QSPI memory datasheet.
Remember to use the latest release of CubeF7 firmware package.
Thanks
Imen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 7:58 AM
Hello @andrewpei ,
Use a debugger to identify the exact instruction causing the HardFault.
Have you made any updates to the example? If yes, please share the exact modifications you made and the debugger output when the HardFault occurs?
Ensure that the QSPI and GPIO peripherals do not have conflicting configurations or resource usage.
Ensure that the dummy cycles are correctly configured as per the QSPI memory datasheet.
Remember to use the latest release of CubeF7 firmware package.
Thanks
Imen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 8:11 AM
Hello @andrewpei
Please refer to this article to debug hardfault.
Saket_Om
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-16 8:55 PM
Hello,@Imen.D ,
Indeed, by debug the code, I found that the data written to NOR Flash differs from the original data,because the dummy cycle configuration for my NOR Flash under the QUAD_OUT_FAST_READ_CMD instruction differs from the example code's implementation.
