2020-10-16 12:47 AM
Hello,
I am trying to update my current installation (1.1.0) to 4.1.2, but CubeIDE throws this message every time.
I have looked for similar problems in the forum, but seems like no one has had this issue, and I don´t know how to solve it. Anyone could please help?
2020-10-16 12:53 AM
Hello FTORR,
This has already be treated in another topic: https://community.st.com/s/question/0D50X0000ByuFvZSQU/stm32cubeide-update-not-working
You have to check if the EPP Marketplace Client update-site URL exists in Window > Preferences > Install/Update > Available Software Sites, and if so uncheck or remove it. Then try again.
2020-10-16 04:43 AM
Hello Julien,
Thank you for your support and sorry but couldn´t find that post before asking. I have done it and that message does not appear anymore, but the update is still failing, now showing this.Any suggestion?
2020-10-16 07:02 AM
Looks like the update failed during install phase because of incomplete module, an about.ini file is missing...
Does this issue is reproducible when launching again the update?
If yes, and only if, you could try to rename C:\ST\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_1.4.0.202007081208 to C:\ST\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_1.4.0.202007081208.backup.
And relaunch the update to download again this broken module.
Another thing to verify is your free disk space. Better to have more than 2Go to update from 1.1.0 to 1.4.2. At the end it will not use all this space, update just requires more temporary space to fetch and apply stuff safely.
2020-10-18 11:57 PM
Hi Julien. Yes, it happened even if retrying to update. Now, after renaming that folder, it complains that cannot open it with this new error (even if retrying the update):
2020-10-20 11:04 PM
Anyone can help please? I have tried to solve it myself but still I am not able to update. I´d prefer to use an ST microcontroller for the product, but updating CubeIDE is a must now.
2020-10-21 06:02 AM
Looking for a solution, I have found this thread:
I will stay on 1.1.0 for some more time, and not update until this issue is resolved in future releases.
Thanks for the support.