Skip to main content
Associate II
July 2, 2025
Question

STM32CubeMX freezes during code generation.

  • July 2, 2025
  • 1 reply
  • 474 views

Hello,
I am experiencing the following issue and would appreciate your help in resolving it:

  • When I create a new STM32 project for STM32G474CEU6 in STM32CubeIDE, main.c and other source files are not generated.

  • The .ioc file loads correctly and the GUI opens as expected, but a message saying “Code generation could not be done..” appears, and only the BSD_License.ftl file is generated.

  • When I press Alt+K to regenerate the code, only two files — common.ftl and mw_common.ftl — are added, and no error messages are shown.

  • In the Problems tab of the IDE, a warning appears: “Project '*' has no explicit encoding set**”, but this can be resolved by pressing Ctrl+1. However, even after fixing this and regenerating the code, nothing changes.

  • Under STWindow > Preferences > STM32Cube > Firmware Updater > Check Connection, a green check mark is displayed.

  • This issue occurs only on an old Windows 11 laptop. On a newer Windows 11 machine and on Ubuntu, code generation works perfectly.

  • I have tried completely reinstalling the latest STM32CubeIDE ver. 1.18.1 several times and changing the location of the firmware repository, but whenever I create a new STM32 project, the same issue persists.

  • This issue has been ongoing for over a year.

  • I then installed the latest version of STM32CubeMX (ver. 6.14.1) and created a new STM32 project.

  • Except for giving the project a custom name and selecting STM32CubeIDE as the Toolchain/IDE, I left all other settings at their defaults.

  • During the initial attempt, a message appeared suggesting that FW v1.6.0 was missing, and something started downloading, but I didn’t look at the details closely.

  • In any case, the message “Generating user source code...” is displayed, and the progress bar freezes at around 20%.

  • I vaguely recall seeing a message in a log file indicating that a Java exception occurred because 'UTF-8' was mistakenly written as 'UFT-8', but I’m not completely sure.

  • It might help to check the STM32CubeMX log files, but I’m not sure where to find them. Could you please tell me where to look?

Thanks!

This topic has been closed for replies.

1 reply

macalonAuthor
Associate II
July 2, 2025