How to use supplied .ioc file when importing CubeMx project?

Sysprogs forums Forums VisualGDB How to use supplied .ioc file when importing CubeMx project?


This topic contains 3 replies, has 2 voices, and was last updated by  support 1 year ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #33415


    Using the STM32CubeMx Project Wizard, VisualGDB will open the STM32 CubeMX tool.

    At this step, how can I use  the .ioc file provided by the project to be importet?

    Configuring the target by hand at this step would be unnecessarily painful.

    Loading the provided ioc file at this step does not work (the empty ioc file will nevertheless be imported upon closing the STM32CubeMx window)



    Thanks for confirming your license. The .ioc files contain settings for the STM32CubeMX generator and do not directly reference any source files/build settings or anything else that could be imported.

    In order to import them into VisualGDB, you would first need to open them in STM32CubeMX, then generate an STM32CubeIDE project, and finally import the generated STM32CubeIDE project using the VisualGDB Embedded Project Wizard.



    I do have a complete “STM32CubeMx project” containing all the source files and in addition an ioc file that was edited according to the target  type, the ports, the clocks, etc.

    When I try to import the project into Visualgdb, CubeMX is beeing opened requiring to produce a new ioc file which is very difficult to make it the same as the ioc file already existing, since one has to go through a lot of settings options..

    Why is it not possible to use the fully prepared ioc file from the project folder to be imported?


    You must be logged in to view attached files.


    Unfortunately, it is hard to suggest anything specific based on the description you provided.
    In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
    Please provide complete and detailed steps to reproduce the issue as described below:

    1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
    2. Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch. If the problem happens with a specific ioc file, please provide the steps (with full uncropped screenshots) how you create that file.
    3. The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.

    You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.

    Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.