iQaudio DAC not recognised on Pi Zero W

This forum is for topics specific to the Raspberry Pi and Arch Linux ARM

iQaudio DAC not recognised on Pi Zero W

Postby slackline » Thu Mar 01, 2018 2:47 pm

Hi,

I've a PiZero W that I've paired with an iQaudio DAC Zero to have headless and synchronised music playing (served up a a Pi2 with a iQaudio DAC+ thats running snapcast).

I setup the PiZero W a number of months ago before having speakers to work with it full-time and used i2select, it worked at the time but since I didn't have a dedicated pair of speaker its sat around until recently as I now have a pair of speakers to get it setup and deployed.

Updated the PiZero W but i2select is no longer available and having read through the iQaudio documentation I've seen its now handled by the addition of device_tree_overlays=iqaudio-dacplus to the /boot/config.txt although I notice there is a difference between the documentation (dtoverlay=) and the defaults in the supplied file (device_tree_overlay=).

My /boot/config.txt based on table 2 on page 3 currently reads...

/boot/config.txt
$this->bbcode_second_pass_code('', '
# grep -v '^#' /boot/config.txt
device_tree_overlay=iqaudio-dacplus
gpu_mem=64
')

...and on rebooting the relevant modules are loaded (suggesting that dtoverlay= and device_tree_overlay= are synonyms and work the same), the output of lsmod | grep 'snd'...

lsmod | grep snd
$this->bbcode_second_pass_code('', '
# lsmod | grep snd
snd_soc_pcm512x_i2c 16384 0
snd_soc_pcm512x 28672 1 snd_soc_pcm512x_i2c
snd_soc_iqaudio_dac 16384 0
snd_soc_bcm2835_i2s 16384 0
snd_soc_core 176128 3 snd_soc_pcm512x,snd_soc_iqaudio_dac,snd_soc_bcm2835_i2s
snd_compress 20480 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_bcm2835 32768 0
snd_pcm 94208 5 snd_soc_pcm512x,snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_bcm2835,snd_soc_core
snd_timer 32768 1 snd_pcm
snd 65536 5 snd_compress,snd_timer,snd_bcm2835,snd_soc_core,snd_pcm
')

Checking this against my Raspberr Pi2's these are the same modules that are loaded (and is what I'd expect from the iQaudio documentation since it indicates they use the same overlay).

Unfortunately the iQaudio DAC isn't detected on the PiZero W as the following shows...

$this->bbcode_second_pass_code('', '
# aplay -l
aplay: device_list:272: no soundcards found...
')

$this->bbcode_second_pass_code('', '
# ls -l /proc/asound/
total 0
-r--r--r-- 1 root root 0 Mar 1 14:39 cards
-r--r--r-- 1 root root 0 Mar 1 14:39 devices
-r--r--r-- 1 root root 0 Mar 1 14:39 modules
dr-xr-xr-x 2 root root 0 Mar 1 14:39 oss
-r--r--r-- 1 root root 0 Mar 1 14:39 pcm
dr-xr-xr-x 2 root root 0 Mar 1 14:39 seq
-r--r--r-- 1 root root 0 Mar 1 14:39 timers
-r--r--r-- 1 root root 0 Mar 1 14:39 version
# cat /proc/asound/cards
--- no soundcards ---
# cat /proc/asound/devices
33: : timer
# cat /proc/asound/modules
# cat /proc/asound/pcm
# cat /proc/asound/timers
G0: system timer : 10000.000us (10000000 ticks)
# cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k4.14.22-1-ARCH.
')

First thoughts were that its a physical connection issue and I've ensured that the DAC itself, which was originally screwed together using the supplied bolts/spacers/screws and it is definitely connected physically.

Searching I've found an old locked thread about a the Pi3 not working with an older verison of the kernel 4.9.28 (see here) but I'm now way past that on 4.14.22-1...

$this->bbcode_second_pass_code('', '
# uname -a
Linux alarmpiw 4.14.22-1-ARCH #1 SMP Tue Feb 27 06:55:49 UTC 2018 armv6l GNU/Linux
')

The only other references to Arch/iQaudio DACs are on the Archphile pages which use the older i2select method (I've been unable to work out where i2select commands/packages are now as they are no longer available in the repository as far as I can work out).

I'm now stumped as to what to try next, any suggestions or pointers would be very much appreciated.
slackline
 
Posts: 15
Joined: Wed May 11, 2016 8:18 pm

Return to Raspberry Pi

Who is online

Users browsing this forum: No registered users and 11 guests