-
Notifications
You must be signed in to change notification settings - Fork 79
Description
Caution
The Issues are strictly limited for the reporting of problem encountered with the software provided in this project.
For any other problem related to the STM32 product, the performance, the hardware characteristics and boards, the tools the environment in general, please post your report to the ST Community in the STM32 MCUs dedicated page.
Describe the set-up
NUCLEO-U5A5ZJ-Q
STM32CubeMX v6.12.1
Describe the bug (skip if none)
Select USBX->UX Device HS->Device Class HS->VIDEO and generate code.
The generated file USBX/App/ux_device_descriptors.c (line 381) creates a device descriptor with bDeviceClass = 0, bDeviceSubClass = 0, and bDeviceProtocol = 0.
Please refer to section 3.2 Device Descriptor of "UVC v1.5 Class specification" available at https://www.usb.org/document-library/video-class-v15-document-set
Extracted from that document:
"...since the device uses an Interface Association
Descriptor in order to describe the Video Interface Collection, it must set the bDeviceClass,
bDeviceSubClass and bDeviceProtocol fields 0xEF, 0x02 and 0x01 respectively. This set of
class codes is defined as the Multi-interface Function Class codes."
Perhaps line 432 of the ux_device_descriptors.c file should also consider the presence of the IAD descriptor?
How to reproduce the bug (skip if none)
- Indicate the global behavior of your application project
- List the modules that you suspect to be the cause of the problem (Drivers, BSP, MW...)
- Describe the use case that generates the problem
- How we can reproduce the problem
Additional context
If you have a first analysis, an enhancement, a fix or a patch, thank you to share your proposal.
Screenshots
If applicable, add screenshots to help explain your problem.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status