Skip to main content
Associate III
September 11, 2024
Solved

STM32CubeIDE doesn't save clock configuration

  • September 11, 2024
  • 3 replies
  • 1362 views

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.

    This topic has been closed for replies.
    Best answer by mƎALLEm

    @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

    3 replies

    mƎALLEm
    Technical Moderator
    September 11, 2024

    Hello,

    What error is displayed? Could you please share your ioc file?

    Associate III
    September 11, 2024

    Hi, 

    I share some pictures of the problem. To correct the problem, I change the SMPS Clock Mux to HSE as shown in the tutorial. However, when I generate the code and save it goes to HSI again. I attach also the ioc.

    Thanks.

    Screenshot 2024-09-11 154740.png

    Screenshot 2024-09-11 154745.png

    Screenshot 2024-09-11 154756.png

    mƎALLEm
    Technical Moderator
    September 11, 2024

    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.

    mƎALLEm
    mƎALLEmBest answer
    Technical Moderator
    December 2, 2024

    @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

    Associate
    November 21, 2025

    Hi,

    I have the same issue with CubeMX V6.15.0

    Is there some way how to fix it? Thanks.

    DavH42_0-1763711741604.png

    DavH42_1-1763711756700.png