Skip to main content
Associate
July 28, 2026
Solved

STM32CubeIDE programs only 50% of flash at STM32C092GCU7

  • July 28, 2026
  • 1 reply
  • 48 views

STM32CubeIDE 1.19.0

STM32C092GCU7 with 256kb flash, 128 pages with 2kb size

 

I have 106,25KB of code. If I shift the start adress from 0x8000000 to 0x800A000 (to reserve space for future bootloader) CubeIDE cuts of the code to 88KB and only erases the pages till page 63 (Code would use now space in the second part of flash). Length in linker file is sufficient.

If I take the generated .elf file and program it by STM32CubeProgrammer, everything goes well. But this is only a part solution for me, because I want to have the possibility to debug in CubeIDE.

 

Start adress 0x8000000

ST-LINK SN  : 57FF6F067186535436441487
ST-LINK FW : V2J46S7
Board : --
Voltage : 3.22V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x44D
Revision ID : Rev A
Device name : STM32C09x
Flash size : 256 KBytes
Device type : MCU
Device CPU : Cortex-M0+
BL Version : 0x121



Opening and parsing file: ST-LINK_GDB_server_a12268.srec


Memory Programming ...
File : ST-LINK_GDB_server_a12268.srec
Size : 106.25 KB
Address : 0x08000000


Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 53]

 

Start adress 0x800A000 (same code as above)

ST-LINK SN  : 57FF6F067186535436441487
ST-LINK FW : V2J46S7
Board : --
Voltage : 3.22V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x44D
Revision ID : Rev A
Device name : STM32C09x
Flash size : 256 KBytes
Device type : MCU
Device CPU : Cortex-M0+
BL Version : 0x121



Opening and parsing file: ST-LINK_GDB_server_a13288.srec


Memory Programming ...
File : ST-LINK_GDB_server_a13288.srec
Size : 88.00 KB
Address : 0x0800A000


Erasing memory corresponding to segment 0:
Erasing internal memory sectors [20 63]

 

Any hints would be very appreciated.

Best answer by CBa

An update to STM32CubeIDE to version 2.2.0 and/or a STLinkV2 has solved the problem

1 reply

CBaAuthorBest answer
Associate
July 28, 2026

An update to STM32CubeIDE to version 2.2.0 and/or a STLinkV2 has solved the problem