2022-10-18 03:59 AM
Hi,
i cannot update the STM32IDE firmware. I only get this error after a long time of being stuck in the update process at 36%
Solved! Go to Solution.
2022-10-19 05:56 AM
Hi again,
Managed to resolve the issue. The previous version of the IDE for some reason did not notify the the above errors as errors at all. The problem was that some variables were initiated multiple times. Got it fixed and everything is now working as intended. Thanks Samer for the help.
Anton
2022-10-19 02:14 AM
Hello @Anton Kaisti
First let me thank you for posting.
If this behavior persists, try to check the network connection in the CUbeIDE. In case you are using a PROXY make sure that CubeIDE take the same configuration.
Don't hesitate to reply in case this proposition didn't respond to your exact need.
Kind regards,
Semer.
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.
2022-10-19 03:40 AM
Hi, i now managed to update to the latest firmware, however now all projects have a massive amount of errors and i dont know what to do about them. Here an example:
Urgent help needed.
Regards
Anton
2022-10-19 05:07 AM
Seems to be missing at least one include file.
Find first error.
Check where file is normally included in the build, and that the file is present.
I would generally avoid updating a primary build environment, but understand ST pushes this and the instability that causes.
2022-10-19 05:56 AM
Hi again,
Managed to resolve the issue. The previous version of the IDE for some reason did not notify the the above errors as errors at all. The problem was that some variables were initiated multiple times. Got it fixed and everything is now working as intended. Thanks Samer for the help.
Anton
2022-10-19 06:14 AM
Hi, the includes were correct. it was just that some variables were initialized 2 times and this did not cause any errors in the previous version (for some reason)
And i do agree with you that i should not update the version (for this exact reason) however we got a new sensor which had some drivers that were not available in the previous version. :grinning_face_with_sweat:
Thank you for the help anyway!
Anton