‎2020-04-07 02:06 AM
I'm trying to generate the code on the STM32F407G-DISC1 evaluation board for the TrueStudio project environment.
The code generation just freezes.
Has anyone else seen this?
I'm running on Windows 7 Pro, 64 bit
I've tried different combinations of projects and processors but the result is the same.
Solved! Go to Solution.
‎2020-04-07 02:27 PM
Hello @SidBr​ ,
Please check if your project path location contains special character as "#" or "&".
Then, please keep us informed about your progress.
Best Regards,
Imen
‎2020-04-07 02:27 PM
Hello @SidBr​ ,
Please check if your project path location contains special character as "#" or "&".
Then, please keep us informed about your progress.
Best Regards,
Imen
‎2020-04-08 07:52 AM
Thanks @Imen DAHMEN​
This was the problem.
Since I started working from home, the IT department gave me a laptop where the User account was “R&D�?, which appeared in the STM32CubeMX repository path.
I created a new admin user not containing an '&', and it now works.
This has solved most of my other issues.
‎2020-04-08 08:04 AM
I already reported highlighted this issue internally to CubeMx team for analysis.
Best Regards,
Imen
‎2020-04-09 06:20 AM
Hello, I have the same thing when I had upgrade the system windows 10 (1093 -> 1909). And it's the same even when I try to generate for stm32cubeide
‎2020-04-09 06:36 AM
Hi @sschu.236​ ,
Have you managed to fix it?
Take a look in the 'Project Manager' options and check to see what the path of the 'Repository' is.
'&' and '#' breaks the code generation.
‎2020-04-09 07:05 AM
Hello, I looked the path, i don't have any special caracters. My path is like that:
‎2020-04-09 08:16 AM
Hello, I resolved the issue. My work folder contained effectively a special character. I changed the work folder's name and all is OK. Thank you for your suggestion. :ok_hand:
‎2021-01-11 06:52 AM
I see this frequently, randomly, roughly 2 out of 10 times, on several projects. The associated paths have no special characters other than a space. My solution is to kill the process with the Windows process manager and try again. The odds are in my favor!