Date
Votes
62 comments
-
René Geilenkirchen Hallo Daniel!
just got my Digi in the mail, soldered the 6pin header, copied the testtone image, switched the power on and....
got a 1kHz Testtone after a few seconds!
Yeah ;)
Next up i'll try and see if i can get my squeezeplug installation working.
René -
HiFiBerry team Great :-)
Enjoy your sound!
Daniel -
Marijn van Butselaar Got my HiFiBerry Digi as well! Tested it on a couple of Pis, all with three different chargers (Original, el-cheapo China and from an Asus tablet) and both optical and coax.
Model A Revision 2.0 256MB (Rev 0008): All ok
Model B Revision 2.0 512MB (Rev 000f): All ok
But half of the P5 holes were factory-filled with solder, so was a bit of a pain to put the header on...Model B Revision 2.0 256MB (Rev 0005): All ok
Model B Revision 2.0 512MB (Rev 000e): All ok
Only problem was that sometimes the Digi would not power on (D1 led off, and not detected by the kernel module). This was mostly on the 000e model I used, but also once on the 000f model.
Now all I need is more software support (Hello Sam Nazarko).
PS. That tone can be quite annoying ;) -
HiFiBerry team Dear Marjin,
The problem that the card does not powerup correctly: I assume, this might happen during plugging in the Mini-USB connector. Can you check if this still happens, if you connect/disconnect the power by plugging/unplugging the mains supply?
About the software: I'm in contact with a developer from Broadcom and I expect to have an experimental OpenElec build with HiFiBerry Digi support soon.
Best regards
Daniel -
David Tischler Hi!
Received mine yesterday, first impression: Works like a charm on my Model B Revision 2.0 512MB Revision 000d!
The test-image immediately produced the annoying sound. On my existing Raspbian installation, after updating the system and adding the entries to /etc/modules as described here, on the first reboot I got the following syslog entries:[ 13.373838] snd-hifiberry-digi snd-hifiberry-digi.0: ASoC: CODEC wm8804.1-003b not registered
[ 13.385585] snd-hifiberry-digi snd-hifiberry-digi.0: snd_soc_register_card() failed: -517
[ 13.396707] platform snd-hifiberry-digi.0: Driver snd-hifiberry-digi requests probe deferral
I had to edit /etc/modprobe.d/raspi-blacklist.conf and comment out the following line:blacklist i2c-bcm2708
After a reboot the syslog now shows:[ 13.435772] snd-hifiberry-digi snd-hifiberry-digi.0: wm8804-spdif <-> bcm2708-i2s.0 mapping ok
And now squeezelite is playing through the HiFiBerry Digi.
David -
Marijn van Butselaar Daniel,
I was indeed plugging/unplugging the Micro-USB connector. Did some (well more then some) testing with both ways, Micro-USB and mains. In seems to make a difference, but still sometimes it would not power on either way.
Could you explain why the two different ways of connecting the power would make a difference?
About the software: Great to hear there is progress on this behind the scenes. Although I prefer Raspbmc, beggars can't be choosers.
Keep up the good work!
Regards,
Marijn. -
HiFiBerry team Dear Marijn,
the Micro-USB connector is not really a good design for a power connector. During plugging in the power it may not give a good connection all the time. That means, the voltage may drop during plugging in. This may lead to an undefined state of some components.
I think, Raspbmc support will also follow soon. However, Sam seems to be very busy at the moment.
Best regards
Daniel -
Gerard Got mine Hifiberry Digi today, soldered, and tested with the testtone image. This worked immediately.
Then I tried the new Volumio 1.2 Beta. Just activate from the menu and it worked.
Great! -
Antony Hubbard My Digi arrived yesterday. I soldered the header, assembled and powered up.
I was running Squeezeplug v7 image which didn't have all kernel modules (.ko) available. The diagnostic script determined this for me.
I downloaded latest version of Raspian from RPi Foundation and followed instructions.
Worked perfectly.
I then installed Squeezelite and all is working.
Great product and support. -
Olivier REVELIN Hi there !
Digi recieved and soldered. Works like a charm with speaker-test command. Will try with volumio 1.2 today. (1.1 worked with some tweaking). -
Bernard Wilkens Received the Digi today. plugged it on a Rev b Raspberry board. Playing Picore player Rev 1.13 like a charm. -
David Tischler Hi!
After a few days of using the HiFiBerry Digi it suddenly stopped working in the middle of playing a song.
Upon booting:- D1 Led On
- syslog shows "snd-hifiberry-digi snd-hifiberry-digi.0: wm8804-spdif <-> bcm2708-i2s.0 mapping ok"
When I try to play sin1000_48khz.wav- The optical output on HiFiBerry turns red
- A light clicking noise can be heard, followed by silence
- After 20 seconds message "aplay: pcm_write:1710: write error: Input/output error" is shown
And the syslog now contains[ 469.361731] bcm2708-i2s bcm2708-i2s.0: I2S SYNC error!
[ 489.458744] bcm2708-dmaengine bcm2708-dmaengine: DMA transfer could not be terminated
Connecting another music source to the amp, using the same input and the same cable as used in the test before, works fine.
I also removed the HiFiBerry and checked the soldered P5 header by turning the GPIO pins on and off, that looked ok.
Any suggestions what else to check?
David -
Bernard Wilkens Did some more testing of the Digi with Picoreplayer. In my setup it does not play 24/192 files. Also tested with some 24/96 files, these play like a charm as do 16/44 files.
Just used the Picoreplayer with teh default settings of version 1.13. -
HiFiBerry team @David Tischler: Do you have another Raspberry Pi available? I've seen a problem like this once. In this case it was a hardware problem on the Raspberry.
@Bernnard Wilkens: I'm not sure, if piCorePlayer supports 24/192 files or if this is a problem with your DAC. Many DACs support only up to 96/24. Do you use the Cinch or the optical output? -
Christi Scarborough Can confirm the Digi is working here with my Model A running Volumio (I configured the kernel modules manually as per the HifiBerry instructions. The test tone plays, although there are underruns which cause breaks in the sound. This doesn't seem to be a problem in normal operation, so I suspect it may be an issue with root lacking permissions on the audio buffer device. -
Christi Scarborough Oh dear, it looks like I may have spoke too soon. After 2.5 hrs or so of playback, it stopped mid track. There is no longer a green light on the Digi. Help? -
HiFiBerry team Dear Christi, if you power it off and on again, does it work again? -
Christi Scarborough Sadly not. Even removing the power cable and retrying results in no green light and no sound. -
HiFiBerry team Ok, can you just turn if of for 10 minutes or so and try again. In every case I will send you a new one. -
HiFiBerry team What was your oder number? -
Christi Scarborough 2746 -
Christi Scarborough Thanks. Sorry to say that leaving for 10 mins doesn't seem to have helped. -
Leif S Y Gutehall Hi
Got my Digi yesterday and installed it today, it boots as it should and all lights are on, but no sound. The solder joints look ok, but ill get my DVM back tomorrow and can test them, doubt thats the issue.
I tried both through Optic output and RCA, no signal on either on them that my DAC can recognise.[ 5.621819] bcm2708_i2c_init_pinmode(0,0)
[ 5.783706] bcm2708_i2c_init_pinmode(0,1)
[ 5.859368] bcm2708_i2c bcm2708_i2c.0: BSC0 Controller at 0x20205000 (irq 79) (baudrate 100000)
[ 6.024191] bcm2708_i2c_init_pinmode(1,2)
[ 6.127861] bcm2708_i2c_init_pinmode(1,3)
[ 6.186095] bcm2708_i2c bcm2708_i2c.1: BSC1 Controller at 0x20804000 (irq 79) (baudrate 100000)
[ 6.886436] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory
[ 10.582218] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 11.056483] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 12.026768] wm8804 1-003b: revision E
[ 12.038752] snd-hifiberry-digi snd-hifiberry-digi.0: wm8804-spdif <-> bcm2708-i2s.0 mapping ok
[ 17.031646] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I do have error messages in mounting the fat directory, but I have tried two domes on different DS cards and the message still show up.
/Stefan G -
HiFiBerry team Hi Stefan,
that looks good. The FAT entry is not a problem. I guess, the LED on the optical transmitter lights up - right? The control connection works ok. There could still be a problem with one of the sound signal lines that are on the P5 header.
Did you test it with the test image?
If yes, can you please login and do the following:
sudo pkill mplayer
mplayer test.wav (not sure how the test file is named, please have a look with ls).
Then check if mplayer runs or gets stuck.
Thanks
Daniel -
Leif S Y Gutehall Hi Daniel,
Yes the light in the Toslink transmitter light up, i tried your suggestions and it all seems fine, except for no sound and no signal received by the dac.pi@raspberrypi ~ $ sudo pkill mplayer
pi@raspberrypi ~ $ ls
Desktop ocr_pi.png python_games test-48.wav
pi@raspberrypi ~ $ mplayer test-48.wav
Creating config file: /home/pi/.mplayer/config
MPlayer svn r34540 (Debian), built with gcc-4.6 (C) 2000-2012 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing test-48.wav.
libavformat version 53.21.1 (external)
Mismatching header version 53.19.0
Audio only file format detected.
Load subtitles in ./
==========================================================================
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio: 192000->192000)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
waitpid(): No child processes
AO: [pulse] Init failed: Internal error
Failed to initialize audio driver 'pulse'
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A: 124.4 (02:04.3) of 300.0 (05:00.0) 0.3%
MPlayer interrupted by signal 2 in module: play_audio
A: 124.4 (02:04.4) of 300.0 (05:00.0) 0.3%
I do suspect a faulty connection now.. i will try to resolder and see. -
Leif S Y Gutehall No luck,
I resoldered twice and still the same results. Do you have any test points on the card or the pinout for the sockets? Tomorrow I'll try to get the oscilloscope out to see how things look from there. -
HiFiBerry team It stops at 0.3%? Looks like the chip does not generate the correct clock or the Raspberry doesn't receive it. Could be a problem with the chip or the soldering. Will you have an oscilloscope available soon?
Best regards
Daniel -
Leif S Y Gutehall Daniel
No it continue playing, in this instance I stopped playback myself. I have a 'scope in my closet, just didn't have time to bring it out today. -
HiFiBerry team Having it constantly playing is a good sign.
Can you please post the output of "aplay -l" -
Jeroen Lagerwerf Hello, unfortunately mine mostly generate noise.
The noise sounds different every time i start playback. On the test image is used aplay test-48.wav and mplayer test-48.wav - they both produce different sound randomly.
After some testing on Openelec, it played normal music only once (again, after restarting paplayer repeatedly). But 99% of the time there is just noise or like a noisy fm station.
(tested on a DacMagic and Marantz receiver)
Regards,
Kamp
Please sign in to leave a comment.