I am having a strange problem with my DAC+. I am using it on a Pi 2. It was working fine, then I rebooted the Pi. After I rebooted, the card is detected OK and has its green light on, but does not produce any sound. I have tried reinstalling the OS (Raspbian) and have also tried OpenELEC but neither work.
Strangely, before the card stopped working I could not get OpenELEC to connect to my wireless network - Kodi crashed. Now it works fine. This is probably a coincidence. I was using Raspbian and the DAC+ worked fine with this.
I am using the official Raspberry Pi power supply. What information do you need to help me debug this further? I have made certain that I have not made a mistake with the settings on my hifi, and it is definitely the hifiberry/Pi that is the problem.
Thanks
Andrew.
Date
Votes
14 comments
-
HiFiBerry team Let's check with Raspbian. What is the output of "aplay -l"? How do you test the sound output?
Best regards
Daniel -
Chris Mullen "...but does not produce any sound." <= Need more detail. Do u mean while logged onto the PI2 directly u can't get any sound out of the DAC+ ??
Or do u mean when you cast sound from another device to the RPI2 u get no sound. As an example this could be a client DLNA or Airplay issue with nothing wrong with the RPI2 setup. -
Andrew Pattison Apologies - I missed out a step when setting the card up. I did things in a bit of a hurry and didn't notice that I needed to create a /etc/asound.conf file and add settings to it. It is working now under Raspbian. -
Andrew Pattison Looks like I spoke too soon - it has stopped working again. The green light comes on when I play a test sound using aplay. The output of aplay -l is:
pi@raspi3 ~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0 -
Andrew Pattison Some more information: I only have one device I can check the output of the HifiBerry with at the moment - the back-to-back 3.5mm headphone adaptor I have has gone walkabout - that would enable me to connect headphones or my set of computer speakers.
To see if I could detect any output from the hifiberry using a slightly different method, I connected the output of the hifiberry to the microphone socket of my laptop. No sound played, but there was a change to the noise on the line while the sound file was playing. -
Andrew Pattison I have tried powering my Pi 2 using a different power supply - one that is designed for the Pi. It outputs 5.25V and 2A. This made no difference. I also turned the volume right up on the amplifier when it is connected to the hifiberry - I can hear slight changes in the noise when I play a test sound using aplay. -
HiFiBerry team Check the output volume with amixer or alsamixer. The "PCM" mixer should be at 96% for full level.
amixer sset PCM96%
It is already worked, this is most likely not a power supply, but a configuration issue.
Best regards
Daniel -
Andrew Pattison I have got it working. Here is what I did:
I am setting some options in /etc/rc.local. The settings I was making were:
# configure HifiBerry
# set PCM volume to 180/215
amixer cset numid=1 180,180
# set DSP Program to 'Fixed process flow'
amixer cset numid=6 3
# switch de-emphasis off (here on = off for some reason)
amixer cset numid=5 on
I then changed the DSP program to 1 and the de-emphasis switch to off. It then produced sound. I then changed the de-emphasis switch to on and it stayed working. I then changed the DSP program to 4 and it also stayed working. So it seems that the DSP program 'fixed process flow' does not work. Which is odd as I'm reasonably sure I had it working on this setting before.
Confusingly the logic of the de-emphasis switch seems to be reversed - that is, when the switch is on this means that de-emphasis is switched off. That is what it sounds like to me anyway. Can you possibly tell me what kind of de-emphasis is being applied?
Thanks
Andrew. -
Andrew Pattison Sorry to have troubled you with something that was my fault.
I have now set my hifiberry up on OpenELEC and it is working well. Very impressed with the sound it is producing - this is a great product! -
gesamtplan Sorry for hangin on this post. I think I am to stupid to create a new topic.
I got issues with my Raspberry Pi B+ and the Hifiberry DAC+ too.
I was updating the Kernel via rpi-update to 3.18.8 yesterday. After doing the overlay described in here. The DAC+ works fine. But I need to compile the kernel cause I want the "ACT" LED on another GPIO to see the raspi working.
I downloaded the new GIT for the 3.18.8 kernel and compiled it with the toolchain recommended on a Ubuntu machine using the .config from the working Rapsian. After moving the kernel Image and the modules the LED is working fine but at the startup I got message from the "pcm512x" and the DAC+ is not working anymore.[ 4.284787] input: Chicony USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:04F2:0402.0001/input/input0
[ 4.324306] hid-generic 0003:04F2:0402.0001: input,hidraw0: USB HID v1.11 Keyboard [Chicony USB Keyboard] on usb-bcm2708_usb-1.3/input0
[ 4.500966] input: Chicony USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:04F2:0402.0002/input/input1
[ 4.521010] hid-generic 0003:04F2:0402.0002: input,hiddev0,hidraw1: USB HID v1.11 Device [Chicony USB Keyboard] on usb-bcm2708_usb-1.3/input1
[ 4.687056] udevd[158]: starting version 175
[ 5.952069] bcm2708_i2c_init_pinmode(1,2)
[ 6.103807] bcm2708_i2c_init_pinmode(1,3)
[ 6.275168] bcm2708_i2c bcm2708_i2c.1: BSC1 Controller at 0x20804000 (irq 79) (baudrate 100000)
[ 6.597987] bcm2708_spi bcm2708_spi.0: master is unqueued, this is deprecated
[ 6.786005] bcm2708_spi bcm2708_spi.0: SPI Controller at 0x20204000 (irq 80)
[ 6.910026] random: nonblocking pool is initialized
[ 9.297997] pcm512x 1-004d: No SCLK, using BCLK: -2
[ 9.358742] pcm512x 1-004c: Failed to reset device: -5
[ 9.381966] pcm512x: probe of 1-004c failed with error -5
[ 9.405514] usbcore: registered new interface driver rtl8192cu
[
After changing the kernel to the 3.18.8 to the rpi-update one the DAC+ works. Is the GPIO 17 in any way needed for the HIFIBERRY DAC+? Cause on this PIN my LED is hanging. -
HiFiBerry team Most likely you have compiled a kernel without device tree support. In this case you need to configure the board as you did before in 3.12.x
Best regards
Daniel -
gesamtplan Hello Daniel,
thanks for the fast reply. How can I insert a device tree support? First I will compile the kernel again with the right settings for LED support and try on your advice to mount the modules via /etc/modules.
Best regards
Rainer -
HiFiBerry team From our compile script:
cd $BASE/tools/mkimage
./mkknlimg ${KERNEL_SRC}/arch/arm/boot/zImage $BASE/kernel.img -
gesamtplan Hello Daniel,
with the "old" method an my compiled kernel the system is running now.
When I use the commands from your compile script the kernel.img is made and running too, but without led although I used the kernel I recently compiled on the Ubuntu system.
I know that's not your business but perhaps you can help me with understanding what I am doing and what's going on.
Rainer
Please sign in to leave a comment.