[Resolved] STM32CubeIDE project creation issue

[Semer CHERNI]

Updated post to reflect permanent fix

Dear STM32CubeIDE user,

Further to the recent STM32CubeIDE project creation issue, we would like to inform you that a solution is now available for you.

This permanent fix applies to all STM32CubeIDE versions.

1. Issue description

When creating a new STM32 project in STM32CubeIDE, the “STM32Cube” radio button may have become unresponsive, blocking the “Next” button after the product selection screen. This prevented the project creation from being completed.

2. Permanent fix

You can apply this resolution to any STM32CubeIDE version, even if you applied the temporary workaround that we recently shared with you.

1. Open STM32CubeIDE.
2. Refresh the database.
   Go to Help > STM32Cube updater > Select “Check the Target selector Device Database Updates”
3. Restart STM32CubeIDE
4. If you deactivated the auto refresh function previously, you may wish to reactivate it for all your STM32Cube tools. Here is how to proceed:

• STM32CubeIDE:
  Go to Window > Preferences > STM32Cube > Firmware Updater.
  Select your preferred auto-refresh option.

• STM32CubeMX:
  Go to Help > Connection & Updates > Updater Settings.
  Select your preferred auto-refresh option.
• STMCUFinder:
  Click on the Settings icon > Settings > Updater Settings.
  In the "Database Auto-Refresh" section, select your auto-refresh option.

We apologize for any inconvenience caused by this temporary issue.

If you require further information or assistance, please contact our customer support.

Best regards,

STMicroelectronics

[Andrew Neil]

For reference, some recent posts which seem to be encountering this issue:

v1.16.0: STM32Cube Option disabled during project creation; No .ioc File Generated

stm32 targeted project type is empty and its not generating .ioc file

CubeIDE 18.1 does not create CubeMX project - no .ioc file

ioc file not generating

.ioc file generation

No .ioc file generated; FPU not initialised

 

PS:

Possibly another: NUCLEO-H743ZI2 board not supported in STM32CubeIDE - Obsolete

[DocAlex]

Hello,

 

I am using 1.19.

 

I deleted (as told) 

.stm32cufinder, .stm32cubemx, .stm32cubeide and .stmcube

I set the option to "no Auto refresh"

restarted the IDE. 

It still does not work. I cannot select an STM32 project. No .ioc

 

What to do?

[Andrew Neil]

---

@DocAlex wrote:

I am using 1.19.?

---

As noted in the original post by @Semer CHERNI , this thread is about version 1.18.1 and earlier - so shouldn't affect v1.19.

 

---

@DocAlex wrote:

It still does not work. I cannot select an STM32 project. No .ioc

---

This is about creating a new project - not sure what you mean about "selecting" a project?

Please give a full description of what, exactly, you are doing - maybe you have a different issue...?

Screenshots may help.

https://www.techrepublic.com/article/how-to-take-screenshots-in-windows-10/

[JDoe.2]

Once again ST screws-up and reveals behavior worthy of ***-stain companies like "Meta", "Microsoft" or "Google". What I'm seeing is that I had a tool that worked, used internet access even though it doesn't need to, and suddenly some functions are blocked... and the only fix is to update to a new version.

None of us needs nor wants to have to login to use an IDE. None of us wants to be forced to update. And definitely none of us wants to be at the mercy of people with a kill-switch for the tools we use to make a living.

Because for me it's very clear: you have, inadvertently or not, revealed that you can kill someone's CubeIDE install whenever you want. I did not get a message about an update or anything. One day it worked, the next it was broken. What else are you doing in my back? Copying all the code I write for my employers? Feeding it to an LLM, maybe?

I've already stopped recommending ST MCU's at work because A/ too many hardware bugs on new IP blocks B/ your tools AND third-party tools are nowhere near worth what they cost and now C/ it feels like you're following every "the consumer is the product" trend in the world.

And let's not forget the "on by default" spyware we have to disable in CubeIDE's settings with every update. I have never and never will share information with you willingly. Disable it by default, you're only aggravating me and people like me. You know, the people who make product recommendations to companies that translates into sales for your products.

[Amel NASRI]

We understand your concerns and are fully committed to helping you overcome the recent issues with STM32CubeIDE to ensure continuous operation. We sincerely apologize for any inconvenience caused.  

We value your feedback and would like to provide clarification on the points you have raised.

• We have identified the root cause behind this issue, and we are currently resolving resolved it.

The problem is due to a change in our database, which impacts current versions already deployed.

Edit: Permanent fix is available. Please refer to the updated original post or to the notification mail that you should have received.

• Developers are never forced to update the versions of their tools.

As part of our software management lifecycle process, ST releases regular updates for multiple software packages to add new features or to fix issues on specific versions.

We are maintaining public access to all the versions of our tools and we have no intention of forcing developers to update them. The permanent fix shared for all previous STM32CubeIDE versions is proof of our commitment.

• Rest assured that using STM32Cube tools is safe. Furthermore, the handling of your personal data is fully compliant with GDPR rules.

ST takes user privacy and data protection very seriously. Our STM32 tools are fully compliant with our corporate privacy statement.

Our tools collect anonymous data to improve future versions but we never use or copy developer code. The collection of analytics can be disabled in the tool settings.

• We are removing the login from our tools and replacing it with a notification service.

Login information is used to communicate updates and fixes to developers. We are replacing this approach with a notification service. Users will be offered the choice to subscribe to notifications.

For more details on upcoming changes and improvements, you can refer to the post STM32CubeIDE 2.0 Release - Early Heads-Up, which outlines our plans to enhance your experience.

Your feedback is valuable, and we aim to ensure STM32CubeIDE meets your expectations. Please feel free to share any additional insights or suggestions.

[Andrew Neil]

---

@Amel NASRI wrote:

• Developers are never forced to update the versions of their tools.

---

Unfortunately, this particular issue has affected even people who were not doing updates!

[fkardame]

I tried re-installing cubeide and also followed the steps. It still does not allow to create STM32 project type. 

 

Deleted all .stm32 directories and started stm32cubeide and still the same. 

 

 

UPDATE: Resolved after deleting the workspace directory and now it allow to create STM32Cube project type. 

UPDATE 2: It greyed out again after first attempt. So everytime I have to clear workspace .metadata directory

UPDATE 3: I cannot get it work anymore. I even tried uninstalling and reinstalling cubeide after deleting all .stm and workspace directory.

Please provide permanent solution as this is the second time I had to spend 2 hours in debugging this issue.

Please advice. 

[Ghofrane GSOURI]

Hello @fkardame 

Could you please provide more details about the STM32CubeIDE version that you are using.

THX

Ghofrane

[fkardame]

Hey,
I am on latest version 1.19.0 

[jintse]

im facing the same problem. im using 1.19version in mac. i've tried to follow the instruction as said, but i could not find folder “.stmcufinder” to delete. where is the exact position in mac? 

[sergey23]

It's in your $HOME

rm -rf ~/.stmcufinder/

Those "solutions" don't work for me nevertheless, I am trying to start 1.19 on my Mac for hours now with no luck, deleting and reinstalling everything multiple times.

[sergey23]

Like, ST people, seriously? This is not something subtle. This is basic stuff.

[elshazlio]

This is so unprofessional and unbecoming of ST.

[dantronics]

Sitting here at work trying all of these options, nothing is working. Using 1.19.0. We need a solution IMMEDIATELY ST!

[Lokesh23ms]

Hello @Semer CHERNI @Ghofrane GSOURI 

 

You mentioned there is a new database published for 1.18.1 or older versions. 
Where is that database? How to use it? I am using 1.15.1, so what am I supposed to do? 

[Ghofrane GSOURI]

Hello @Lokesh23ms 

We recommend forcing a database update using the following procedure: Help>
STM32Cube updates > Check for target selector device database updates.

By following this step you will be able to use the new database published for 1.18.1 or older versions.

THX

Ghofrane 

[tje7415]

For those using mac, the folder in question is located under your user home folder. open a window to your home folder, then press command+shift+(period key). this will make the hidden folder viable. 

This is unacceptable. If we use this software at the main IDE thinking we are going to get the OEM experience by using your chips, we should at least expect to not have to update to keep the current IDE working. This shows that ST has some sort of ability to remotely force users to update even if it was unintentional. 

[funnywit_02]

I followed all the suggested steps, changed the auto-refresh setting, deleted the .stmcufinder  folder, and restarted STM32CubeIDE, but the issue still persists on my end.

Even after disabling auto-refresh, the IDE downloads the .stmcufinder folder again on startup, and the STM32Cube option remains greyed out during project creation. I'm using STM32CubeIDE v1.19.0 on Windows and this is blocking me from creating CubeMX-based projects.

Is there a way to prevent the database from being re-downloaded or to manually install the compatible database for v1.19.0?

[elshazlio]

It did not work for me, even after following the steps.

[V3J_WJ]

I had the issue with the latest version STM32CubeIDE 1.19.0 and this solution worked out great. Before doing that, I installed the latest CubeMx as well.