2024-11-18 08:06 AM - edited 2024-11-18 11:29 PM
The structure of the stm32 usb device library feels very complex, is there any tutorial to clarify the structure?
I want to implement a UVC.
This is a picture I found on a wiki, but I can't make sense of it.
For example, the file stm32xxx_ll_usb has no LL for the API name, but the USB core has LL for the API name, which is very confusing, and PCD HAL driver The name doesn't tell you what it does.
If the following structure is better applied
2024-11-18 08:14 AM
2024-11-18 08:16 AM
2024-11-18 08:27 AM
My impression is that STM USB stack with tangled pointers and bidirectional function calls between logical levels is much more complex than USB. ;)
2024-11-18 09:02 AM
2024-11-19 10:49 AM - edited 2024-11-19 10:49 AM
Hi @Shiina
Capturing USB traffic is an excellent recommendation! Correlate the captured USB traffic with your code to understand how specific operations in your code translate to USB packets.
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.