.ioc file specification and data import

[Alejandro Bizzotto]

CubeMX and STM32CubeIDE will generate a .ioc file associated with the configuration of the MCU to be programmed. For a modest project with few connections, adding the GPIO and their labels is normal, but when there are 130+ signals this become a tedious and error prone task.

We need a way to import data into CubeMX. 

@st team: please add a function to CubeMX/STM32CubeIDE to import a list of GPIO, pin, port, config, etc into the configuration of the MCU which is being used.

Alternately/in the meantime: you could also publish the full specification of the file and its fields, so we can modify it with some scripts.

Thank you in advance.

[Ghofrane GSOURI · Accepted solution]

Hello @Alejandro Bizzotto  

Your change request has been submitted to the development team for a feasibility assessment.

The internal ticket number is 216942.

Thank you very much for your valuable contribution.

Ghofrane

[Alejandro Bizzotto]

For anyone who is interested in automating these kinds of works (adding a bunch of signals/labels to CubMX), I found a way to use AI for this.

I have the signals assigned and connected in my schematic (in Altium) and a list of signal-names -> port-names in a spreadsheet (Excel), in this list the correspondence with the pin numbers was not specified.

To get the correspondence between the signal names, ports and pin numbers I feed Claude with a print of the schematic in pdf format.

I made the connections in CubeMX of the peripherals and a few more pins, then I take that .ioc file and give it to Claude, asked it to generate a new file including the connections which are present on the list it generated before but not in the .ioc file. 

Claude somehow figured out the proper format of the fields of the file and generated a new one which I was able to open with CubeMX, not all the signals are there, but from 124 I needed to attach and label only 8 are missing. Good enough!

Before using Claude for this I tried ChatGPT, Gemini and qwq (in local), none was able to generate a working .ioc file, Claude somehow figured out how that file works!