I am trying to set up a Raspberry Pi Zero 2 W with the ReSpeaker mic2 HAT. Unfortunately it hasn’t been smooth sailing. As many, I imagine, I am following this guide to install everything. However when I try arecord -L or arecord -l the ReSpeaker 2Mic HAT is not shown.
I have tried multiple Pi OS (OS Legacy 64x Lite, OS Legacy 32x Lite, OS 64x Lite) and keep getting the same issues.cat /proc/asound/cards doesn’t show the ReSpeaker. If I am correct the driver has been installed correctly when these modules are loaded:
snd_soc_core
snd_soc_wm8960
snd_soc_seeed_voicecard
And they are when I run lsmod | grep snd_soc. So I checked if the card is even detected and thats where I am at now and where I am getting stuck. I am starting to think something is wrong with the hardware itself. To check this I have done the following:
Run dmesg | grep -i wm8960 to check if the chip is detected and I got the following messages:
probe with driver wm8960 failed with error -5
Failed to issue reset"
When I run sudo i2cdetect -y 1 I get the following:
Unfortanatly I don’t have a spare Respeaker or Pi lying around for now and trying to postpone buying and extra for now if I can help it .
I hope someone can help me with this or understand what is happening/confirm things for me. Thank you all in advance.
Greetings Bintley
EDIT: After banging my head on this for a day and posting here I just found out I have the ReSpeaker 2-Mics Pi HAT V2.0 which uses TLV320AIC3104. I am retrying and will update this post if it’s working or if I hit any issues.
So, Can you describe your development environment, or say what setup you have tried. What steps have you taken?
I used the copy text and (right-click) to translate your question. No Habla espanol
Be sure to un-install FIRST… reboot in between.
use the 32-bit version unless you have extra hair to pull out getting the 64-bit going (or expertise).
HTH
GL PJ
FYI, you need a few reply’s to get enough forum credz to posts, links, pics and new topics. jump in the water is fine
I have used a Raspberry Pi Zero 2 W, I have tried the drivers that have been posted on this page and those for Wyoming Satellite from Rhasspy, I have tried with the 64-bit version only but the speaker still does not appear, I have the Pi Hat 2 Mic v2 speaker.
thanks
Awesome, no spoon required then
after another reply or so , feel free to start a new thread. Take a run at it with the 32-bit option first. Report back.
Others will chime in, that way also.
HTH
GL PJ
You’ll get it… seems to take a few try’s from the looks of the number of times this pops up.
I am working on a ready to use image here: GitHub - florian-asche/PiCompose at feature/initial-base. I am like almost ready. Need to test the new version, when the build is done. Need to test if i still need to add the pipewire config or not. Anything else should work when the build is done.
Yes, it takes a couple more reply’s to build enough forum cred
replay again should put you over the limit , and welcome to level 1
I knew others were testing it so that is Awesome.
A great project that will be very useful to all users. Count on me to try it out and give you my feedback. Thank you very much. , So if I understand your image correctly, I can do my project with my speaker v2 board?
Please can anyone provide working files for raspberry Pi Zero and Respeaker 2mic V2? I already tried everything and ive been working for days and cant complete the task. HUGE PLEASE.
Hi Kian, thank you for the reply – I’ve already tried everything in the official wiki you linked, multiple times.
I followed all steps (dtoverlay, seeed-voicecard install, different kernels, manual module loading, etc.), but arecord -l still shows no capture devices on Raspberry Pi Zero 2 W.
I also tried:
older 32-bit Raspberry Pi OS with kernel 6.1.21-v7+
building seeed-voicecard from GitHub (HinTak fork)
loading snd_soc_tlv320aic3x manually and checking modules
Unfortunately, nothing has worked. Could you please provide a confirmed working image or config for Raspberry Pi Zero 2 W with ReSpeaker 2-Mic HAT v2? Or connect me with someone who has it working?
Hi, I tried using the image from the feature/initial-base branch as instructed.
Unfortunately, the compose/ folder is not recognized or mounted correctly after boot – Docker doesn’t see any projects and nothing runs automatically.
I created compose/respeaker-test/docker-compose.yml directly on the boot partition (while the SD card was mounted in a PC), but after booting the Raspberry Pi, the folder /compose doesn’t exist at all inside the system.
Additionally, audio recording doesn’t work either – arecord -l returns no devices, even though ReSpeaker 2-Mic Pi HAT is properly connected. PipeWire is running, but no audio input nodes are detected via pw-cli ls Node.
It seems like the audio overlay for ReSpeaker hasn’t been applied or the I²S driver is not active.
Could you please clarify:
How exactly should the compose/ folder be structured and recognized by the system?
Is there a working example of a docker-compose project that confirms ReSpeaker functionality?
Was the 2-Mic HAT tested successfully with this image?
Thanks a lot – the idea behind PiCompose is great, but currently I can’t get any Docker project or audio functionality working with it.
initial-base is the correct one. I will add the docker files for homeassistant shortly.
arecord -l should return something. The system needs one or two reboots at start for the installation. It needs internet access and give it like 15min after each reboot. Will test the image with that board tomorrow.
I am currently working on the new board. And that is fully working now.
First of all, I really appreciate all your work and effort on this – seriously, hats off!
I actually gave up earlier today after frying my brain (and maybe some SD cards), but reading your update gave me new hope.
With that in mind, I’ll gladly try to be a useful tester and help push this to the finish line – not just for the joy of getting it working, but also because my own project based on this has real potential for monetization. If it takes off, I promise nobody involved will be poorer for it.
I’ll give it another shot on Monday, and if your test run with that board works, would you consider sharing a more detailed step-by-step guide for your current path? I keep wondering if I messed something up along the way – having clear documentation would give me more confidence and help me use the whole setup more effectively, especially since I’m not that close to the codebase.
And of course – if there’s anything you’d like me to test, debug, or break in a controlled fashion, just say the word!
.
PJ 
