Hello,
I was wondering if Audio Weaver can utilize the onboard touch screen, or if it is possible to install additional drivers, etc. on top of your BSP in order to access the touch screen on the STM32F769. We want to design a GUI that will be able to control certain filter parameters that are going to be programed into the board using the Audio Weaver software. Any help on this would be greatly appreciated!
11:05am
Hello,
You will need to consult the ST documentation to make sure there is not a pin configuration conflict with any of the peripherals we are using, like the CODEC for example. But other than that, there shouldn't be any issue with getting input from the touch screen to control audio parameters. See the ControlDriver.c code in the ST BSPs for the recommended way to use GPIO to control parameters inside of your Audio Weaver layout.
This is a cool idea! Best of luck!
-Axel
8:27am
On the same topic, I am able to add LCD support and display on startup in main.c of the Audio Weaver Application before the AWEIdleLoop() Awe Idle loop.
During run time, the LCD has a display and Audio Weaver Server is able to connect to the target.
However, as soon as I 'RUN' the layout on AWE Designer, the Layout audio functionality works correctly but the LCD goes blank.
What could be causing this?
Also, are there any sample LCD interface available from Audio Weaver for this STM32F769 target?
Eric F.
9:50am
Please check the schematic for your ST board. There may be a conflict between the signals driving the LCD and the signals driving some other peripheral. DSP Concepts does not provide support for ST board firmware in general. We provide sample BSPs for select boards but expect the user to be responsible for any enhancements. to the firmware.
4:31pm
Hi,
As I stated the LCD operates properly even when AWEIdleLoop is running, and I can connect to the target with the server. So I really doubt it is a schematic issue.
The issue is that once I RUN the layout from AWE Designer on the PC, then the display goes blank.
What happens when I start the AWE layout? Is it more of a memory allocation problem?
Thanks,
Eric F.
5:06pm
When a design is loaded to a target from Designer the block diagram is turned into a list of text commands (the .AWS file) and these commands are turned into binary commands (the .AWB file) and then executed one by one on the target to create the signal processing layout and start it running. The first command issued is "destroy" which stops any currently running layout and then zeros the "fast", "fastb", and "slow" heaps. The rest of the commands create wires and modules connects them together and starts the layout running.
7:32am
Hi,
I want to control the modules of Design, through STM32F769 board. I assign the Object ID to the modules also.
I have followed the Control Interface Step.
I am using the user push button to control the design module.
It was not working.
Can you suggest different method to control with the STM32 board?
Can you figure out my issue?
Also I want to interface the audio weaver design with STM32F769i board touchscreen.
1:12pm
Hi Vaibhav,
I have contacted you via e-mail to get more details about what you have done.
Thanks!