ThreadX USBX Audio Class example
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-05-22 7:29 AM
I was reading this conversation and found the comment about an example showing support of Audio Class with USBX and ThreadX
For some reason, the example is disappeared
Is there a reason on why it has been deleted? Is there a way to get it?
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-05-22 7:37 AM
Hi @nico23
List of unavailable projects :./Projects/STM32H743I-EVAL/Applications/USBX/Ux_Device_Audio2.0_PlayBack
You can find it directly from ST.com.
The audio middleware stacks, such as STM32_Audio, STemWin, and TouchGFX, are not included on GitHub because they are subject to a restrictive license known as the ST Ultimate Liberty license. Before users can access these middleware stacks, they must agree to the terms of the associated license. Since this licensing process could not be implemented on GitHub, the solution adopted was to remove these middleware stacks from the package published on GitHub and keep them on st.com.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-05-22 7:36 AM
maybe this helping ...
So look at https://www.st.com/en/embedded-software/x-cube-azrtos-h7.html#get-software
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-05-22 7:37 AM
Hi @nico23
List of unavailable projects :./Projects/STM32H743I-EVAL/Applications/USBX/Ux_Device_Audio2.0_PlayBack
You can find it directly from ST.com.
The audio middleware stacks, such as STM32_Audio, STemWin, and TouchGFX, are not included on GitHub because they are subject to a restrictive license known as the ST Ultimate Liberty license. Before users can access these middleware stacks, they must agree to the terms of the associated license. Since this licensing process could not be implemented on GitHub, the solution adopted was to remove these middleware stacks from the package published on GitHub and keep them on st.com.
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.
