0

Why is the Digi+ sold if it isn't supported anywhere?

itsikhefez

October 11, 2014 17:08

None

Follow

I have to say that this is very frustrating.

I've tried getting the Digi+ to work with RuneAudio 0.3-alpha, Volumio 1.41, piMusicBox 0.5.
I flashed all of them, updated kernel, edited modules files...
And always nothing.

I've searched the entire internet for solutions, even here, and nothing.
What is the point of having a product if it can't be used?

I've wasted hours on trying to get this to work

• Facebook
• Twitter
• LinkedIn

13 comments

• 0
  
  Martin Taylor October 11, 2014 17:16

  I have the Digi+ working with Volumio v1.41 very happily. Are you sure you've followed all the installation advice?
• 0
  
  itsikhefez October 11, 2014 21:12

  I have flashed an sdcard with Volumio 1.41,
  updated kernel,
  and updated /etc/modules.
  
  The installation advice is all over the place,
  Could you point me to a where it is explained thoroughly
  
• 0
  
  HiFiBerry team October 12, 2014 08:27

  Dear itsikhefez,
  
  most of the developers do the development in their free time. Unfortunately due to the monolithic architecture of the Linux kernel and the missing plug-and-play features of the Raspberry Pi Linux kernel it is a bit more complicated to configure it then it is with PCs. However I know that Andrea from Runeaudio has already implemented Digi+ support and is already testing the new release. Until then it needs some manual configuration.
  
  Best regards
  Daniel
• 0
  
  itsikhefez October 12, 2014 17:48

  I don't mind manual configuration, I am a software engineer after all.
  I would just be glad if there was a guide somewhere what manual settings need to be made.
• 0
  
  HiFiBerry team October 13, 2014 07:33

  Hi Itsikhefez,
  
  there is a configuration guide here:
  http://www.hifiberry.com/guides/hifiberry-software-configuration/
  
  Note that this is for Raspbian. Other distributions may have the configuration files on different locations.
  
  Also check my questions here:
  http://www.hifiberry.com/forums/topic/digi-with-runeaudio/
  
  Best regards
  Daniel
• 0
  
  itsikhefez October 13, 2014 07:45

  Thanks Daniel,
  I have seen these before, but I will try again.
  The modules files was in (this is not exact, I'm not next to the Pi)
  /etc/modules-load.d/raspyberrypi.conf
  
  In addition, there was one blacklist which was
  /etc/modprobe.d/snd-soc-pcm512x.conf (~)
  and the content was: blacklist snd-soc-pcm512x
  
  I've tried all the combinations of everything, but as your explanation,
  I will do the following:
  
  1) flash version 0.3-alpha
  2) update kernel* - pacman -Syu
  3) edit module files- remove any lines and put: (http://www.hifiberry.com/guides/hifiberry-software-configuration/)
  snd_soc_bcm2708**
  bcm2708_dmaengine
  snd_soc_hifiberry_digi
  
  4) remove: blacklist snd-soc-pcm512x
  5) Configure ALSA
  6) Won't change any settings in the WebUI
  
  Additional Questions:
  Q1: Should I update to latest kernel or a specific version?
  Q2: In some guides, it was snd_soc_bcm2708_i2s (not snd_soc_bcm2708), which to use?
  Q3: Do I need to configure MPD?
• 0
  
  HiFiBerry team October 13, 2014 10:03

  Dear itsikhefez,
  
  the easier way to do this is to ask Andrea from RuneAudio if he can provide you the latest internal image. I know that he has one finished.
  I don't know what the current version of the Kernel in ArchLinux is, 3.12.28/29 should work without problems.
  On the newer kernels, most modules will be auto loaded if you load the snd_soc_hifiberry_digi driver.
  
  I can't tell about mpd, I don't know how it is configured on RuneAudio and if it needs updates.
  
  Best regards
  Daniel
• 0
  
  itsikhefez October 16, 2014 08:34

  Hi Daniel
  
  As I still unsuccessful,
  I tried running the test image.
  It does not work either.
  On my monitor I could see similar errors to what I had in Rune.
  

  [   33.748654] wm8804 1-003b: Failed to read device ID: -1
  [   33.748689] wm8804 1-003b: ASoC: failed to probe CODEC -1
  [   33.748777] snd-hifiberry-digi snd-hifiberry-digi.0: ASoC: failed to instantiate card -1
  [   33.748870] snd-hifiberry-digi snd-hifiberry-digi.0: snd_soc_register_card() failed: -1
  [   33.748912] snd-hifiberry-digi: probe of snd-hifiberry-digi.0 failed with error -1

  
  
  
  Afterwards, the output of aplay was that no soundcards were detected.
  
  Before playing the test sound, it wrote that no sound cards were found and it was assuming HifiBerry DAC.
  
  The green light on the board is on.
  
  What next?
• 0
  
  HiFiBerry team October 16, 2014 09:11

  Dear itsikhefez,
  
  if our test image does not work, there might be a hardware problem with the board or the Raspberry Pi. Do you have another Raspberry Pi to test? Otherwise we need to test the board here. In this case please return the board to us, we will check it
  and replace it if it is defective.
  
  Best regards
  
  Daniel
  
• 0
  
  HiFiBerry team October 16, 2014 09:23

  Another idea: You could also test another power supply. We have seen rare cases with power supplies injecting voltage peaks during startup. Usually the hardware is quite robust against this, but in very rare cases this could result in the Digi not being recognized.
  
  Best regards
  Daniel
• 0
  
  itsikhefez October 16, 2014 09:25

  I do not have an additional RPi board.
  
  I will try with another PSU.
  If it does not work, where should I ship it to?
  
  Thanks,
  Itsik
• 0
  
  itsikhefez October 16, 2014 09:29

  I tried an additional PSU, it did not help
• 0
  
  HiFiBerry team October 16, 2014 10:39

  Please return it to
  
  Modul 9 GmbH
  Bachmattstr. 14
  CH-8932 Mettmenstetten
  
  Please note your order number on the return.
  
  Best regards
  Daniel