2023-11-23 04:59 AM - edited 2023-11-23 05:43 AM
STM32CubeIDE 1.14.0 was released today on st.com as well as an in-tool update patch.
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.
2023-11-23 05:40 AM - edited 2023-11-23 05:41 AM
@Semer CHERNI maybe you want to complete the fixed issues and known issues/limitations section by adding the link to the wiki?
2023-11-23 05:46 AM
Hello @t.decker
Thanks for mentioning it :).
I made the updates.
KR,
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.
2023-11-29 03:29 AM
@Semer CHERNI The hard-coded keyboard shortcut to login (alt+L) is still there on 1.14.0. This gives the problem on Mac, that you are not able to type @ (on Apple QWERTZ-keyboard). Please make this configurable!
JHi
2023-12-05 05:14 AM
Hi, It would be great to add new button in Help menu "Report STM32CubeIDE bugs"... It is not clear where the customer can get a suuport
2023-12-05 04:02 PM
I have been using 1.7.0 from my F411 project.
Recently I downloaded and installed 1.14.0, only to find it cannot compile my 1.7.0 project.
Is it normal? How to make it work or shall I just stick with 1.7.0 IDE?
2023-12-05 04:45 PM
@HDaji.1 Yes this is normal. Change is a curse, as a Chinese proverb says, and it is inevitable.
This is a technical forum, if something does not work after upgrade, please share relevant details.
2023-12-05 06:25 PM
Thx for the advice.
After I checked carefully, the errors are related to some shared variables, which I put in main.h.
Compiling is OK; just ld complains multiple definitions in IDE 14; strangely IDE 7 does not.
2023-12-06 06:59 AM - edited 2023-12-06 07:05 AM
@HDaji.1 thank you for the clarification.
> ld complains multiple definitions in IDE 14; strangely IDE 7 does not
This is because of new GNU compiler installed with IDE v. 1.14. TL;DR they changed the rules about multiple definitions that were ok before. To resolve, either install the older toolchain, same as you've used with v 1.7 (in the Toolchain manager) or change your code per the new rules.
The warning can be also disabled by some compiler option - but IMHO this is less desirable. Either use the old proven toolchain and avoid other compatibility issues, or deliberately update the toolchain and fix the code per the new rules.
2023-12-11 01:32 AM
After updating the ST link firmware, it refuses to detect the target and bricked two original debuggers. Don't update the firmware. Before the firmware update st-link worked