2020-09-01 09:14 AM
There appears to be a bug in STM32CubeMX where some settings are not loaded when reopening the app and project, even though they were previously successfully written to the .ioc file. Default settings are always used instead, and then re-saving the project (without making any changes yourself) will write these undesired settings back to the .ioc file. These settings are:
Steps to reproduce:
ln -s ~/STM32Cube/Repository ~/projects/demo/cube_repo
-ProjectManager.CustomerFirmwarePackage=../../cube_repo/STM32Cube_FW_F4_V1.25.0
+ProjectManager.CustomerFirmwarePackage=../../../../STM32Cube/Repository
-ProjectManager.LibraryCopy=2
+ProjectManager.LibraryCopy=1
System info:
Solved! Go to Solution.
2020-09-14 06:02 AM
Hello @Miles ,
Thanks for bringing this to our attention, Issues confirmed an they will be fixed.
Best Regards,
Khouloud
2020-09-03 06:19 PM
This is also an issue when running STM32CubeMX in command line mode.
For example with this script (saved as mxcmd.txt):
config load /home/miles/projects/demo/cube_workspace/test1/test1.ioc
project generate
exit
And executed with:
/home/miles/STM32CubeMX/STM32CubeMX -q $(readlink -f mxcmd.txt)
It overwrites the .ioc file with the same changes as described in the previous message, and then generates project output with these undesired settings.
Two other annoyances with the CLI interface:
2020-09-14 06:02 AM
Hello @Miles ,
Thanks for bringing this to our attention, Issues confirmed an they will be fixed.
Best Regards,
Khouloud