Getting Started with Raspberry Pi | Seeed Studio Wiki

[giscus[bot]]

Getting Started with Raspberry Pi | Seeed Studio Wiki

Getting Started with Raspberry Pi

https://wiki.seeedstudio.com/ReSpeaker_2_Mics_Pi_HAT_Raspberry/

[sirArrhichion]

Hello! I am trying to install the drivers for ReSpeaker 2-Mics Pi HAT on a raspberry.
I tried to follow this guide but I had this issue:
"grep: /boot/kernel.img: No such file or directory"
Then I followed this:
https://forum.seeedstudio.com/t/installing-respeaker-2-mic-hat-not-working-unable-to-locate-package-and-kernel-version-issues/269986
and I installed the drivers successfully using this repo: https://github.com/HinTak/seeed-voicecard
The command "arecord -l" though gives me no results.
Am I missing something?

[y-lobau]

Does anyone know how does it work with picovoice? Is there an API to customize picovoice? Is it free to use forever or the same pricing requirements and limits apply (https://picovoice.ai/pricing/)?

[allphasepi]

My Raspberryt[pi Zero refuses to shutdown when I run the script from boot. If I run it from shell and stop the programme my pi shuts down but with the script runnung it just hangs after shutdown and doesn't complete a full shutdown. The green light stays on, I can't access my pi so end up having to power it off to complete shutdown. I've triedadding pygame.mixer.quit(), pygame.quit(), sys.exit() to the end of the script but something is stopping safe shutdown'

[feiticeir0]

Why don't you connect a monitor to it and see what's going on in real time ? Maybe you can spot what's happening.

[allphasepi]

I have pretty sure background pygame.mixer is keeping it from shutting down I'm running a flask app I'm going to try an Apache flask app to see if that will help if not rewrite it as a node js script and see if that changes things. Just checking it's not a common problem. Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Bruno Santos ***@***.***> Sent: Wednesday, July 17, 2024 8:58:41 AM To: Seeed-Studio/wiki-documents ***@***.***> Cc: Phil Marshall ***@***.***>; Comment ***@***.***> Subject: Re: [Seeed-Studio/wiki-documents] Getting Started with Raspberry Pi | Seeed Studio Wiki (Discussion #912) Why don't you connect a monitor to it and see what's going on in real time ? Maybe you can spot what's happening. — Reply to this email directly, view it on GitHub<#912 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEVEUUH3ZDL7AI5UA2COIRDZMYP3DAVCNFSM6AAAAABBZNNJGGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBXGA2DOMI>. You are receiving this because you commented.Message ID: ***@***.***>

[allphasepi]

I put it into a monitor and it seems also lib pcm.c 8545: sound_PC_Recover2 underfunded occurred seems to be the problem hanging my pi zero w and XDG_RUNTIME_DIR not set in environment. I've Googled it and it's a bit of a mini field. Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Phil Marshall ***@***.***> Sent: Wednesday, July 17, 2024 9:46:48 AM To: Seeed-Studio/wiki-documents ***@***.***>; Seeed-Studio/wiki-documents ***@***.***> Cc: Comment ***@***.***> Subject: Re: [Seeed-Studio/wiki-documents] Getting Started with Raspberry Pi | Seeed Studio Wiki (Discussion #912) I have pretty sure background pygame.mixer is keeping it from shutting down I'm running a flask app I'm going to try an Apache flask app to see if that will help if not rewrite it as a node js script and see if that changes things. Just checking it's not a common problem. Sent from Outlook for Android<https://aka.ms/AAb9ysg>

________________________________ From: Bruno Santos ***@***.***> Sent: Wednesday, July 17, 2024 8:58:41 AM To: Seeed-Studio/wiki-documents ***@***.***> Cc: Phil Marshall ***@***.***>; Comment ***@***.***> Subject: Re: [Seeed-Studio/wiki-documents] Getting Started with Raspberry Pi | Seeed Studio Wiki (Discussion #912) Why don't you connect a monitor to it and see what's going on in real time ? Maybe you can spot what's happening. — Reply to this email directly, view it on GitHub<#912 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEVEUUH3ZDL7AI5UA2COIRDZMYP3DAVCNFSM6AAAAABBZNNJGGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBXGA2DOMI>. You are receiving this because you commented.Message ID: ***@***.***>

[mlozo]

Hi everyone,

I'm having trouble getting audio recording to work with my ReSpeaker 2-Mics Pi HAT v2 on my Raspberry Pi Zero 2WH. I've followed the installation instructions step by step on a fresh Raspbian OS Lite installation (after running update & full-upgrade). Here’s what I did:

Step 1:
I connected the HAT to my Raspberry Pi Zero 2 WH and powered it with a 5V 5A supply (this powers both the HAT and the Pi).

Step 2:
I downloaded, compiled, and installed the DTS as per the instructions. I then added the following lines to my /boot/firmware/config.txt file:

dtoverlay=respeaker-2mic-v2_0-overlay
dtoverlay=i2s-mmap

After reboot, I checked the devices:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi [vc4-hdmi], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: seeed2micvoicec [seeed2micvoicec], device 0: 3f203000.i2s-tlv320aic3x-hifi tlv320aic3x-hifi-0 [3f203000.i2s-tlv320aic3x-hifi tlv320aic3x-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: seeed2micvoicec [seeed2micvoicec], device 0: 3f203000.i2s-tlv320aic3x-hifi tlv320aic3x-hifi-0 [3f203000.i2s-tlv320aic3x-hifi tlv320aic3x-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I also selected the seeed2micvoicec card in alsamixer and set all Capture levels to maximum (no channels are muted). SPI and I2C are enabled in raspi-config, and the test programs for the buttons and LEDs work perfectly.

The problem:
When I try to record audio (with the Device ID set to 1), I always get an empty file — even though the file length corresponds to the recording duration, it contains no audio (not even static).

I've tried recording via Python scripts as well as using the sound recorder tool, but the outcome remains the same.

Additional observations:

• Running dmesg | grep -i 'tlv320' gives me these messages:

  [   11.323631] tlv320aic3x 1-0018: supply IOVDD not found, using dummy regulator
  [   11.323803] tlv320aic3x 1-0018: supply DVDD not found, using dummy regulator
  [   11.323846] tlv320aic3x 1-0018: supply AVDD not found, using dummy regulator
  [   11.323893] tlv320aic3x 1-0018: supply DRVDD not found, using dummy regulator
  [   11.323934] tlv320aic3x 1-0018: Invalid supply voltage(s) AVDD: -22, DVDD: -22
  

• Running dtoverlay -l shows no overlays loaded, even though the config file seems correct.
• In the /boot/firmware/overlays directory, I found the respeaker-2mic-v2_0-overlay.dtbo file, but the i2s-mmap.dtbo file is missing.
• My OS details:

  $ cat /etc/os-release && uname -a
  
  PRETTY_NAME="Raspbian GNU/Linux 12 (bookworm)"
  NAME="Raspbian GNU/Linux"
  VERSION_ID="12"
  VERSION="12 (bookworm)"
  VERSION_CODENAME=bookworm
  ID=raspbian
  ID_LIKE=debian
  HOME_URL="http://www.raspbian.org/"
  SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
  BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
  Linux rpi 6.6.74+rpt-rpi-v7 #1 SMP Raspbian 1:6.6.74-1+rpt1 (2025-01-27) armv7l GNU/Linux
  

Has anyone encountered this issue before? Is the missing i2s-mmap.dtbo file the cause, or might there be something else I should check? Any suggestions or further diagnostic steps would be really appreciated — I just want to be able to record sound via Python!

Thanks in advance for your help!

[nfs0619]

We have received your message and are arranging debugging. We will analyze your issue as soon as possible and provide a solution. If you do not receive a follow-up response, you can also reach out to our technical support team at techsupport@seeed.io for updates. Thank you for your patience!

[nfs0619]

Sorry for the wait! We tested the setup and did not encounter any issues. Here are some successful test results for your reference:

The Additional observations you mentioned also seem normal. You can compare them with the following screenshots:

One possible reason for the issue could be that you are following the v1 version of the tutorial instead of the correct v2 version. Please ensure you are using the correct guide for ReSpeaker 2-Mics Pi HAT v2:
Official v2 Tutorial

We recommend following this tutorial and double-checking your setup. If the issue persists, feel free to reach out to our technical support team for further assistance:
techsupport@seeed.io

[mlozo]

thanks for the answer, I definitely follow the instructions from v2 (and I have v2 hardware)

for me the file is also created and there is no information about errors, but the file does not contain sound, there is silence on it... have you checked the content of the wav file?

[nfs0619]

Hello,

We tested the setup using a Raspberry Pi Zero 2W (the only difference between W and WH is the pre-soldered headers) and did not encounter any issues. The recorded file also contains sound.

Could you try following our tutorial step by step once again? If the issue still persists, I recommend reaching out to our technical support team at techsupport@seeed.io for further assistance.

[mlozo]

Thank you for your response. I've performed the entire process multiple times, starting from flashing a fresh system image (Raspberry Pi OS, both 64-bit and 32-bit, both Full and Lite versions), each time with the same outcome — the recorded file contains only silence.

I recorded the entire procedure, beginning from the first boot after flashing the new system image. Here is the video: https://youtu.be/qc2tAuFuh50?si=8zWwQjq5KSvXl-ri

I followed all steps outlined in the V2 instruction manual. At the end, I recorded an audio file and opened it in GoldWave; it clearly shows no sound whatsoever.

Do you have any other suggestions? In parallel, as you recommended, I will contact support via email. Thanks again!

[cer0484]

Hi,

I have a ReSpeaker 2-Mics Pi HAT v2 connected to a Raspberry Pi Zero WH, but when following the setup guide, no input or output appears when using aplay / arecord.

I tested the exact same setup on an RPi Zero 2 WH, and everything worked fine. So, I’m wondering—is the RPi Zero WH compatible with this board? I used Raspberry Pi OS from 19.11.2024 as well as newer versions, but without success.

I also tested the functionality of the button and LED on the board, and they are working. Does anyone have an idea why the audio inputs and outputs are not showing up?

Thanks for any advice!

[nfs0619]

Thank you for your feedback. We have received your message and are currently arranging for debugging. If you do not receive further updates, please feel free to reach out to our technical support at techsupport@seeed.io for further assistance. Thank you for your support and understanding.

[pstulzer]

Same issue here.

[nfs0619]

Hello, thank you for your patience. We’ve updated our Wiki with instructions to resolve this issue — please check it out here: https://wiki.seeedstudio.com/respeaker_2_mics_pi_hat_raspberry_v2/#2-setup-the-driver-on-raspberry-pi

If you have any questions during the setup, feel free to contact us at techsupport@seeed.io. We’ll be happy to assist you further.

[dhuskov]

Raspberry zero 2 w I get following error
On the step
sudo dtoverlay respeaker-2mic-v2_0-overlay.dtbo

• Failed to apply overlay '0_respeaker-2mic-v2_0-overlay' (kernel)c
  why?
  thanks for the help

[nfs0619]

Hi there! Please make sure to follow the instructions provided in our official documentation for compiling and setup:

• If you are using the V1 version, please refer to this guide:
  https://wiki.seeedstudio.com/ReSpeaker_2_Mics_Pi_HAT_Raspberry/
• If you are using the V2 version, please refer to this guide:
  https://wiki.seeedstudio.com/respeaker_2_mics_pi_hat_raspberry_v2/

Also, ensure that your Raspberry Pi is running the latest full version of Raspberry Pi OS, as this helps avoid compatibility issues with the kernel or drivers.

If you still encounter problems after following the documentation, we recommend reaching out to our technical support team at techsupport@seeed.io — they can provide faster and more detailed assistance.