Hi there,
I try to implement the "AWE BSP stm32l496 s1.4" (based on Discovery kit with STM32L496AG)
on my custom design.
As stated in "awe-core-integration-guide" there ar three communication channels
between Hardware an (Windows)-PC.
-Control Data, Audio Data and Tuning Data
Are these 3 interfaces tunneled through the USB-OTG-Port of the STM32L4?
I don't have (QSPI)-Flash on my board.
Is it mandatory?
last but not least:
In the Example-App the ST-Library "STM32CubeExpansion_Audio" is included.
Are AWE-Core and that Lib indepentend components?
Or they need each other?
Kind Regards
Thomas
12:07pm
Hi Thomas,
Our STM32L496 sample BSP supports stereo USB playback as an audio source.
It also uses the USB HID protocol to provide a tuning interface.
However, Control Data refers to the ability of the firmware to call an API to directly get or set an Audio Weaver module's parameters.
The flash file system is optional so no need for QSPI flash support if you don't need this feature.
You do not need the ST examples code but you do need the HAL-layer drivers. Our BSP example makes use of the ST middleware but you could implement your firmware without that if you wanted to fore go the convenience.