2024-03-17 06:59 AM
Hi folks,
I use latest STM32CubeIDE on Linux and noticed that build analyzer always updates "Memory Regions" tab for previous build configuration (whatever it was Debug or Release).
No matter how many times I rebuild code in "Debug" configuration, the information is still provided for "Release".
As soon as I switch project setup to "Release", it would show results for "Debug" after next build.
Could anyone explain if Build Analyzer could do analysis of the last build instead of previous configuration? (or it's a bug in the tool)
Cheers,
Lex
Solved! Go to Solution.
2024-03-20 03:10 AM - edited 2024-03-20 03:13 AM
You can switch to the wanted build configuration view of the analyzer by clicking on the .map / .elf file inside the Debug/Release folder in the Project Explorer file tree.
And new for me in CubeIDE 1.15 is the refresh button thing: https://community.st.com/t5/stm32cubeide-mcus/build-analyzer-does-not-work-after-stm32cubeide-update/m-p/652218
2024-03-17 07:19 AM
Hi,
i only use "debug" , so i never seen this problem. (optimizer -O2 .)
Whats the difference (in your settings) between Debug or Release ?
2024-03-17 07:29 AM
It does appear buggy. I don't get the same exact behavior, but it doesn't seem to switch properly between configurations for me. Clearly a bug.
I have found that deleting the Release directory, then building the Debug configuration will get it to show Debug correctly again (and vice versa).
2024-03-20 03:10 AM - edited 2024-03-20 03:13 AM
You can switch to the wanted build configuration view of the analyzer by clicking on the .map / .elf file inside the Debug/Release folder in the Project Explorer file tree.
And new for me in CubeIDE 1.15 is the refresh button thing: https://community.st.com/t5/stm32cubeide-mcus/build-analyzer-does-not-work-after-stm32cubeide-update/m-p/652218