2022-07-01 01:41 AM
Hi,
I am experiencing issues migrating projects from STM32CubeIDE 1.9.0 to 1.10.0. After performing the migration, a number of custom project .c/.h files are deleted from the project and filesystem, and some are completely replaced, deleting /*USER CODE*/ sections.
After installing the new application (help->check for updates) and restarting Windows 10 system I perform the following:
If I open the .ioc again and force another code generation, the peripheral .h are correctly regenerated (but as the files were previously deleted, all the /* USER CODE */ sections in these headers are gone).
I have tried rolling back, creating a new workspace directory and importing the project into the new clean directory but the result is the same (and repeatable).
I have tried a completely separate project for a STM32G0. In this case custom .c are deleted but not custom .h.
Our projects are structured with the project code separate from the workspace directory. After some experimenting, I have determined that if I directly copy the project code folder into a new workspace directory and perform the same process, the issue does not seem to occur.
Can anyone suggest what might be causing the issue or point to angle to investigate?
I would like to get to the bottom of it before committing to migrating all our projects (and avoid regenerating/restructuring projects as part of the migration).
Note sure if it is relevant but I have noticed that the file name format of the .mxproject has changed.
Thanks!
Solved! Go to Solution.
2022-07-07 05:33 PM
Please see response from @Sara BEN HADJ YAHYA on separate thread here:
2022-07-01 05:24 AM
Hello @Community member ,
Thanks for your feedback,
There is indeed a CubeMX issue, it seems that the custom source files, system_stm32f4xx.c, sysmem.c and syscalls.c get removed when the project is migrated from MX v6.5.0 to MX v6.6.0.
The header files are always generated correctly, I tried several tests but I couldn't manage to reproduce this part. Could you please share your ioc file before project migration if you still have a copy or help me with a detailed scenario.
I apologize for the inconveniences,
Sara.
2022-07-01 06:51 AM
I reported same , but i choice leave MX version on project (my 6.3) .
2022-07-01 02:15 PM
Hi @Sara BEN HADJ YAHYA ,
Thanks for the confirmation.
After further digging, I have noticed that some files are also deleted/overwritten in the TouchGFX/target/ directory.
What is ST's recommendation at this point for active development? Roll back to 1.9.0 or stick with 1.10.0 without migration?
Thanks
P.S. I have messaged you the offending .ioc file before project migration.
2022-07-02 01:26 AM
This deletion occurs only once. After this copy files back from backup and all works for me.
But yes migration is complicated, some things you need run twice etc.
2022-07-03 02:57 PM
Thanks @MM..1
On the flipside, my attempt to use 1.10.0 without migrating does not work. The files are deleted on a subsequent code generation, regardless of the selection.
I'm going to let the dust settle and see what ST comes back with before migrating all our projects.
Cheers.
2022-07-07 05:33 PM
Please see response from @Sara BEN HADJ YAHYA on separate thread here: