We have seen several issues related to the in-tool update mechanism in STM32CubeIDE during the last few days!
THE RESULT:
TRIGGERS:
- In-tool update from any STM32CubeIDE version STM32CubeIDE 1.10x or later.
- Using the Toolchain Manager to download another version of the toolchain vs what is delivered as part of the installation package.
- MPU users trying to download and add OpenSTLinux as part of there projects.
- Use Eclipse Marketplace to download any plug-in.
ROOT-CAUSE:
- 2022-12-07: CDT released the new CDT 11.0.0, the first CDT version requiring requiring Java17.
- STM32CubeIDE bundle a JRE11 since one plug-in is not compatible with Java17.
- STM32CubeIDE 1.10.x is pointing to https://download.eclipse.org/tools/cdt/releases/latest.
- When any of the "triggers" mentioned above is executed, the installation will become corrupted due to that incompatible components are fetched from the latest up-stream CDT repo.
WORK-AROUND:
- The only way to recover is to uninstall and use download the new installer to re-install the broken version.
- In-tool updates have been temporarily disabled to make sure that no more customer installations are impacted by in-tool updates or toolchain manager.
Update 2022-02-08:
MID-TERM FIX
- STM32CubeIDE 1.11.2 was released 2023w04.
- This version locks down which versions that are used of certain plug-ins preventing the risk for the IDE installation to become corrupted.
- Side-effect of locking down plug-in versions is that some plug-ins on Eclipse Marketplace requiring new versions of these plug-ins will not be possible to install.
LONG-TERM FIX
- Port the remaining plug-in to be Java17 compliant allowing us to update the JRE.
- The aim is to fix this for the 2023 June release.
