Hi,
When can we expect a working driver for the current Raspberry OS?
“sudo arecord -L” does not show the device!
3 months later and no progress of seeed on that 
Hello you dear girls and boys from Seeed,
why don’t you care about your customers?
Hello Fellow ReSpeaker buyers!
So it does seem to be a bit hard to figure this one out since there doesn’t seem to be much on here re: code, etc., I figured I’d offer what I’ve deduced.
First - you won’t see this as a microphone or any kind of sound device because the Pi doesn’t know what it is - to start, it’s just an address on the I2C bus.
Here’s some telling info. Note the last command: i2cdetect (you may need to download i2ctools from GitHub or Adafruit). Note also that (for me) nothing new or different shows up for arecord or lsusb:
pi@LanguageCORE:~ $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 2: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 3: Device_1 [USB PnP Sound Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
pi@LanguageCORE:~ $ lsusb
Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Ultra Fit
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller
Bus 001 Device 003: ID 1b3f:2008 Generalplus Technology Inc.
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@LanguageCORE:~ $ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- 3b -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
pi@LanguageCORE:~ $
So for my unit, I now have an I2C address of 3b. Obviously I have enabled I2C in my Raspberry Pi’s options - so if you haven’t that would be step 1.
Once you have the unit plugged in and visible on your I2C detection tool, you can start writing some code to address the thing and see what we can do with it. Unfortunately - that’s where I am at right now. If I find anything useful - I’ll come back here & post it. If any of you have found anything useful - please share. Not sure why there seems to be either no - or more difficult to find - documentation, like a starter test script that shows how to use the functions - I’m sure there is, somewhere…
Dave
Hi,
is there any solution, how to fix this problem? I am not able to use the 4mic array on buster!
The only solution at the moment is the driver install with downgrading the kernel on Debian Buster to 2018.
The Seeeds don’t care about their customers. Throw that sh… away!
Someone has forked the drivers and they work with the latest Rhaspbian. Look in the github issues for HinTak.
@seeds: In your Wiki you suggest to use the Raspberry Pi OS from “2021.06.30” but the newest is from “2021.05.07”.
What’s going on here? Where can we find this ominous version?