2023-02-16 12:21 AM
I am trying to set-up the demo-kit for Acoustic Echo Cancelling and I am a bit confused about steps 1 and 2 of Getting started with the STM32Cube function pack for acoustic echo cancellation - User manual in part 2.3.1.
On my boards bridges that should be soldered are not but also bridges that should not be soldered are. What does "Configure" means, should I solder every bridge indicated ? And unsolder also the ones that should not be ? Why are resistors highlighted in orange ?
Solved! Go to Solution.
2023-05-11 07:27 AM
Hi,
The support helped me on solving the issues.
There were 3:
1- A short circuit caused by J18-19.
2 - There is a bug in the release v1.2.0 leading to a loud buzzing sound in the loudspeaker.
It is solved with using version v1.1.0.
3 - I had an issue when trying to record as both recorded channels were the same.
This was due to PC audio settings/drivers. To avoid this go to: Sound Control Panel > Recording > STM32MIC + LOUDSPEAKERS > Properties > Advanced > Uncheck "Enable Audio Enhancement."
2023-02-21 09:40 PM
This forum thread was marked by the moderator as needing a little more investigation, so a Support case was created in your name and will be handled off-line. Should anyone have any similar questions, please feel free to open a Support case directly at your myST portal - https://community.st.com/s/onlinesupport
2023-05-11 07:27 AM
Hi,
The support helped me on solving the issues.
There were 3:
1- A short circuit caused by J18-19.
2 - There is a bug in the release v1.2.0 leading to a loud buzzing sound in the loudspeaker.
It is solved with using version v1.1.0.
3 - I had an issue when trying to record as both recorded channels were the same.
This was due to PC audio settings/drivers. To avoid this go to: Sound Control Panel > Recording > STM32MIC + LOUDSPEAKERS > Properties > Advanced > Uncheck "Enable Audio Enhancement."
2023-08-14 09:55 AM - edited 2023-08-14 12:46 PM
Hello,
I'm having the same confusion regarding the configuration of the kits and the nucleo board for Multi-Mic Input (BF, SL, AEC). Its confusing because the diagram has items unsoldered, some soldered and they don't match what's actually on the board. I doubt items should be de-populated... But am still unsure about what exactly should be populated in this case, as it varies significantly.
I'm following the documentation found here: https://www.st.com/resource/en/data_brief/fp-aud-smartmic1.pdf
X-NUCLEO-CCA01M1
Pad | Board Status | Documentation Status | What to do? |
J1 | O | ||
J17 | O | ||
J3 | O | X | |
J14 | X | ||
J21 | O | X | |
J22 | O | ||
J20 | O | ||
J25 | O | X | |
J23 | O | ||
J18 | O | X | |
J10 | X | X | |
J9 | X | X | |
J12 | O | ||
J6 | X | ||
J15 | O | ||
J2 | O | X | |
J11 | O | ||
J13 | X | ||
J8 | X | ||
J5 | X | ||
J24 | O | ||
J4 | X | ||
J16 | O | X |
X-NUCLEO-CCA02M2
"Solder the external headers to M1_EXT_B and M4_EXT_B". Umm, what external headers, and in what fashion? This is the most undescriptive instruction, because there were no "headers" included with my kit. It was only the board in the plastic package. Are there supposed to be, and otherwise what is the procedure to the use 4 mics in the slots that have headers already?
Pad | Board Status | Documentation Status | What to do? |
SB18 | O | ||
SB19 | O | ||
SB9 | X | ||
R1 | X | X | |
R2 | X | X | |
R3 | O | ||
R4 | X | X | |
SB8 | O | X | |
SB2 | X | X | |
SB1 | X | X | |
SB24 | O | ||
SB10 | O | X | |
SB17 | O | ||
SB11 | X | X | |
SB16 | O | ||
SB15 | X | X | |
SB13 | X | X | |
SB7 | X | X | |
SB26 | O | ||
SB21 | O | ||
SB25 | O | ||
SB20 | O | ||
SB14 | O | ||
SB12 | O | ||
SB22 | O | ||
SB23 | O |
I'm also experiencing an issue where after flashing the board with the following: FP-AUD-SMARTMIC1 - STM32Cube function pack for MEMS microphone acquisition, advanced audio processing and audio output - STMicroelectronics it doesn't appear as a "Sound Output" device in windows, only sound input. But I suspect this may be to the board pinout misconfiguration. One problem at a time.
Can anyone from ST populate the above table on what to do?
@MMarn.1 I tried to open a ticket for clarification but received an error - "Looks like you don’t have access to create a case. Ask your community manager for access"