Hello from a hifiberry/DAC noob. I have a DAC+ Zero on top of a Pi Zero 2W, and am writing for help after spending dozens of hours trying to figure it out on my own. I'm currently attempting to use Volumio. Config file has been updated properly, DAC+ Zero is recognized, and once I get Volumio up and running, and seems to be playing fine--but I can't get any output. I've been through the no sound checklist, and don't know where to go to here except either consider that the hifiberry hardware that I received has an issue, or I should just buy a Pi 3 B+ and hope to avoid the same issues with that board. I've been through every combination of settings on the Volumio side, from I2s/DAC options to everything else possible, it seems. Volumio seems to be playing, but I'm just not getting any output no matter what I try. FTR, I have two Pi Zero 2w's, and both output fine with not only Volumio, but also hifiberry OS, etc. Power supply is a 5V 3A. Any help would be greatly appreciated, thanks!
13 comments
-
HiFiBerry team On the Pi Zero, the usual problem are bad solder connections on the 40-pin header. Check the solderings you did with a multimeter.
-
John Thanks for your reply. I checked continuity on all power and ground pins, as well as GPIOs 18-21, and also pins 27-28. All were solid. Maybe I've made an error on my boot/config.txt file? I appreciate your help.
-
John I didn't detect any pertinent text when I ran dmesg, but I did with sudo vcdbg log msg. Please let me know if you'd like the dmesg output as well. Thank you!
~ $ sudo vcdbg log msg
001177.577: brfs: File read: /mfs/sd/config.txt
001178.496: brfs: File read: 1225 bytes
001245.249: brfs: File read: /mfs/sd/config.txt
001246.222: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
001747.934: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
001747.992: *** Restart logging
001748.018: brfs: File read: 1225 bytes
001777.946: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
001787.162: HDMI0: hdmi_pixel_encoding: 162000000
002749.143: brfs: File read: /mfs/sd/initramfs7
002749.168: Loaded 'initramfs7' to 0x0 size 0xf27525
002769.908: initramfs loaded to 0x1b0c8000 (size 0xf27525)
002770.790: dtb_file 'bcm2710-rpi-zero-2-w.dtb'
002770.807: Trying Device Tree file 'bcm2710-rpi-zero-2-w.dtb'
002770.834: brfs: File read: 15889701 bytes
002776.591: brfs: File read: /mfs/sd/bcm2710-rpi-zero-2-w.dtb
002776.614: Loaded 'bcm2710-rpi-zero-2-w.dtb' to 0x100 size 0x7f2f
002788.109: dtdebug: delete_node(/__local_fixups__)
002791.593: brfs: File read: 32559 bytes
002804.542: dtdebug: using platform 'bcm2835'
002805.399: brfs: File read: /mfs/sd/overlays/overlay_map.dtb
002810.825: dtdebug: overlay map loaded
002834.883: dtparam: uart0_clkrate=48000000
002838.203: dtdebug: /__overrides__ has no uart0_clkrate property
002838.218: Unknown dtparam 'uart0_clkrate' - ignored
002838.242: brfs: File read: 4743 bytes
002843.161: brfs: File read: /mfs/sd/config.txt
002843.285: dtparam: i2s=on
002846.476: dtdebug: found override i2s
002846.515: dtdebug: override i2s: string target 'status'
002853.479: brfs: File read: 1225 bytes
002860.559: dtdebug: Opened overlay file 'overlays/hifiberry-dac.dtbo'
002861.106: brfs: File read: /mfs/sd/overlays/hifiberry-dac.dtbo
002871.946: Loaded overlay 'hifiberry-dac'
002879.939: dtdebug: merge_fragment(/soc/i2s@7e203000,/fragment@0/__overlay__)
002879.966: dtdebug: +prop(status)
002880.676: dtdebug: merge_fragment() end
002880.836: dtdebug: merge_fragment(/,/fragment@1/__overlay__)
002889.042: dtdebug: merge_fragment(/pcm5102a-codec,/fragment@1/__overlay__/pcm5102a-codec)
002889.071: dtdebug: +prop(#sound-dai-cells)
002890.152: dtdebug: +prop(compatible)
002891.139: dtdebug: +prop(status)
002892.205: dtdebug: merge_fragment() end
002892.233: dtdebug: merge_fragment() end
002903.875: dtdebug: merge_fragment(/soc/sound,/fragment@2/__overlay__)
002903.901: dtdebug: +prop(compatible)
002904.340: dtdebug: +prop(i2s-controller)
002905.173: dtdebug: +prop(status)
002905.603: dtdebug: merge_fragment() end
002907.496: brfs: File read: 668 bytes
002925.610: dtdebug: Opened overlay file 'overlays/vc4-kms-v3d.dtbo'
002927.414: brfs: File read: /mfs/sd/overlays/vc4-kms-v3d.dtbo
002973.699: Loaded overlay 'vc4-kms-v3d'
002973.715: dtparam: noaudio=true
002973.859: dtdebug: found override noaudio
002997.427: dtdebug: fragment 11 disabled
003004.477: dtdebug: merge_fragment(/reserved-memory/linux,cma,/fragment@0/__overlay__)
003004.505: dtdebug: +prop(size)
003005.466: dtdebug: merge_fragment() end
003014.841: dtdebug: merge_fragment(/soc/i2c@7e805000,/fragment@1/__overlay__)
003014.868: dtdebug: +prop(status)
003015.443: dtdebug: merge_fragment() end
003027.070: dtdebug: merge_fragment(/soc/fb,/fragment@2/__overlay__)
003027.095: dtdebug: +prop(status)
003027.534: dtdebug: merge_fragment() end
003036.652: dtdebug: merge_fragment(/soc/pixelvalve@7e206000,/fragment@3/__overlay__)
003036.680: dtdebug: +prop(status)
003037.271: dtdebug: merge_fragment() end
003046.507: dtdebug: merge_fragment(/soc/pixelvalve@7e207000,/fragment@4/__overlay__)
003046.534: dtdebug: +prop(status)
003047.104: dtdebug: merge_fragment() end
003056.805: dtdebug: merge_fragment(/soc/pixelvalve@7e807000,/fragment@5/__overlay__)
003056.833: dtdebug: +prop(status)
003057.384: dtdebug: merge_fragment() end
003065.692: dtdebug: merge_fragment(/soc/hvs@7e400000,/fragment@6/__overlay__)
003065.719: dtdebug: +prop(status)
003066.347: dtdebug: merge_fragment() end
003076.257: dtdebug: merge_fragment(/soc/hdmi@7e902000,/fragment@7/__overlay__)
003076.283: dtdebug: +prop(status)
003076.852: dtdebug: merge_fragment() end
003086.881: dtdebug: merge_fragment(/soc/v3d@7ec00000,/fragment@8/__overlay__)
003086.907: dtdebug: +prop(status)
003087.461: dtdebug: merge_fragment() end
003097.584: dtdebug: merge_fragment(/soc/gpu,/fragment@9/__overlay__)
003097.611: dtdebug: +prop(status)
003098.129: dtdebug: merge_fragment() end
003100.264: dtdebug: merge_fragment(/soc/cprman@7e101000,/fragment@10/__overlay__)
003100.292: dtdebug: +prop(claim-clocks)
003101.639: dtdebug: merge_fragment() end
003101.737: dtdebug: fragment 11 disabled
003103.898: dtdebug: merge_fragment(/soc/txp@7e004000,/fragment@12/__overlay__)
003103.926: dtdebug: +prop(status)
003104.850: dtdebug: merge_fragment() end
003114.973: dtdebug: merge_fragment(/soc/hdmi@7e902000,/fragment@13/__overlay__)
003115.000: dtdebug: +prop(dmas)
003115.559: dtdebug: merge_fragment() end
003116.995: dtdebug: merge_fragment(/chosen,/fragment@14/__overlay__)
003117.020: dtdebug: +prop(bootargs)
003118.021: dtdebug: merge_fragment() end
003127.478: dtdebug: /aliases:serial5=uart1
003127.632: dtdebug: /aliases:serial5=uart0
003127.667: brfs: File read: 2760 bytes
003131.456: brfs: File read: /mfs/sd/cmdline.txt
003131.528: Read command line from file 'cmdline.txt':
003131.553: 'console=serial0,115200 console=tty1 root=PARTUUID=3324453a-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=US'
003142.713: dtparam: uart1=off
003145.880: dtdebug: found override uart1
003145.918: dtdebug: override uart1: string target 'status'
003263.056: dtparam: cam0-pwdn=40
003266.251: dtdebug: found override cam0-pwdn
003266.286: dtparam: arm_freq=1000000000
003269.483: dtdebug: found override arm_freq
003269.539: dtdebug: override arm_freq: cell target clock-frequency @ offset 0 (size 4)
003278.645: dtdebug: override arm_freq: cell target clock-frequency @ offset 0 (size 4)
003287.845: dtdebug: override arm_freq: cell target clock-frequency @ offset 0 (size 4)
003297.169: dtdebug: override arm_freq: cell target clock-frequency @ offset 0 (size 4)
003306.701: dtparam: core_freq=400000000
003310.113: dtdebug: /__overrides__ has no core_freq property
003310.128: Unknown dtparam 'core_freq' - ignored
003323.664: dtdebug: delete_node(/hat)
003330.843: brfs: File read: 176 bytes
003750.786: brfs: File read: /mfs/sd/kernel7.img
003750.812: Loaded 'kernel7.img' to 0x8000 size 0x6aab28
003750.849: Device tree loaded to 0x1b0bfa00 (size 0x850d)
003754.660: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
007633.297: vchiq_core: vchiq_init_state: slot_zero = 0xcb180000, is_master = 1
007642.954: TV service:host side not connected, dropping notification 0x00000002, 0x00000001, 0x00000010
xxxxx@raspberrypi:~ $ -
HiFiBerry team Is the device listed when running aplay -l ?
-
John It is.
xxxxxx@raspberrypi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
xxxxxx@raspberrypi:~ $ -
John Any other thoughts on how I might be able to trouble shoot this? Or at this point do you think it might be a hifiberry hardware issue? Since my last post I've again also tried LibreELEC, OSMC, and Moode, with the same sort of issue. Audio seems to be playing fine, just no sound.
-
HiFiBerry team Usually this is caused by hardware problem. However, there is no way to tell if it's the Pi, the DAC or the connection between both. Bets you can do is try another Pi.
-
John I've tried my other Pi Zero 2W, same result. I've successfully checked all 40 pins for continuity on both of those Pis, as well as the DAC+ Zero, so if it's a hardware issue, it doesn't seem to be in the connections. FTR, both Pis run music fine with no DAC.
Do you have any case studies/config notes of a recent successful pairing of the Zero 2W and the DAC+ Zero? I've scoured the forums here and at Volumio, and see a lot of people have had issues finding a solution as well. I bought this DAC because it says it's compatible with the Pi Zero 2W, but after months of tinkering, and without seeing any documentation of a successful pairing, I can't help but begin to question that claim.
As I've seen lots of issues with the Pi Zero 2W/DAC+ Zero pairing, I might as well ask while I'm writing-- if I got a Pi 3 B+, do I avoid all of these issues, whatever they are?
-
HiFiBerry team The DAC+ Zero is compatible with all Pi's with the 40-pin connector. However, there are much more issues when using it with the Pi Zero. The reason is simply very often bad solder connections. We see these regularly. To make sure, I recommend to try with a Pi with a pre-soldered header. If there is still no sound, get in contact with the dealer you bought it from.
BTW: There is no "pairing" in of any kind involved. The Pi just sends audio data that the DAC. -
John Wouldn't my successful continuity tests (as well as magnified visual inspection) indicate that the solder joints are fine? I know you keep on saying bad soldering, but every visual and electrical test indicates otherwise.
I know there is no 'pairing'. Poor choice of words.
Can you answer my question about the Pi 3? Given my successful tests so far, if I'm getting a new unit I'd like to go with the Pi 3 B+. Are there far less issues reported with the Pi 3, I hope?
Thanks for your help.
-
HiFiBerry team > Wouldn't my successful continuity tests (as well as magnified visual inspection) indicate that the solder joints are fine?
I can't comment on this. We have seen too many issues with poor solder connections. However, if the connections are 100% ok, you will get the same problem with a Pi3. -
John Back again. This time, I tried the Dac+ Zero on a Pi 4b, and configured the config.txt in a variety of combinations, in line with your docs. Still no luck. So I think that rules out solder connections, since I've now tested it on 2 Pi Zero 2Ws, and now the Pi 4b.
-
HiFiBerry team It might be a problem with the DAC. You can contact us by mail at support@hifiberry.com. Let us know when and where you bought it and we can check about the warranty process.