cancel
Showing results for 
Search instead for 
Did you mean: 

ThreadX USBX Audio Class example

nico23
Senior II

I was reading this conversation and found the comment about an example showing support of Audio Class with USBX and ThreadX

https://community.st.com/t5/stm32-mcus-embedded-software/has-anyone-managed-to-get-a-usbx-audio-device-working-on-stm32/m-p/112225/highlight/true#M5290

For some reason, the example is disappeared

Is there a reason on why it has been deleted? Is there a way to get it?

1 ACCEPTED SOLUTION

Accepted Solutions
FBL
ST Employee

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.


View solution in original post

2 REPLIES 2
AScha.3
Super User

maybe this helping ...

AScha3_0-1747924534618.png

So look at https://www.st.com/en/embedded-software/x-cube-azrtos-h7.html#get-software

 

If you feel a post has answered your question, please click "Accept as Solution".
FBL
ST Employee

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.