Would like to be able to use Build Analyzer.

[Hollies]

I hope to use the same Build Analyzer in VSCode as in the IDE, which allows developers to more clearly see the use of flash and memory. I have tried to use GPT to write a plugin, but the effect is not good, and I don't understand the JS language well, so it is difficult to develop it by myself.

My mother tongue is not English, please forgive me if it is not easy to understand.

[Southbranch]

Looks very nice!

Is this an add-in to VS Code?

Just a small suggestion: memory sub areas could perhaps be indended under the parent area?

[ATwice291]

Yes, here is a link to the VSCode Marketplace

Feel free to write whatever you think about it. I have no idea how to make plugins, it all happened by accident. I was just very disappointed when I started taking my first steps in VSCode for STM32 and didn't find such a useful tool. The layout is far from perfect, but at least it responds to clicks, expands and collapses)) It's a big success for me. Indents are important, 100% agree

[ATwice291]

quick patch, v.1.0.2 

[Southbranch]

Great, the devil is in the details! 

[Hollies]

You've developed a really useful plugin. I admire your executive ability. Unlike me, I left my work halfway.

[prudhvichitturi]

1. how to run this , i have lloaded .map file ,
2. what is the next step?

[mattias norlander]

Hi,

There are some different ways to open it:

From Explorer view:

From CMake Tools view:

If you do not yet have a successfully compiled project resulting in an elf/map-file combo, the build analyzer cannot show any info.

Kind regards, Mattias

[mattias norlander]

Maybe some more context...

2025-05-07, we deployed version 3.x our ST VS Code extension. There is a sticky post about this in this forum.

As part of this pre-release deployment, we provide a new build analyzer. It looks like this:

This pre-release is available here:

• https://marketplace.visualstudio.com/items?itemName=stmicroelectronics.stm32-vscode-extension&ssr=false#overview
• Why a pre-releae?
  • This is a huge update from architecture point of view. Even if there are not tons of new benefits/features.
  • Deploying this update as a pre-release ensures that existing users are not auto-updated. Nobody likes forced major tool updates in on-going projects.
  • And it sets the right expectation in terms of maturity.

At the marketplace you can read the readme.md and the changelog.md to understand a bit more. More info coming step-by-step in a continuous delivery spirit.