I found a problem today when I created a new project,and tried to manage software packages byManage Run-Time Environment. I choose "Configuration via STM32CubeMX".(like the Screen Shot blow) ww3.sinaimg.cn/.../6cda5b3djw1f0wv0gwltvj20rr0lg3zf.jpg
After generate code by STM32CubeMX 4.13.0. When I returned to keil but it told me that
Error #545: Required gpdsc file '.....Project\RTE\Device\STM32F407VETx\FrameworkCubeMX.gpdsc' is missing
After I searched the update log of CubeMX, I found there words: New features: ..... In the project settings, the user can choose to generate a CMSIS-Pack description file (gpdsc) to integrate with other IDEs.
So,STM32CubeMX 4.13.0,will not generate a gpdsc file as earlier version , unless you change your Toolchain/IDE to"Other Toolchains(gpdsc)". ww4.sinaimg.cn/.../6cda5b3djw1f0wv0gbsn0j20go0hi3z0.jpg
That's inconvenient for developers.Will the next Update will fix that problem?
There is a possible solution,I did not try (because I don't want to write a new STM32CubeMxLauncher)but it should works:
Keil used a Program (X:\Keil_V5\ARM\Pack\Keil\STM32F4xx_DFP\2.7.0\MDK\CubeMX\STM32CubeMxLauncher.exe) to generate a script for CubeMX to know the information about the Project. the script is like
load STM32F407VETx project name STCubeGenerated project toolchain "MDK-ARM V5" project path X:\Workspace\....
So change the 3rd line of script to project toolchain "Other Toolchains (GPDSC)" to generate a GPDSC file, and import it to target project.
where
Updated to STM32CubeMX Version 4.16.0 today and this problem is still there plain as day. Trying to use STM32CubeMX and Keil MDK together continues to be a waste of time. The combination of STM32CubeMX and Keil MDK has only a fraction of the usefulness either product has when used alone.
I should be more specific. What happens is that cubemx tool only uses the first word of the directory filename and places the generated files in the wrong directory. So the sources are not in the project directory and MDK shows the source files like main.c to be missing.
Hi,
I was playing around with v4.15 of the cubemx and v5.20 of the MDK. I noticed that if my project directory had spaces in it that I would see the errors described above. If the project directory had no spaces it works perfectly.
Can anyone confirm this?
Thanks, Bob
@Matthias Hertel thanks very much,my problem solved....
You are reading templates from the "Default" location.
Browse to your Pack directory e.g. C:\Keil\ARM\Pack\Keil\STM32F4xx_DFP\2.0.0\MDK\CubeMX
why i had not any template for cubemx???
why when i want to add template in stmcubemx it has not any template??? please see image:: www.mediafire.com/.../z73to517o5r9k79zg.jpg i don't have any template?
I don't think the issue will be solved any time soon. The problem was reported and acknowledged as a bug more than 1 year ago! That's unacceptable.
see also: http://www.keil.com/support/docs/3823.htm
It has been confirmed that this issue still exists in v4.14 release version, which is caused by a bug in STM32CubeMX 4.14.
There is a workaround solution:
Before running the code generation!!! Select from "Project" menu: "Settings..." (alt-p) Switch to tab "Code Generator" At the bottom of the dialog there is "Template Settings" where you need to press the "Settings..." button Hit "OK" to close all dialogs. Now generate the Code and both GPDSC and MX_Device.h file should get generated.
ST will fix this bug in the next release.
when stm32CubeMX (4.14)is called from keil uVision5 it gets the project name "STCubeGenerated", not the actual project name. After generating code either a new project (open project) is started with the name STCubeGenerated or the data file is not recognised cos its got the wrong name. Under stm32CubeMX settings the project name "STCubeGenerated" is greyed out so cant be changed.
MCU REF STM32F405RGTx
fw pac name STM32Cube FW_F4 V1.11.0
STCubeGenerated.ioc
I cant see any *.gpdsc file
I also found that there is a same problem in 4.14.0. As the keil call the CubeMx, from the CubeMx project setting you can find the Project name is not correct.
Hello Zhang, I tested 4.14 and it does generate a gpdsc as expected. Can you check again that you installed 4.14 properly?
Best Regards, Matthias
The new version 4.14.0 reproduce this problem again. I doubt ST is not happy to let Keil use their tool :(.
View all questions in Keil forum