STM32CubeIDE doesn't save clock configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-11 6:35 AM
Hi, I'm facing a problem with the Clock Configuration tab with the latest version of the STM32CubeIDE. In fact, every time I open the ioc file, there is an error with the SMPS Clock Mux on the STM32WB board I'm using. I correct and generate code and saved but when I open the file again the error is still there. I'm using the latest version of the Cube.
Thanks.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-02 12:57 AM
@mÆŽALLEm wrote:
I reproduced the behavior.
I will escalate the issue internally and get back to you as soon as I have an answer/feedback.
Internal ticket 190817 for follow-up.
Issue fixed in CubeMx V6.13.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-11 6:46 AM
Hello,
What error is displayed? Could you please share your ioc file?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-11 6:50 AM - edited ‎2024-09-11 7:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-11 7:03 AM - edited ‎2024-09-11 7:16 AM
I reproduced the behavior.
I will escalate the issue internally and get back to you as soon as I have an answer/feedback.
Internal ticket 190817 for follow-up.
Thank you for your patience.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-02 12:57 AM
@mÆŽALLEm wrote:
I reproduced the behavior.
I will escalate the issue internally and get back to you as soon as I have an answer/feedback.
Internal ticket 190817 for follow-up.
Issue fixed in CubeMx V6.13.0
