Skip to main content
Artur Vieira
Associate III
January 29, 2026
Solved

Build Analyzer strange information

  • January 29, 2026
  • 1 reply
  • 215 views

Hi

 

Starting my first project testing VSCode integration of ST tools instead of using Eclipse... Just reporting an issue with build analyzer, it is indicating that I have 188% of FLASH used...

ArturVieira_0-1769682076462.png

The compiler output gives the correct information:

ArturVieira_1-1769682143413.png

It seems an issue parsing the map or elf file to operate the tool.

 

Best answer by Artur Vieira

Ok, it seems to be solved.

 

I was "copying" code from other project to reuse, and I have a structure that is to be placed in a specific section (to make sure that is at the start of FLASH)

__attribute__((section(".application_properties"))) __attribute__((aligned(16))) const ApplicationProperties_t applicationProperties = {
And had forgot to add that section to the Linker Script.
 
Now that I add to the Linker script it seems to be OK, the build analyzer seems to be reporting the size OK. 
 
 

1 reply

PGUER.1
ST Employee
January 29, 2026

Hi,
It may seem strange, but the build analyzer is designed to help you identify unusual issues.
There is likely a problem with the LD files (such as missing or incorrect section definitions).

You can try to identify the element causing this behavior by:

  • Switching the 'select elements display type' to Array
  • Looking for an element in the memory range: 0x0800ed9c - 0x0800edbe
  • Checking if a session is defined for this element

If everything looks fine from your perspective, you can share your LD and map files with me via private email if possible.

Please note that there might also be an issue with the build analyzer implementation.



Artur Vieira
Artur VieiraAuthorBest answer
Associate III
January 30, 2026

Ok, it seems to be solved.

 

I was "copying" code from other project to reuse, and I have a structure that is to be placed in a specific section (to make sure that is at the start of FLASH)

__attribute__((section(".application_properties"))) __attribute__((aligned(16))) const ApplicationProperties_t applicationProperties = {
And had forgot to add that section to the Linker Script.
 
Now that I add to the Linker script it seems to be OK, the build analyzer seems to be reporting the size OK.