Build Analyzer issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-09 5:36 PM
Hello,
Is there a trick to get the Build Analyzer to produce data every time the code is compiled? It seems like the only way I can get it to update the window is if I change something in the linker script file and recompile again. Is there an easier way or a setting that needs to be set?
thanks
Matthew
Solved! Go to Solution.
- Labels:
-
STM32CubeIDE
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-11 6:18 AM
Oops, I take that back... Mahmoud sent me a private email showing me the trick on how to get it to work each and every time... I've tested it 10 times now, and it seems to work for me. Not sure why this trick is not public, so I will post the solution here...
after the user builds the project, you must right click on the project name, and select refresh. Then the update for the building analyzer works. Give it a try and let me know if it works for you too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-09 8:23 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-09 8:42 PM
Hi @Pavel A.
I just tried your suggestion, and when the "auto" is turned on, the refresh button is disabled:
turning off "Auto" re-enables that button, but I still have the original problem of the build analyzer not updating.
Either the build analyzer window is blank, or it is using data from an older compile.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-10 12:50 AM
Hello @matt-crc ,
First let me thank you for posting.
I suggest that you refer to UM2609, section 2.5 where this new button is explained and how you can change the behavior.
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-10 12:57 AM
I figured out the button settings as per section 2.5 of your manual... But the main problem is getting the data.
In Auto Mode, the build analyzer does not update
in On Request mode, the build analyzer does not update with the refresh icon.
Do you know how to get the Build analyzer to work reliably?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-10 1:06 AM
I suggest that you restart STM32CubeIDE, then build the project, knowing that I am using STM32CubeIDE 1.18.
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-10 1:09 AM
I'm running STM32cbutIDE 1.18 as well.... There must be a better way than having to restart the package after each compile....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-10 1:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-10 6:30 AM
My experience: The behavior used to work but was broken some time in the past few updates. The "auto" refresh doesn't work, and while restarting stm32cubeide works (once), it's hardly a solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-10 6:33 AM
Yeah, its a real pain to have to restart the tool to check where the variables are stored
