Hi,
I want to implement the first project on an STM32M MCU. I have these questions:
1) Does the ST - Audio Weaver support all F4 and F7 family? (for example STM32F405)
2) I did not find any example of how to set the GPIOs for Audio inputs/Outputs on the Weaver Designer. The only example is with the discovery board.
Please guide me.
3:21pm
Hello,
Yes, the ST AWE Core libraries provided in the STM32F4/7 BSPs will work on any F4/F7 chip, so you should be able to use it on your custom hardware.
As for setting up GPIO for audio input/output, you will have to read the ST documentation to learn how to configure the hardware for your needs. Our reference BSPs for the STM32 Discovery Boards show how to get audio from multiple paths, including USB, internal microphones, and audio line-in, which should provide insight on how to best configure your audio path.
If you are asking how to set up different audio devices for Designer running in Native (Windows) mode, you can use the File->Preferences option in the Audio Weaver Server to select/deselect any audio devices plugged into your PC.
Hope this helps!
-Axel
6:52pm
Hi Axel,
Thank you.
Let me explain more deeply. an STM32 chip has several I/Os. when we build custom hardware, from where (in the Audio Weaver Designer) I can define that the input/output audio is connected to which GPIO pin?
The STM32 MCU has several peripherals, but none is designed directly for the Audio connection.
I want to use the hardware standalone. it means the hardware should naturally have one audio input and one audio output. Then I want to design the processing blocks using your software and upload it to the STM32.
is that possible?
8:49am
The audio routing on the chip is all done in the firmware. Audio Weaver is agnostic to where the audio comes from. It is up to the firmware Engineer to setup the hardware to deliver audio to Audio Weaver. We do not provide support for setting up any specific hardware platform but do provide sample BSPs for reference.
The bottom line is that Audio Weaver expects to receive frames of audio data from some buffer copying process setup by the firmware Engineer. How that data arrives into the buffer and what pins get set up to deliver that data is an exercise for the firmware Engineer.
Within Audio Weaver Designer itself, you can use routers and de/interleavers to split or combine different channels within your audio processing layout, but the ultimate source and destination of this audio must be defined by the the firmware.
I hope this clears things up for you,
-Axel