cancel
Showing results for 
Search instead for 
Did you mean: 

How to properly rename a dual-core project?

AraceliGuerrero
Associate III

Added dual-core to title - may be significant ...


Hello.

I've tried rename my project in the past, and this always generate a lot of errors due to the dependencies.
Which is the properly way?
I am working with STM32H755. Yes, dual-core.

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions

Thank you so much!


Well, after reading here and there, I was able to follow these steps in this specific order, and the errors that were previously occurring no longer showed up.

  1. In the IDE, rename the subprojects one by one. Keep the format ProjectName_CM4 and ProjectName_CM7. Press F2 and make sure the ‘Update references’ option is checked.
  2. Rename the root project, the one that contains the .ioc file. Press F2 and use the desired name.
  3. Delete the project from the IDE.
  4. Rename the folder, keeping the same name.
  5. Rename the .ioc file.
  6. Open the .ioc file in STM32CubeMX and generate the code.
  7. Import the project again into the IDE.
  8. Delete the Debug Configurations.
  9. Run ‘Clean Project’.
  10. Press Ctrl + B to build everything.
  11. Set up the debug configuration again.

View solution in original post

5 REPLIES 5
Andrew Neil
Super User

Which dependencies?

ISTR the IOC file doesn't get properly renamed - but a manual rename fixes it.

 

Maybe also Debug/Run configurations?

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.

Okay, I’ll write down what I did and the order I did it in. I haven’t touched this part again because it started breaking, but from what I remember, in the end it would generate warnings that didn’t appear at the beginning. I also got an error saying the linker was corrupted or something like that. And overall, it didn’t feel like a clean rename because some things weren’t updating properly.

  1. From the IDE, select ‘Rename’, press Enter, and wait.
  2. The .ioc file doesn’t change, so I modify it manually.
  3. Open CubeMX and check in Project Manager, because sometimes the name doesn’t get updated there.
  4. Open the CM4 folder, modify the .project file to update the <name> tag with the new name. Do the same in CM7.
  5. In CubeMX, click ‘Generate Code’ to make sure everything has the new name.
  6. In CubeIDE, select ‘Clean Project’.

At this point, I start getting redefinition errors.

I've never found it necessary to hack the .project file.

But I've only ever done it on single-core projects - so that might make a difference ...

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.
Ghofrane GSOURI
ST Employee

Hello @AraceliGuerrero 

I believe there is no official, one-step rename feature for dual-core projects in STM32CubeIDE. I have raised this request #0060931 to the development team for a feasibility assessment.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Thank you so much!


Well, after reading here and there, I was able to follow these steps in this specific order, and the errors that were previously occurring no longer showed up.

  1. In the IDE, rename the subprojects one by one. Keep the format ProjectName_CM4 and ProjectName_CM7. Press F2 and make sure the ‘Update references’ option is checked.
  2. Rename the root project, the one that contains the .ioc file. Press F2 and use the desired name.
  3. Delete the project from the IDE.
  4. Rename the folder, keeping the same name.
  5. Rename the .ioc file.
  6. Open the .ioc file in STM32CubeMX and generate the code.
  7. Import the project again into the IDE.
  8. Delete the Debug Configurations.
  9. Run ‘Clean Project’.
  10. Press Ctrl + B to build everything.
  11. Set up the debug configuration again.