STM32CubeIDE 1.6.0 released
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-02-24 7:00 AM
STM32CubeIDE 1.6.0 was released this week on st.com as well as a in-tool update patch.
Caution: The in-tool update does not allow updating drivers and ST-LINK server tool. Full installer is required for this.
What is new in 1.6.0? (only some highlights)
- Target support updated in-sync with STM32Cube ecosystem in general. In particular:
- Added support for additional STM32G0 and STM32WB series devices.
- Integration of STM32CubeMX 6.2.0, STM32CubeProgrammer 2.7.0 and latest versions of various other STM32 deliverables.
- Added Azure RTOS ThreadX debug support.
- Toolchain manager changes
- The Arm and Gnu Tools for STM32 toolchains based on GCC 9-2020-q2​ is the new default bundled and used toolchain in CubeIDE 1.6.0.
- Toolchain manager extended to support using a locally installed 3rd party GCC toolchain.
- Information Center updated with new Tools Panel for easy access/download of additional tools.
- STM32CubeMX plug-in provides pinout compatible search feature
- For MPU series :
- Application / Library user land development
- JRE updates
- Moved to Java11
- JRE is now distributed as plug-in allowing also in-tool update of JRE via P2
Main issues fixed in STM32CubeIDE 1.6.0
Only a sub-set of the many tickets closed are mentioned in the release note.
Known problems and limitations
Please refer to the release note.
Where do I Obtain CubeIDE 1.6.0?
- https://www.st.com/stm32cubeide
- ... Or update your current installation of STM32CubeIDE using: Help > Check for updates
- Caution: After updating STM32CubeIDE, the post-update restart fails. STM32CubeIDE must be restarted manually.
- Labels:
-
STM32CubeIDE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 2:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 2:42 AM
Sounds better as not weird trace here. Are you able to import back to such workspace a project from failing workspace (File > Open Project From File System) ? Once import done what about Device configuration Tool behavior ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 3:19 AM
Your log file only reports Exceptions with git plugin for your project:
!ENTRY org.eclipse.team.core 4 0 2021-03-02 10:19:45.908
!MESSAGE Could not instantiate provider org.eclipse.egit.core.GitProvider for project ***_***-***.
!STACK 1
org.eclipse.team.core.TeamException: Could not instantiate provider org.eclipse.egit.core.GitProvider for project ***_***-***.
at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:200)
at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:267)
at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:542)
at org.eclipse.team.internal.core.TeamHookDispatcher.getProvider(TeamHookDispatcher.java:96)
at org.eclipse.team.internal.core.TeamHookDispatcher.getRuleFactory(TeamHookDispatcher.java:102)
at org.eclipse.core.internal.resources.Rules.factoryFor(Rules.java:101)
at org.eclipse.core.internal.resources.Rules.refreshRule(Rules.java:178)
at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1547)
at org.eclipse.cdt.internal.core.pdom.PDOMSetupJob.syncronizeProjectSettings(PDOMSetupJob.java:76)
at org.eclipse.cdt.internal.core.pdom.PDOMSetupJob.run(PDOMSetupJob.java:58)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Could you try to disconnect your project from Git in STM32CubeIDE with Right click on the project > Team > Disconnect and try headless-build again.
This could be reverted with Right click on the project > Team > Share Project, and does not have impact on Git repository history.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 3:24 AM
I am actually using the project with SmartGit (advanced Git GUI software) and have never configured the project for Git in CubeIDE.
Might this be the cause of the issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 3:49 AM
I'm not SmartGit aware, only using Git bash or eGit on Windows, but the tool could be the cause.
One test you could try is :
- Close SmartGit
- Rename the .git folder in your project to .git-backup
- Relaunch headless-build
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 3:56 AM
You must be aware that this is not risks free.
7-2018 toolchain under plugins directory can be garbage collected at any time, depending on P2 willingness. It means that your "Local" toolchain won't exist anymore.
To be sure to keep it safely, install it thanks to the Toolchain Manager as described above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 4:02 AM
Thanks @Cartu38 OpenDev​ , looks like I received exactly the same through the update channel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 4:35 AM
Now the project is not even going...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 4:39 AM
I will try to upgrade to the old version, CubeIDE_1.5.1. I will try to upgrade to the old version, 1.5.1. The project has become, and I just need to fix a few things. Time is short. Thank you for trying to help me !!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2021-03-03 4:51 AM
You're welcome.
Ok project is not building but here according to me more project setup than tool issue or at least vs. first sharing done you're not facing here hanging tool what was a mess (as refresh workspace sounds helping may you have original one corrupted at a point ? ... due to any hard exit of tool or ?°.
Then about project build issue maybe because new workspace not at same level than original one and relying on some external dependencies or ... (may have plenty or issue roots here but all such shoudl be fixable shortly based on your project knowledge looking at build trace).
