Dear readers,
I’m developing a SW project with KEIL MDK Plus (V5.25) and the STM32CubeMX (V6.5) tool. The target processor is the STM32F303VCTx and everything goes well until I added a USB device to the project.
Before I describe the issue I’d like to ask some basic questions for a better comprehension:
When I generate the code with CubeMX a new KEIL project is generated in the path
…\RTE\Device\STM32F303VCTx\STCubeGenerated\MDK-ARM
and the original KEIL project is going to be updated by CubeMX. May I understand the two KEIL projects as a generated output which shares some common resources ?
The problem appears when I added a USB device and the Middleware class USB_DEVICE with HID. After generating code and compiling the project I received the following message:
./RTE/Device/STM32F303VCTx/STCubeGenerated/Inc\usb_device.h(33): error: 'usbd_def.h' file not found
In principle, it’s possible to fix this by adding manually some groups from the generated cubeMX code and with some include path from my local STM32Cube repository but I’m not sure whether this is the right way?
I guess I have to add the USB port to the run time environment. Is this correct:
CubeMX looks like this:
and the KEIL project folder looks like this:
Any suggesting how to solve the missing groups, paths and entries in the KEIL project ?
Thanks in advance.
Best regards
Norbert
Hello Grant,
The two USBD options are a little confusing because sometimes I have to add the component in the Keil Runtime environment and sometimes it is enough to add it in STM32CubeMX only. Previously I tested both options without success. On the other hand when I want to use STM32CubeMX and I activate "Connectivity" with USB and "Middleware" with USB_Device I would expect that the existing folder are connected to my working project but no groups are added.
This is one of my starting questions: When I use STM32CubeMX and generate the code I'll find two projects (*.uvprojx), my working project and a new generated (STCubeGenerated.uvprojx) which contains the folder for the usb device. Should I merge these project or what is the typical way to manage this ?
When I merge both project and add some include paths it is possible to fix this issue and the project is compilable. Is this the intended way to do this ? (I'm not sure because when changing anything in CubeMX this could cause further manual actions)
Thanks in advance