How to avoid project migration issue in STM32CubeMX v6.6.0 and STM32CubeIDE v 1.10.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-04 2:47 AM
A regression was detected when a project is migrated to the latest STM32CubeMX v6.6.0. The following source files got removed from Core/Src folder after the migration.
- system_stm32xxxx.c
- sysmem.c
- syscalls.c
To avoid this issue, please apply one of the following workaround:
- Delete .mxproject file before performing project migration
- Move or copy the whole project in another location before project migration
We are working on a patch release for MX and IDE in which the described issue will be fixed. The patch will be available soon.
We apologize for the inconveniences.
Solved! Go to Solution.
- Labels:
-
STM32CubeIDE
-
STM32CubeMX
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-08 8:02 AM
Hello,
This issue is fixed.
STM32CubeMX v6.6.1 and STM32CubeIDE v1.10.1 are now available under st.com
Sara.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-06 8:06 AM
After this update, I also noticed the generator added several LL driver header files, even though I have only HAL drivers selected:
Build still works fine but I expect the files are added unintentionally.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-06 9:40 AM
@Sara BEN HADJ YAHYA​ By the way - what is the purpose of the .mxproject file?
It seems to only make trouble. I always delete it and neither CubeMX or CubeIDE complained.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-07 7:03 AM
Hello @ARaym.2​ ,
Thanks for your feedback,
This is actually a normal behavior, it is new implementation done in MX v6.6.0.
Several users needs to switch between HAL and LL in their projects so starting from v6.6.0, MX copies both types of drivers whatever the settings to use HAL or LL for a given peripheral initialization.
Sara.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-07 7:11 AM
Hello @Pavel A.​ ,
The .mxproject is used by CubeMX to recognize the list of generated files or drivers used in the previous generation so that it can do the update after a new generation.
Deleting it won't affect the project.
Sara.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-07 5:36 PM
Hi @Sara BEN HADJ YAHYA​, Thanks for the update... great to have a work around.
Could I please suggest you also update the errata:
https://wiki.st.com/stm32mcu/wiki/STM32CubeIDE:STM32CubeIDE_errata_1.10.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-08 12:12 AM
Hello @Community member​ ,
We are currently working on a patch release for CubeMX and CubeIDE in which this issue will be fixed. I will let you know once it's done.
Sara.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-07-08 8:02 AM
Hello,
This issue is fixed.
STM32CubeMX v6.6.1 and STM32CubeIDE v1.10.1 are now available under st.com
Sara.
