2026-03-01 11:51 AM - last edited on 2026-03-02 4:41 AM by Andrew Neil
CubeMX does not generate .project and .cproject files for cubeIDE, when in CubeMX project it is selected to not use default firmware location, and path set to folder with STM32Cube FW from github.
To reproduce:
1 Open CubeMX
2 Select File->New Project
3 Select chip, in my case stm32g491ceu6
4 Open Project manager tab, enter name and location for the project, toolchain - stcubeide
5 Uncheck "Use Default Firmware Location", Click Browse and navigate to a folder with github repository with cude FW package
6 Go to "Code Generator" sub tab, select radio button "Add nevessary library files as reference in the toolchainproject configuration file"
7 Click generate
8 Observe folder content in the file explorer - .cproject and .project are missing.
CubeMX version 6.16.1
Solved! Go to Solution.
2026-03-03 10:33 AM
@trs wrote:a github repo (https://github.com/STMicroelectronics/STM32CubeG4) cloned on my machine,
ST's GitHub repos rely on submodules - so you have to follow the instructions to clone correctly:
Did you do that?
2026-03-01 1:28 PM
Just tried this and both .project and .cproject showed up as expected. Maybe you missed a dialog box, or maybe you have some other project setting which is incorrect, or maybe you have "dot" files hidden.
It is easier to debug STM32CubeMX issues when you attach the IOC file that produces the incorrect behavior.
2026-03-01 7:00 PM
Thank you for support. Attaching my STM32CubeMX project with the IOC file.
These are all files that I get after pressing Generate button.
2026-03-01 8:22 PM
I do not see an attached IOC file.
2026-03-01 8:29 PM
2026-03-02 4:33 AM
> ProjectManager.CustomerFirmwarePackage=..\\..\\libs\\STM32CubeG4
Maybe a relative path is supported in the "Firmware Relative Path" box.
I can't test out your IOC exactly because our library paths are not the same. With a non-default absolute path, everything works for me.
2026-03-02 11:52 AM - edited 2026-03-02 11:55 AM
Cannot reproduce this problem. Tested with relative path:
ProjectManager.CustomerFirmwarePackage=..\\CUBELIBS\\STM32Cube_FW_C0_V1.1.0Though in the CubeMX GUI the path is displayed as absolute (and it does not let user edit in place), in the ioc file it is relative.
2026-03-02 3:37 PM
If you open IOC file I shared before, can you get to generate STM32CubeIDE project?
As soon as I check the box "Use Default Firmware Location" the project generates normally. Then if I uncheck the checkbox, click Browse and navigate to a github repo (https://github.com/STMicroelectronics/STM32CubeG4) cloned on my machine, all files in the project's Drivers folder are gone, and there is no path in .project file to any source file anymore, including main.c.
The GUI says Relative path, which is I suppose automatically resolved into a relative path, as there is no way to paste any text into the text box. The only way to set the path is to click Browse button. Is it not the case on your side?
The path it resolved, after I navigated to the repo through Browse button click - is correct:
ProjectManager.CustomerFirmwarePackage=..\\..\\libs\\STM32CubeG4
Here is my folder structure, where STM32CubeG4 is a submodule in main Git repo:
2026-03-02 3:55 PM
> a github repo (https://github.com/STMicroelectronics/STM32CubeG4) cloned on my machine
Maybe this is the issue. What if you use the standard way of installing the package? (Help -> Manage embedded...)
You can't just mix and match any repo version with any CubeMX version.
2026-03-02 5:43 PM
You are probably correct. I don't want to try installing firmware package as the STM32CubeMX already installed it's own package and I know that is working.
So the issue is that github repo != installed package. Which is unfortunate, as it would blend very nicely with having a github repository within your project repository, where FW package is a submodule in it. This is attractive because:
A) it is easy to get updates - no installation is required;
B) modifications to the FW library are easy to keep track of because I would create a separate branch, and would always see what I changed in the library and why;
C) integration of my changes and updates is a breather as I would merge/rebase my branch of the FW library.
Anyway, thank you for the help! Hopefully this will be possible in near future.