Skip to main content
Explorer
July 31, 2025
Solved

STM32G473RB - Error in Launch Sequence - when Flash File > 64kB

  • July 31, 2025
  • 1 reply
  • 367 views

Hello, I have the same problem but with the new version STM32CubeIDE_1.19.0. All the symptoms are the same as in this post but in the STM32G473RB processor and when the firmware becomes more than 64KB. 


Shpegun60_1-1753950923963.png

 

Shpegun60_0-1753950898325.png

 

Shpegun60_2-1753950956029.png

 

Cube programmer normally writes the .elf taken from the project

10:46:40 : Data read successfully
10:46:40 : Time elapsed during the read operation is: 00:00:00.007
10:46:44 : External loader sector number is too big, displaying only the first 4000 sectors
10:47:12 : Memory Programming ...
10:47:12 : Opening and parsing file: bms_g474.elf
10:47:12 : File : bms_g474.elf
10:47:12 : Size : 64.05 KB
10:47:12 : Address : 0x08000000
10:47:12 : Erasing memory corresponding to segment 0:
10:47:12 : Erasing internal memory sectors [0 65280]
10:47:13 : Download in Progress:
10:47:14 : File download complete
10:47:14 : Time elapsed during download operation: 00:00:01.891
10:47:14 : Verifying ...
10:47:14 : Read progress:
10:47:14 : Download verified successfully
10:47:14 : RUNNING Program ...
10:47:14 : Address: : 0x08000000
10:47:14 : Application is running, Please Hold on...
10:47:14 : Start operation achieved successfully

 

 

    This topic has been closed for replies.
    Best answer by Shpegun60

    Shpegun60_1-1758017658841.png

    Solution: Disable DBANK by default and everything will work

     

    1 reply

    Shpegun60Author
    Explorer
    July 31, 2025

    I managed to get around this bug in the following ways, but it does not solve the root of the problem:
    1) I enable this checkbox:

    Shpegun60_0-1753952189799.png

    after that the IDE writes only those sectors to Flash that have been changed

    2) Every time after generating a new elf file, you need to flash it through the
    STM32CubeProgrammer utility

    Shpegun60_0-1753962802096.png

     

    3) Run Debug directly in STM32CubeIDE 1.19.0

     

    Shpegun60_1-1753962848471.png

     

    Since the latest version of the code is flashed, STM32CubeIDE will see this and will only run debug.

    4) do this every time something has been changed in the code

     

    Otherwise, if we try to run debug with the flag [Incremental flash
    programming (experimental)] is enabled, without prior firmware via STM32CubeProgrammer, we get this:

    Shpegun60_0-1753963730626.png

     

     

    Shpegun60AuthorAnswer
    Explorer
    September 16, 2025

    Shpegun60_1-1758017658841.png

    Solution: Disable DBANK by default and everything will work