• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Subscribers 24 subscribers
  • Views 3512 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can’t compile KEIL MDK with STM32CubeMX middleware USB components due to missing header file (usbd_def.h)

Development WISAP

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 ?

  • What is the reason for the second (new) generated project ? Is it connected to the stand alone concept from STM ?
  • Due to the original KEIL project contains all the developed code I’d like to continue with this project. Is there any reason against this ?
  • Do I need a special configuration settings to make sure that I receive everything from CubeMX?

 

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

Parents
  • 0

    There are two different USBD stack options if you are using those tools (unless I'm very much mistaken). There is the Keil Middleware and there is the (free) STM stack. Perhaps you are caught in a mix of the two?

    Personally, after evaluating several stacks, I went with libusb_stm32 from Dmitry on github. I felt it was lean enough yet complete enough to get my objectives done. There are many other 3rd party stacks as well, such as no-longer-tiny TinyUSB.

Reply
  • 0

    There are two different USBD stack options if you are using those tools (unless I'm very much mistaken). There is the Keil Middleware and there is the (free) STM stack. Perhaps you are caught in a mix of the two?

    Personally, after evaluating several stacks, I went with libusb_stm32 from Dmitry on github. I felt it was lean enough yet complete enough to get my objectives done. There are many other 3rd party stacks as well, such as no-longer-tiny TinyUSB.

Children
  • 0 in reply to Grant B

    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

    Norbert