Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32

Forum List Topic List

[ prev topic ]  

.project file links duplicted during STM32CubeMX code regeneration

Posted by gshera on 2015-07-09 04:10

I have observed that when code is regenerated from STM32cubeMX (4.8.0) the .project link entries become duplicated at the end of the file instead of replaced. This does not yet cause a problem since eclipse appears to handle it by giving priority to the latter entries but if files have been removed in later configurations, the links in the project will still exists and be compiled.

I have tried this on 2 different processors including the default configuration for the STM32F429I-DISCO board.

For a particular project, the duplicated links have the correct file but the for the duplicated entries all had the same locationURI entry, causing in all files linking to a single file. This results in compilation failure. Additionally the order of the file entries was randomized preventing comparison with the committed .project file. The only solution was to remove the .project and .cproject files before code generation. This causes other problems such as total loss of project configuations and path setup to non-generated files.

Is there any way to prevent this?
My workflow is ensure eclipse is closed,
Open the .ioc file, make changes, in CubeMX,
Genenerate Code
Re-Open preovious workspace.

The project higherarchy follows the guide:
http://www.openstm32.org/Importing+a+STCubeMX+generated+project?structure=DocumentationQuestion
I do not rename the project or generated files.

Reads: 10374
Link
Posted by gshera on 2015-07-26 23:07

No improvement with 4.9.0
Also posted on STM32 Software Tools and Firmware forum. I’ll update if resolved.

Link

Posted by mtutak on 2016-01-08 15:26 Poland

I have similar issue. I believe this is bug on STM32CubeMX side.

After manual adding new project files, Eclipse changes tag with in “.project” file.

These tags make STM32CubeMX unhappy with project regeneration and ends with error: “...SW4STM32 project generation have a problem.”. After this error project wont compile anymore...

Do you found any solution to avoid this problem? Manual replacing back to is a bit annoying.

Link

Posted by borrisl on 2016-04-21 09:43

I have this problem as well and it is very frustrating. To understand the origin of the issue, is seems that when I add other files to the project this error occurs on the next CubeMX code generation.

What I need clarification is, if there is a way to manually correct this, how?

Link
Posted by gshera on 2016-04-22 18:33

I was contractor on this project for several months, and have since moved on. I’m working from memory here so your results may vary and this may not be completely how I did it but hopefully you’ll get the idea.

Source control is essential, be sure you have a committed version before you perform the changes in CubeMX.
AFter changes in CubeMX, compare in the .project file against the committed version, and look at the file link difference. (we were using subversion, diff with winmerge or meld). Some manual comparing and editing is required. Forunately the order of the files is normally kept in tact so the compare is not terrible.
In your difference viewer, in the new file, delete the section of old file paths that match committed version and refresh. The new diff will show the old file paths nearly matching the file paths with the bad locationURI, plus and additons and deletions, from here you should be able to update the old paths from the committed version (keep in mind additions and deletions).

You may also try to re-arrange the order of the files before editing in CubeMX.. I also did find in some cases re-creating the project resulted in a different file order in the .project file, and the edits from CubeMX worked correctly.

Good luck.

Link