2025-10-06 7:16 AM - last edited on 2025-10-06 8:11 AM by STTwo-32
Hi Champs,
one of my customers develop on STM32WBA54KGU6. This SoC does not come with SMPS.
Although he selects the righ reference (STM32WBA54KGU6) for code generation, SMPS seems to be used by default - he has to comment the line out form generated code to build properly.
he uses the latest dev tool versions :
is it a known issue?
please note that it is not a blocking point but it still requires a post code generation control from his side to comment out the generated SMPS statement in the generated code.
Warm regards, Agnès
Solved! Go to Solution.
2025-10-08 11:29 PM - edited 2025-10-09 12:55 AM
Hello All,
Thank you for having reported this issue
I escalated this request internally for fix (ticket number: 219199)
(PS: ticket number: 219199 is an internal tracking number and not available outside of ST)
2025-10-06 8:14 AM
Salut @agnes
Could you please attach the .ioc file of your customer (or send it as a privet message). There is not a known issue about SMPS code generation for the STM32WBA54.
Best Regards.
STTwo-32
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.
2025-10-08 8:46 AM
2025-10-08 10:33 AM
2025-10-08 11:29 PM - edited 2025-10-09 12:55 AM
Hello All,
Thank you for having reported this issue
I escalated this request internally for fix (ticket number: 219199)
(PS: ticket number: 219199 is an internal tracking number and not available outside of ST)
2025-10-09 2:12 AM
It seems this is a known behavior with STM32CubeIDE code generation for STM32WBA54 devices. You may want to this related discussion for more details and possible workarounds:
https://community.st.com/t5/stm32-mcus/visit-stm32cubeide-smps-configuration-issue/td-p/832475
2025-10-09 7:45 AM
Hi @agnes
The issue is reproduced with your ioc file, and I think that your IOC file may be corrupted.
When creating a new IOC file from scratch and enabling the same IPs, the generated code was correct and did not exhibit the issue.
Could you please check if the issue occurs with the attached ioc file?
If you have a specific scenario or additional steps that we can follow to reproduce the issue, please share them here.
2025-10-20 5:29 AM
Hello @agnes ,
Were you able to resolve the issue with my attached ioc file?
Do you agree with my assessment, or is there anything you would like to add?
I will wait for your feedback.