Build Analyzer does not work after STM32CubeIDE update.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-19 7:42 PM
Hi.
I was using STM32CubeIDE 1.14.0 until yesterday.
Build Analyzer worked fine in 1.14.0, but after updating to 1.15.0 using the update feature provided by CubeIDE, nothing is displayed in Build Analyzer.
The build was successful and the <project>.map file was created, but the Build Analyzer information was not displayed, and I uninstalled and reinstalled CubeIDE, but it was the same.
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
‎2024-03-20 12:28 AM - edited ‎2024-03-20 12:39 AM
Hello Kim,
You have to click on the "Refresh" button:
Please, refer to the User Manual, section 2.5 where this new button is explained and how you can change the behavior:
BR
Christelle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-20 12:28 AM - edited ‎2024-03-20 12:39 AM
Hello Kim,
You have to click on the "Refresh" button:
Please, refer to the User Manual, section 2.5 where this new button is explained and how you can change the behavior:
BR
Christelle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-20 12:38 AM
Thank you!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-20 12:41 AM
welcome !
Please refer to my last comment if you want to change the behavior of this functionality.
Have a good day
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-03 10:07 AM - edited ‎2024-04-03 10:11 AM
I am having the same issue after 14.1 to 15.0 on Win 11.
I have changed the setting to Auto and still blank in Build Analyzer tab after building. Have restarted IDE.
Additionally, the refresh button is disabled, does not highlight when I mouse over it and clicking it does nothing:
EDIT: My mistake. 'On Request 'does in fact enable the 'Refresh' button and the button perform the functionality correctly.
I assumed that the 'Auto' setting would load the analysis on every build, but alas it does not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-05 6:23 PM
Has anyone managed to get the 'auto' option to work, or is there an issue with the 'auto' refresh?
As section 2.5 states:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-06 1:59 PM
Cube IDE has always had a bug in that the Build Analyser would sometimes not show - until you clicked on the .map file in the LH pane.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-25 6:48 AM - edited ‎2024-04-25 7:02 AM
@Kim KyungTack , @christelle burguera selecting "on request" did not fix the problem. It is additional click and still randomly fails.Just keep it on "Auto"
What does work for me is selecting the project and click on "refresh" or hit F5
then the actual .map /.elf file appears and when you click on that the build analyzer and stack analyzer will populate.
I suspect cubeide has some bug in refresh after build. If was not reliable before but in version 15 it got much worse.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-25 6:50 AM
yes, see my reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-05-09 8:19 AM
I have installed the latest version 1.15.1 but the problem still persists. Any solutions?
