2017-10-11 03:26 AM
Hi,
I am using package Stm32l4 1.9.0 package on Linux with Stm32CubeMX to generate workbench project.
It seems there is naming problem, since folder in downloaded repository is named
'STM32Cube_FW_L4_V1.9.0/Middlewares/Third_Party/FatFS'while it should be
'STM32Cube_FW_L4_V1.9.0/Middlewares/Third_Party/FatFs'This causes problem during build and code generation. Repository was updated using CubeMX.
Can somebody replicate this, or is something wrong with my configuration?I hope i am not duplicating this issue.
Best Regards, Miha
Solved! Go to Solution.
2017-10-11 05:01 AM
Hello
Mohor_i_.Miha
,I can confirm a problem with this package. Currently, please manually correct the mistake.
Best regards,
Tilen
2017-10-11 04:51 AM
Can somebody replicate this, or is something wrong with my configuration?
I leave that for ST, but it is quite probable they never ever tried with a case-sensitive file system.
2017-10-11 05:01 AM
Hello
Mohor_i_.Miha
,I can confirm a problem with this package. Currently, please manually correct the mistake.
Best regards,
Tilen
2017-10-11 05:07 AM
Hello, I can confirm this issue. I just logged in to post the same problem.
The 1.9.0 firmware contains the wrong capitilization 'FatFS'. Generation fails. Changing this manually to 'FatFs' seems to fix the issue.
Problem occurs in Linux, where case matters...
In STM32Cube_FW_L4_V1.8.0, the directory was correct with 'FatFs' and worked fine.
It would be helpful if the CubeMx debug output would spit out an error that helped the user find the problem. Took me a while to locate the root cause why FatFs wasnt being generated.
2017-10-13 04:41 AM
Hi,
I would like to inform you the folder '
Middlewares/Third_Party/FatFS' will be renamed '
Middlewares/Third_Party/FatFs' in the coming release of the STM32CubeL4 package (V1.10.0) which is expected to be available by the end of October.
Sorry for any inconvenience this created for you.
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.