Can STM32CubeIDE change a processor within a current workspace/project

[CharlieMangold]

STM32CubeIDE

Version: 1.12.0

     We have an older Atollic TrueSTUDIO workspace that we want to migrate to a STM32CubeIDE. The original plan was to take one of our newer STM32CubeIDE projects, change the processor and then import the older source code files. The question we have is that there does no seem to be an easy way to change the processor in STM32CubeIDE, even under the Device Configuration Tool. In Atollic you could go into the project settings and use a pull-down to simply change the processor. Do you have to create a new project and then import the the original code into it to change a processor?

Thanks

 

[STTwo-32]

Hello @CharlieMangold 

For the migration from the Atollic TrueSTUDIO to STM32CubeIDE, I suggest you to take a look at the UM2578 that could give you some help.

Best Regards.

STTwo-32 

[CharlieMangold]

We have migrated several older Atollic projects but it is much easier to take one of our newer STM32CubeIDE projects and change the processor(all the needed drivers/paths are already there.) Is it possible to change to processor or do we have to start all over ?

 

Thanks

[TDK]

In short, this isn't a supported function and there's not really a straightforward way to do so.

There are some things you can do. Load your IOC in STM32CubeMX and list compatible MCUs (in Pinout menu, or Alt+L) and select one and import. This will change the processor and import your settings, but it won't transfer user code.

You can clone the project and then edit the IOC file directly (along with the .project file), although this is not straightforward.

[CharlieMangold]

It seems like in ST's effort to try an simplify starting a project from scratch has made it more difficult creating a new workspace from a very similar one. We like to keep the drivers and code within the same workspace so it is very portable and not dependent on numerous installations/paths. Once we have a proven workspace(with our own pin setup/config) it used to be a simple processor change to begin working on a similar board or changing the processor on a current one. I now have to create/document a new procedure for this process all because ST has locked the Device Configuration Tool into begin a core component of workspace/project maintenance. I can understand using the tool if you need it but locking processor selection into the tool is a mistake for us.

Thanks for all the help.