Trouble with AWE_BSP_stm32l496_s1.4-Demo-Project on STM32L469D-DISCO-Board

9 posts / 0 new
Last post
TT
Offline
Last seen: 2 months 3 weeks ago
Joined: 05/09/2019 - 4:50am
Trouble with AWE_BSP_stm32l496_s1.4-Demo-Project on STM32L469D-DISCO-Board

Hi,

the Example on Disco-Board doesn't run.

Equipment/Docs:
-Audio_Weaver_Designer_7.A.0.8_STMicro.exe
-AWE_BSP_stm32l496_s1.4_Installer.exe
-STM32L469D-DISCO-Board
-ST-LINK-Utility V4.4.0.0.
-Audio Weaver STM32L496 Discovery Board Users Guide.pdf

I've flashed the "STM32L496_Discovery_SW4STM32.bin"-Binary using ST-LINK-Utility.
The Audio/HID-Devices appears in the Device-Manager.
The AW-Server says "can't connect"

I have compiled the Example with GCC.
The App hangs while Initializing (in AWMain.c "awe_fwInit(&g_AWEInstance);")
The Main-Loop will never reached!

What's wrong?
Is there a Version-Conflict.
The Binary should run out-of-the-Box.

a little frustrated...

Kind Regards

Thomas

 

 

Axel Nilsson
Offline
Last seen: 21 hours 31 min ago
Joined: 12/19/2016 - 2:02pm

Hi Thomas,

 

This problem is often caused by USB cables that supply only power, not data & power. Please try with other USB cables that you know can transfer data & power. 

 

Have you also tried flashing the other .bin files (EWARM and MDK-ARM)? If those work for you but the SW4STM32 .bin does not, then please let us know.

 

Thank you

-Axel

TT
Offline
Last seen: 2 months 3 weeks ago
Joined: 05/09/2019 - 4:50am

Hi Axel,

thanks for your advice.
USB-Cables are not the problem here.
As I wrote: The Audio/HID-Devices appears in the Device-Manager.
awe_fwInit() hangs...

The Issue:
The Disco-Board comes with a (fancy) preloaded App.
You !!! MUST !!! delete the external (QSPI)-Flash.
(with ST-LinkUtility)
Otherwise the AWE-Core crashes.

After that you can flash the bin-File (EWARM/MDK_ARM/SW4ST32 doesn't matter)

When I play audio the Sound is horrible. (pops and clicks)
The Mems-Mics doesn't work at all.
Is MEMS-Mic-Audio-In implemented?

I run "AudioCheck.awd", the CPU-Load is approx. 24%.
Is the STM32L4 to small for AW?

Other obscure behavior:
AW does not start when installed in "c:\Program Files\DSP Concepts\" for example
(splashscreen appears and thats all..)

Seems to be a long way to get familiar with AudioWeaver.

Kind Regards
Thomas

 

 

 

Chris Perry
Offline
Last seen: 21 hours 21 min ago
Joined: 07/16/2017 - 9:45am

After flashing the firmware image please unplug both USB cables and then plug them back in again.

When I flash the board using ST-Link, if I do not power cycle the board, I hear static in the audio output.

To test, I power-cycled the board by unplugging then replugging both USB cables.

I connected to this target using AWE_Server.
I then created a pass-through AWD in Designer by wiring the unconnected output pins of the deinterleave module to the input pins of the interleave module. I then hit the build and run button in Designer.
Next I checked the Windows volume control to make sure it was using "AWE Audio Class" device>

Finally I played an audio file using Windows MediaPlayer.

Jie
Offline
Last seen: 2 weeks 3 days ago
Joined: 08/20/2019 - 4:33am

Hi Chris,

I made it successful on STM32F407G-DISC1 board, where windows volume control showed "AWE Audio Class" and I can play audio thru F407G-DISC.

However, I met the same problem Thomas encountered on STM32L496G-DISCO board, Audio Weaver Server recognize the target but it just can't connect.

 

Axel Nilsson
Offline
Last seen: 21 hours 31 min ago
Joined: 12/19/2016 - 2:02pm

Hi,

 

Did you try erasing the external QSPI-Flash using ST-Link before flashing the .bin files included in the BSP?

 

Thanks

-Axel

Jie
Offline
Last seen: 2 weeks 3 days ago
Joined: 08/20/2019 - 4:33am

Hi Axel,

Yes, I did erase the flash with ST-Link utility. I am thinking would it be needed to modify the .ini file to adjust clock and else?

regards

Jacky

Axel Nilsson
Offline
Last seen: 21 hours 31 min ago
Joined: 12/19/2016 - 2:02pm

Hi Jie,

 

Just to make sure, it was the external flash that you erased using the 'Sector Erase' option as seen below (you have to add the appropriate target config with 'Add External Loader' first):

If you did erase this external flash properly, then the problem is likely with one of your 2 micro USB cables. You mentioned you were able to connect to the STM32F407 so at least the micro USB cable you used for that target is good. Please confirm that both of the micro USB cables you are using for the STM32L496 can be used to successfully connect to the STM32F407.

 

Thanks

-Axel

Jie
Offline
Last seen: 2 weeks 3 days ago
Joined: 08/20/2019 - 4:33am

Hi Axel,

It works with your approach. Thank you very much for your support.