Skip to main content
BMB
Associate II
Jul 16, 2026 5:29 PM UTC
Question

STM32CubeMX project generation issues with custom paths

Similar problems with STM2CubeMX v6.18.0 when generating STM32CubeIDE project and sub-projects structure for STM32N657X0HxQ processor. The only way to succeed is to have ‘Use Default Firmware Location’ checked and ‘Generate Under Root’ NOT checked.

Since I need to use ‘private’ SDK, later manually edited the .cproject and .project files accordingly :-( 

 

In my previous project I was able to use custom path (‘Generate Under Root’ NOT checked), that was STM2CubeMX v6.12.0 and the target was STM32U5 (SDK was STM32Cube_FW_U5_V1.5.0). I still have to adjust the paths manually from time to time and manually add required files.

In short, STM2CubeMX always seems to be broken one way or another ...

    4 replies

    Andrew Neil
    Andrew Neil
    Super User
    Jul 16, 2026 5:36 PM UTC

    ​@BMB - The accepted answer is that the issue was due to not correctly cloning the repository.

    Have you done that?

    If that hasn’t worked for you, it suggests you have a different issue ...

    A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
    BMBAuthor
    Associate II
    Jul 16, 2026 6:49 PM UTC

    This should NOT matter for the problem of .cproject and .project files not being generated.

    I SHOULD be able to point to any directory as long as it contains the structure expected. I work for medical projects so the SDKs end up being forked and reside on our git servers and are included as git submodules. This actually worked some time ago.

    I started with a project from Templates and then tried to recreate it and this has not worked unless I used the default path AND have the  ‘Generate Under Root’. 

    I tried already few clones of the SDK.

    HOWEVER: I tried to make a clean and simple project so I can zip it and present here and this time it WORKED (when using ‘Copy only the necessary library files’). 

    I will investigate this further, now I have a working project so I can compare it to non-working …

    … I wonder if this is the path depth or path structure issue …

    Moreover, whenever I try to create new project, use board selector or part selector STM32CubeMX tries and fails to download a file:

    … after that it seems to be OK …

    This happens every time, the ‘helpful’ suggestion is to ‘try it later’ ...

    Terms & ConditionsAccessibility statement