2025-07-05 7:37 AM - last edited on 2025-07-07 7:44 AM by mƎALLEm
The STM32H750B-dk Based Custom Board isn't entering debugging mode when using STM32CubeIDE . But QSPI Example Code is working perfectly.
Solved! Go to Solution.
2025-07-16 1:26 AM
Hello @Caan ,
In fact, you need to follow the procedure described in the readme file.
For CubeIDE, you need to use STM32CubeProgrammer tool to handle the external QSPI flash:
From th read me file:
In order to make the program work, you must do the following:
1. Select required configuration in memory.h in Templates\ExtMem_Boot\Inc template.
The default configuration is:
- DATA_AREA set to USE_INTERNAL_SRAM
- CODE_AREA set to USE_QSPI
2. Program the internal Flash with the ExtMem_Boot (see below).
3. Program the external memory with this example (see below).
4. Start debugging user application or reset for free running.
In order to load the ExtMem_Boot code :
- Open your preferred toolchain :
- Open the Project
- Rebuild all files
- Load project image
In order to load this example to the external memory:
- Open your preferred toolchain
- Open the Project
- Use project matching ExtMem_Boot selected configuration
- Rebuild all files:
- Run & debug the program:
- For an XiP configuration (eXecute in Place from QSPI):
- Using EWARM or MDK-ARM : Load project image from the IDE: Project->Debug
- Using STM32CubeIDE :
- Open the STM32CubeProgrammer tool
- Select the QSPI external flash loader "MT25TL01G_STM32H750B-DISCO" in case of XiP from QSPI
- From Erasing & Programming menu, browse and open the output binary file relative to your application
- Load the file into the external QSPI flash using "Start Programming" at the address APPLICATION_ADDRESS (0x90000000).
Then run a debug session from CubeIDE.
Hope that helps.
2025-07-05 10:09 AM - edited 2025-07-05 10:09 AM
If the FMC settings are bad, the debugger won't be able to connect.
Does the program work in non-debug mode?
Consider putting in HAL_Delay(1000) prior to any FMC initialization, setting a breakpoint there, and stepping through.
2025-07-06 6:01 AM
When Downloading the binary directly into the Board same error Shows up.
2025-07-07 7:18 AM
The Custom Board is an Exact Replica of the STM32H750B-DK with Dual Flash (same part number and SDRAM IS42s322400F Connected with the same Pins as per the EVK). However, I am unable to start the basic TouchGFX code. The board is connected using STM32CUBEProgrammer with the external loader selected, and the erase and load functions are working properly.
2025-07-07 7:22 AM
@Caan wrote:
The Custom Board is an Exact Replica of the STM32H750B-DK
Try to load the example to a STM32H750B-DK board and check again.
2025-07-07 7:24 AM - edited 2025-07-07 7:26 AM
A sample Touchgfx Code I just now built runs wonderful on the STM32H750B-DK but the same code is going in Hard fault on Custom board.
I think the STM32H750B-DK uses MT48LC2M32B2 as SDRAM and I am Using IS42S32400F as SDRAM.
2025-07-07 7:27 AM
Before going ahead to TouchGFX which is another question.
As the original question was about FMC example, what if you load that FMC example to the STM32H750B-DK board?
2025-07-07 7:30 AM
FMC Example through the same error as my custom board on the STM32H750B-DK.
2025-07-07 7:34 AM
Do you mean you are facing an issue with STM32H750B-DK with this example?:
2025-07-07 7:39 AM - edited 2025-07-07 7:49 AM
Yes, I have cleaned the old installation files of STM32CUBEH7 Folder and cloned the above link specified by you , But the fresh FMC Code is sending out the same error