Skip to main content
Associate
September 15, 2026
Question

STM32CubeMX2 Failing to Start

  • September 15, 2026
  • 9 replies
  • 131 views

I am running STM32CubeMX2 (1.1.1) on a Mac (Tahoe 26.6.2) and I did (with some difficulty) get it installed and running. I configured a MCU (STM32C552CEUx) and generated an STM32CubeIDE project. No problem.

I went back and copied the .ioc2 file, renamed it, and went to configure a different system. Everything was going fine until I tried to configure some new pins after adding middle ware (FreeRTOS and basic_stdio). I could not select pin functions in the graphic mode, table mode, or through activating the associated peripheral (I2C2) and updating the GPIO there. So, I closed CubeMX2 and restarted. Now I get the splash screens showing fine, but when they go away, I just get the spinning timer in the upper-left of an empty screen.

 

In file, I can click Close Window which it will dutifully do, but then I have nothing. In view, Reload and Force Feload do not seem to do anything.  

 

Any thoughts as to how to debug this would be greatly appreciated.

9 replies

Oussama_TROUDI
ST Technical Moderator
September 16, 2026

Hi ​@Martin Jay McKee, and welcome to STCommunity

Thank you for reporting this issue. To help us investigate and reproduce it, could you please share the following if possible?

  • Both .ioc2 files if available: the original file and the copied/renamed one
  • An Issue Reporter export (logs) for the current project and environment
  • Screenshots that may help with further investigation

Any details you can share will be very helpful for us to reproduce the problem and continue the investigation.

Best Regards
Oussama

In order 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.
Associate
September 16, 2026

I’ve attached the two .ioc2 files and a screenshot of where CubeMX2 is stalling. The second screenshot shows what happens when I go to Help in an attempt to create the Issure Reporter logs. 

If there’s anything else I can provide to help, please let me know.

Oussama_TROUDI
ST Technical Moderator
September 18, 2026

Hi ​@Martin Jay McKee 

Thanks a lot for sharing these details,

I'm currently working on it, I'll try to reproduce and get back to you asap.

Regards,
Oussama 

In order 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.
Associate
September 18, 2026

Thank you ​@Oussama_TROUDI. That’s much appreciated.

Oussama_TROUDI
ST Technical Moderator
September 29, 2026

Hello Martin,

I understand that the issue appears to be random. Do you recall taking any other actions before the issue occurred, such as installing packs or changing project settings? Any details about what you did before opening STM32CubeMX2 could help us identify the cause.

To help us investigate, could you please launch STM32CubeMX2 from the macOS Terminal with debug logging enabled?

  • cube mx start --log-level debug

Please continue launching STM32CubeMX2 with CLI command so that debug information is captured. By default, STM32CubeMX2 logs only errors, but we need the additional debug output to investigate this issue.

if the issue occurs again, please attach the generated log file from “/User/<USER>/Library/Preferences/stm32cube/logs”. 
A short screen recording showing the issue would also be very helpful.

 

I have also submitted an internal ticket to track this issue and will get back to you as soon as I have an update.
Internal ticket number: CDM0066116 (This is an internal tracking number and is not accessible or usable by customers).

Best Regards,
Oussama

In order 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.
Associate
September 29, 2026

​@Oussama_TROUDI Thank you again for looking at this. I was modifying some of the selected peripherals before I noticed that I was no longer able to select pin mappings in the pin definition screen. At that point, I restarted CubeMX2 (hoping to clear whatever the error was) and the startup failure showed up. I can’t remember exactly what I changed just before failure, however.

I do have a small update. I was able to get CubeMX2 to start up properly by starting from the terminal. It seems to work regardless of log level, so it appears to be something related to opening from the dock? In any case, I was able to save the environment when I got it started, so that is attached.

Visitor II
October 7, 2026

I am having the same issue.  I was working on a project, closed CubeMX2 to do other things, and now cannot restart the program to resume working on the project.

Associate
October 7, 2026

I will say, launching CubeMX2 from the command-line (as outlined above), got me back into it for the time being. I still can’t simply click on a shortcut, however. 

I’d certainly give 

cube mx start --log-level debug

​​​​​​
a try. If nothing else, it will provide another data point. 

Visitor II
October 7, 2026

Well I maybe stumbled onto something.

I am unable to run from the command line.  “cube” is not in my path.  I located it and tried running the following but it gave an error.

./cube mx start

 

However, I did try running “~/Application Support/STMicroelectronics/STM32CubeMX2_1.1.1/stm32cubemx2”.  When I did this, I got a permissions dialog asking for access to my Downloads folder (!?), and it seems to be working now.  So I suspect it may be a permissions issue.