washburn_it
Hi,
today, after turning on the RuneAudio PI2 (equipped with a DAC+ earphone jack version), I noticed that the audio output was mute and the volume control was not working.
So I went to the menu to set the audio output but I just found "HDMI out" or "Analog out" but the "HiFiBerry DAC+" was not present anymore.
Two days ago everything was working so...what could I check to fix it?
I have been using it for months till now.
Thank you, regards.
Roberto
hondagx35
Hi Roberto,
please post your debug info.
Frank
washburn_it
Hi Frank,
I will do it as soon as I dismount it from my car.
Thanks for the reply.
Roberto
washburn_it
Hi,
the log exceeds 60000 chars so the forum doesn't let me publish it.
I tried to attach a TXT file with it but it's not allowed.
How can I do?
By the way, I noticed that the green led on the hifiberry board (DAC+ earphone version) is turned off even if the board is correctly connected to the GPIO port.
Thank you, regards.
Roberto
hondagx35
Hi Roberto,
To get the best possible support, please specify your hardware and RuneAudio version. Collecting debug info is also suggested.
Frank
washburn_it
Here it is:
http://pastebin.com/HS1U1v1X
the release version: 0.4 (build: beta-20141216) and the board is a Raspberry PI2 (with HIfiberry DAC+ earphone version).
I look forward for any news
Roberto
hondagx35
Hi Roberto,
the I2C communication between your Pi and the DAC is not working.
[ 7.694930] snd-rpi-hifiberry-dacplus sound: ASoC: CPU DAI (null) not registered
[ 7.695007] snd-rpi-hifiberry-dacplus sound: snd_soc_register_card() failed: -517
[ 7.695044] platform sound: Driver snd-rpi-hifiberry-dacplus requests probe deferral
[ 7.698846] pcm512x 1-004d: Failed to reset device: -5
[ 7.699020] pcm512x: probe of 1-004d failed with error -5
[ 7.699066] bcm2708_i2c 3f804000.i2c: BSC1 Controller at 0x3f804000 (irq 79) (baudrate 100000)
[ 7.699576] snd-rpi-hifiberry-dacplus sound: ASoC: CPU DAI (null) not registered
[ 7.699629] snd-rpi-hifiberry-dacplus sound: snd_soc_register_card() failed: -517
[ 7.699662] platform sound: Driver snd-rpi-hifiberry-dacplus requests probe deferral
[ 7.700510] snd-rpi-hifiberry-dacplus sound: ASoC: CPU DAI (null) not registered
[ 7.700572] snd-rpi-hifiberry-dacplus sound: snd_soc_register_card() failed: -517
[ 7.700615] platform sound: Driver snd-rpi-hifiberry-dacplus requests probe deferral
[ 7.701205] snd-rpi-hifiberry-dacplus sound: ASoC: CODEC DAI pcm512x-hifi not registered
[ 7.701281] snd-rpi-hifiberry-dacplus sound: snd_soc_register_card() failed: -517
[ 7.701322] platform sound: Driver snd-rpi-hifiberry-dacplus requests probe deferral
I first would try to use a fresh image or the Hifiberry test image.
If this also does not work your DAC or Rp hardware may be faulty.
Frank
washburn_it
I already tried with the test image and unfortunately the only thing that it can reproduce is noise with a recurring toc-toc-toc...I think that the board is broken.
I contacted the seller (knowhowtech.de) to know the procedure for defective units.
Thank you, regards.
Roberto
rastus
washburn_it wrote...the only thing that it can reproduce is noise with a recurring toc-toc-toc...I think that the board is broken.
From being in the car, maybe not affixed well enough to maintain minimum movement?
washburn_it
I tried the "car media center" on my desk so it was not connected to the car.
When it was connected to the car, the sound was very clean, no noise.
Regards,
Roberto
rastus
washburn_it wroteI think that the board is broken.
I mean, did it brake because it was in your car? ie, moving around, mobile, etc.
hondagx35
Hi,
rastus wroteI mean, did it brake because it was in your car? ie, moving around, mobile, etc.
or overvoltage!
Frank
washburn_it
Overvoltage don't think since the board takes power from the Raspberry and the Raspberry is powered through a switching step-down power supply (12V to 5V 3A) that is directly connected to the battery of the car.
So I think that an overvoltage would have affected also the Raspberry.
Of course everything is possible but two raspberries and a HDMI LCD are still perfectly working.
PeteB
The connection between the HiFiBerry DAC+ and the Pi depends on a few GPIO pins at the 40-pin header. The GPIO and pin numbers are published on the HiFiBerry web site.
The I2C port uses pins 3 and 5, and the DAC+ functions a few more. If even one of those pins is not making contact, or disabled/not working for some reason, the DAC+ will not work, even if everythign else does.
Do you have a multimeter with a resistance (or better yet continuity) setting? If you do, then you may be able to check all the connections one by one (with power disconnected), as well as the expected voltages (with power on, and RuneAudio turned off).
bayed
I can confirm Roberto's debug output for the RPi2 with a vanilla image, the DAC works with a Raspberry 3 and the same image though.
washburn_it
I tried with another module like mine and I had the confirm that there is something that is not working.
I measured the voltage on the P3 connector (on the board) and +5V are missing.
The same is on the correspondant pin of the 2nd GPIO connector (the one with the holes, not the black one) so I think that the problem are +5V missing in a part of the circuit.
Instead they are present on the black connector.
I opened a thread on the Hifiberry official forum so I hope they may give me a clue to try to fix the board (if possible, I worked as electronic technician for several years).
Roberto
washburn_it
I tried to compare the working board with the "faulty" board but unfortunately I didn't find anything new except for what I already found.
Without a schematic is hard to find the fault and I had not useful info from the Hifiberry forum.
Of course they can't reveal too much about the hardware of the board.
So I put the faulty board in a corner, waiting to find more info and try to find a fix (if possible) again.
I checked the +12V power line coming from the battery with a portable oscilloscope to find if there were peaks or strange signal over the 12V but there are just some millivolt of noise but the "signal" is clean.
So just for caution I've set the step-down output voltage just a bit lower than 5V (+4.8) but the output voltage is very stable anyway.
Regards,
Roberto
rastus
So it was/is the board itself, yes? Monty Python: It's not sleeping, it's 'dead'?
washburn_it
Yes it is the board itself broken...lucky me, one of my colleagues had one unused so I bought it at half price
rastus
washburn_it wrote...lucky me, one of my colleagues had one unused so I bought it at half price
Cool!
