Skip to main content
Associate II
September 19, 2024
Solved

Project folder and .ioc file with different name in STM32CubeIDE

  • September 19, 2024
  • 2 replies
  • 2352 views

Hi everyone, I have question for a particular situation. Me and my collegue are working on the same project in STM32CubeIDE but something really strange is happening: On his laptop the project forlder and the .ioc file have a different name and everything is working correctly, If I try to do the same on my laptop I can't do it and if I try to open the .ioc file it says

Screenshot 2024-09-19 124415.png

The thing is, my collegue is not doing this on purpose. Is there a way to generally make it work or is it just a bug?

    Best answer by Andrew Neil

    Are you both using the same version of CubeIDE?

    Did you both import the project into your workspaces in exactly the same way?

    Maybe show screenshots of the Project Explorer window for each project?

    2 replies

    Pavel A.
    Super User
    September 19, 2024

    Maybe your colleague uses standalone CubeMX? Only CubeIDE has the requirement that ,ioc file has the same name as the project (or folder).

    In any case just use the standalone CubeMX (a compatible version. Several CubeMX versions can be installed side by side).

    Associate II
    September 19, 2024

    Hey, Pavel thank you for your answer but no, he uses CubeIDE and he opens the .ioc file in CubeIDE. That's why I am really curious of how he can do it and I can't (almost Jelous)

    Andrew Neil
    Andrew NeilBest answer
    Super User
    September 19, 2024

    Are you both using the same version of CubeIDE?

    Did you both import the project into your workspaces in exactly the same way?

    Maybe show screenshots of the Project Explorer window for each project?

    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.
    Karl Yamashita
    Principal
    September 19, 2024

     

    Show the screen capture of the project trees for both project.

     

    And why would the IOC file be named differently from the Project name? Is it totally different names or does the IOC have a revision appended to the name?

     

    Better yet, instead trying to figure why your colleague's work, just rename the IOC file to be the same as the project. Be careful of underscores and hyphens https://community.st.com/t5/stm32cubeide-mcus/nucleo-h563zi-project-from-touch-gfx-will-not-show-ioc-in/m-p/719979#M30649

     

    If you want to rename the Project to a useful name instead of the board name then see this video https://youtu.be/AizWAlbU4Og?si=FtZQihm-bNsBpxH_

    It's been years and TouchGFX team still hasn't fixed the simple naming issue. If you create an A/B project using the same board, you can only open 1 of the projects at a time because the IDE sees it as the same project. 

     

    If a reply has proven helpful, click on Accept as Solution so that it'll show at top of the post.CAN Jammer an open source CAN bus hacking toolCANableV3 Open Source
    Associate II
    September 20, 2024

    We are both taking the project from the same git folder and have the same workspace, it's just that on his laptop he can have the project folder named "Firmware" and .ioc is a complete different name. If I try to open it on my laptop I have to change the .ioc name to be able to open it. We are trying to avoid naming problem in the future, that's why we are trying to solve this issue. 

    Andrew Neil
    Super User
    September 20, 2024

    @Simo_Sappo wrote:

     it's just that on his laptop he can have the project folder named "Firmware" and .ioc is a complete different name.  


    The name of the folder in the host filesystem doesn't have to be the same as the name of the Project within the IDE.

    The Project tree structure within the IDE does not necessarily map directly to the folders in the host filesystem.

     

    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.