2025-08-26 12:21 PM
Hoping someone could help. I did a full erase on the stm32h747i_disco from the stm32cube programmer. I attempted (several times) to upload the STM32Cube_Demo-STM32H747I-DISCO-V1.0.0_FULL.hex and got the following error:
14:09:58 : Opening and parsing file: STM32Cube_Demo-STM32H747I-DISCO-V1.0.0_FULL.hex
14:09:58 : Memory Programming ...
14:09:58 : File : STM32Cube_Demo-STM32H747I-DISCO-V1.0.0_FULL.hex
14:10:00 : Size : 58.38 MB
14:10:00 : Address : 0x08000000
14:10:00 : Download in Progress:
14:10:04 : Error: failed to download Sector[0]
14:10:04 : Error: failed to download the File
14:10:05 : Memory [0x08000000 : 0x08200000] - Checksum : 0x139CE03C
Does anyone have a suggestion?
Solved! Go to Solution.
2025-08-27 6:47 AM - edited 2025-08-27 6:49 AM
Hello,
Did you enable the flash loader of the external QSPI memory before uploading the hex file??
The part of the graphics in that demo is located in the external memory (QSPI).
2025-08-26 11:11 PM
Hello @Duckpaddle
Which CubeProgrammer version used? Make sure to use the latest one.
Check the flash bank mode in the configuration settings.
Please have a look at this post that may help you.
If possible, share the log file.
2025-08-27 4:42 AM
Thank you for your quick response.
I am using the v2.20.0 version of the STM32CubeProgrammer. I have attached as a screen shot. I have also attached the log file where I attempted to program the board twice.
I am using the Demo Hex file from ST Micro for this board.
Thank you again for your help,
George
2025-08-27 6:47 AM - edited 2025-08-27 6:49 AM
Hello,
Did you enable the flash loader of the external QSPI memory before uploading the hex file??
The part of the graphics in that demo is located in the external memory (QSPI).
2025-08-27 7:37 AM
Thank you that solved the problem. Were you able to discover the issue from the log file?
Thanks,
2025-08-27 8:09 AM - edited 2025-08-27 8:16 AM
@Duckpaddle wrote:
Thank you that solved the problem. Were you able to discover the issue from the log file?
Thanks,
The log file at level 0 doesn't show much information but I had the doubt you didn't enable the external flash loader. So I tried to reproduce the behavior without enabling the flash loader and had almost the same log.
If you increase the verbosity level in the CubeProgrammer to 2 or 3 you can see there is an issue while programming at the address 0x90000000: