0

DIGI2 Pro not playing

Peter Bellamy

October 13, 2021 10:12

None

Follow

Just replaced my DIGI+ Pro with the DIGI2 version and I am getting no lock or output to my DAC. My setup is, RPI 3B, Volumio 2.915.

Volumio DAC setting is DIGI Pro and it is listed in config.sys

#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-digi-pro

however aplay -l doesn't seem to list it

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 H eadphones]
Subdevices: 3/3
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2

I wonder if it is faulty?

Any suggestions welcome!

• Facebook
• Twitter
• LinkedIn

51 comments

• 0
  
  Alan Simmons November 08, 2021 21:58

  I've got the same situation with RPi 4B, DIGI2Pro, and picoreplayer. Dysfunctional / intermittant hardware: out of several dozen boots, the device (sndrpihifiberry) has only been detected once. Otherwise, aplay doesn't list it.

  I'm going to purchase and try a 2nd RPi and a 2nd DIGI2Pro to try to determine where the problem is.

• 0
  
  Peter Bellamy November 09, 2021 18:46

  Changed to Volumio 3.129 but it has made not made it work, ALSA error and no digital output.

  But aplay -l does list it ??

   

• 0
  
  HiFiBerry team November 10, 2021 05:45

  Best way to test the hardware is HiFiBerryOS (https://www.hifiberry.com/os) on a new SD card (this is also important as we regularly see defective SD cards) It should automatically detect and use it. Also make sure, no other hardware is connected and the Digi is plugged  directly into the Pi, not connected via cables or other boards.
  If this doesn't work, there is some hardware issue - with the Pi, the Digi or the connection between both. Defective GPIOs on Pi's are quite common, therefore you should try another Pi if it doesn't work.

• 0
  
  Alan Simmons November 11, 2021 00:42

  Thanks for posting that testing idea. I'm now running HiFiBerryOS on the pi 4B with DIGI2Pro.

  aplay shows this:

  # 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

  I guess that's correct for the DIGI2 Pro? I'm playing flac files from a USB drive. Both COAX and TOSLINK are functioning. So my problem appears to be picoreplayer support for the DIGI2 Pro card.

• 0
  
  Alan Simmons November 11, 2021 00:53

  Using picoreplayer, all I ever see during boot is:

  Waiting for sound card sndrpihifiberry to populate...............
  .......................... Failed to find sndrpihifiberry... Done (42)

  and no devices are listed by aplay.

• 0
  
  HiFiBerry team November 11, 2021 07:28

  Something is very strange in your setup. If HiFiBerryOS lists the HiFiBerry DAC, the Digi was not detected, but you should also not get any sound output. 

• 0
  
  Alan Simmons November 11, 2021 17:25

  OS diagnostic page shows DIGI2 Pro:

  

• 0
  
  Alan Simmons November 12, 2021 00:12

  During boot of picoreplayer, this is reported in dmesg:

  [ 8.276311] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
  [ 8.303689] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
  [ 8.304503] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
  [ 8.308830] wm8804 1-003b: Failed to read device ID: -121
  [ 8.308980] wm8804: probe of 1-003b failed with error -121

  I've now tried PCP 6.1, 7.0, and 8.0, 32- and 64-bit. All with the same results.

• 0
  
  HiFiBerry team November 12, 2021 07:37

  Is this the same Pi and SD card that you used with HiFiBerryOS? While it looks like a hardware problem, the fact that it was working with HiFiBerryOS shows that the hardware is fine.

• 0
  
  Peter Bellamy November 12, 2021 13:59

  In attempt to solve this problem I have changed my setup to: PI 4B, Volumio 3.139, DIGI Pro, and a brand new microSD Card. but the same result, ALSA error.

  It seems this could be because Volumio is not getting the correct driver (my words, not sure of the technicalities). Other Volumio users are experiencing the same and the developers have asked us to ask DAC/DIGI suppliers to provide up to date information for their HATs. 

  I would be grateful if HiFiBerry would respond to that request and confirm their actions in this thread, thanks

  Volumio have provided the following information: https://developers.volumio.com/I2S%20DACs  

• 0
  
  HiFiBerry team November 12, 2021 14:05

  This isn't about Volumio, but piCorePlayer. It has nothing to do with the Volumio configuration in the Volumio UI.
  While we will look into the Volumio stuff, this has nothing to do with this problem.

• 0
  
  Alan Simmons November 12, 2021 20:14

  The PCP debug output is from the same Pi, different SD card, as with HiFiBerryOS. Is is possible there's a GPIO problem, and the two OSs use different pins to detect the HAT? I've got a second set of Pi+HAT on order so I can try with totally different hardware.

• 0
  
  Peter Bellamy November 15, 2021 15:56

  I see in the HiFiBerry blog it is suggested to add the line, force_eeprom_read=0, to the config.txt file

  Is this before or after the dtoverlay=hifiberry-digi-pro line?

   

• 0
  
  HiFiBerry team November 15, 2021 16:02

  Doesn't matter, but I don't think this will make a difference.

• 0
  
  Alan Simmons November 15, 2021 19:10

  OK, I've tried a new Pi 4B with the Digi2 Pro and various picoreplayer versions, and get the same results listed above - no soundcard detected during boot. Switched to an Allo Digione and everything works effortlessly with no config other than choosing the Digione HAT in PCP UI dropdown list. I get the impression the Digi2 Pro is not actually supported by picoreplayer on Pi 4B.

  *UPDATE* - Your power supply suggestion below was dead on. I was using a Nirvana PS (2.85A). When switched to a "standard" PS (3.5A), the Digi2 Pro works perfectly with picoreplayer.

  Thanks for the great support!

  Edited by Alan Simmons November 20, 2021 00:42
• 0
  
  HiFiBerry team November 16, 2021 07:22

  Sounds a bit strange as the Pi3 version seems to be working fine and as far as I know they are using only one version. 
  Next thing I would look at is the power supply. What are you using? Often so called "linear" power supplies have poor ramp-up characteristics. 

• 0
  
  Peter Bellamy November 19, 2021 09:32

  PI 3B and Volumio 3.139.(built on Buster)

  I have now tried all 3 of my DIGI cards. DIGI+ DIGI Pro and DIGI2.

  The oldest, DIGI+, works immediately with its Volumio I2S setting, the other two ALSA error.

  Volumio say they do not understand your piCorePlayer comment. I presume from that they don't use it?

  A couple of users have succeeded with a DIGI2 by not choosing the I2S switch in Volumio and just waiting for the driver name to appear and selecting that. It hasn't worked for me.

  As you can see I have spent a fair amount on DIGI products and not being able to get the recent ones working is extremely frustrating!

• 0
  
  HiFiBerry team November 19, 2021 10:41

  If both the Digi+ Pro and the Digi2 Pro are not working, there's a good chance that you're using an incorrect overlay.
  
  What overlay is used and what's the output of 
  
  aplay -l

   

• 0
  
  Peter Bellamy November 19, 2021 12:29

  DIGI+ Pro overlay. 

  Not listed with aplay -l

  aplay -l
  **** List of PLAYBACK Hardware Devices ****
  card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3

• 0
  
  HiFiBerry team November 19, 2021 14:58

  Please post the full /boot/config.txt file

• 0
  
  Peter Bellamy November 19, 2021 16:57

  initramfs volumio.initrd
  gpu_mem=32
  max_usb_current=1
  dtparam=audio=on
  audio_pwm_mode=2
  dtparam=i2c_arm=on
  disable_splash=1
  hdmi_force_hotplug=1

  include userconfig.txt

  #### Volumio i2s setting below: do not alter ####
  dtoverlay=hifiberry-digi-pro

• 0
  
  HiFiBerry team November 20, 2021 09:19

  Check the dmesg output:directly after booting:
  
  

  dmesg| grep hifiberry

  
  
  
  

• 0
  
  sheeple January 21, 2022 01:50

  I encountered a similar problem today.

  Digi2 on a Raspberry Pi 4 Model B Rev 1.5, powered by standard Pi4 power supply, no other connections other than SD card and Digi2.

  Using piCorePlayer 8.1.0, 64 Bit Kernel I think (check back later). At least in another diagnostics output I saved (dsmeg?), this is indicated:

  [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]
  [ 0.000000] Linux version 5.10.77-pcpCore-v8 (pCP@SoundStation) (aarch64-linux-gnu-gcc (crosstool-NG 1.24.0.351_511442b) 10.3.0, GNU ld (crosstool-NG 1.24.0.351_511442b) 2.34) #1 SMP PREEMPT Sat Nov 13 15:46:02 EST 2021

  I set the audio output to Hifiberry Digi+ Pro as commonly advised and squeezelite immediately stopped working after reboot. Then I began to search for explanations:

  This is pcp_boot.log:

  [ INFO ] pcp_boot.log

  Starting piCorePlayer v8.1.0 startup...
  Loading aes kernel modules for faster SSL... Done.
  Starting rngd using /dev/hwrng... Done.
  Checking for boot files on mmcblk0p1...
  Trying to mount /dev/mmcblk0p1.
  ssh file found on mmcblk0p1.
  newpcp.cfg not found on mmcblk0p1.
  Setting default piCorePlayer repository...
  Generating sound card drop-down list...
  Starting WiFi on wlan0...
  udhcpc: started, v1.34.1
  udhcpc: broadcasting discover
  udhcpc: broadcasting discover
  udhcpc: broadcasting discover
  udhcpc: broadcasting select for 192.168.178.48, server 192.168.178.1
  udhcpc: lease of 192.168.178.48 obtained from 192.168.178.1, lease time 864000
  deleting routers
  route: SIOCDELRT: No such process
  adding dns 192.168.178.1
  Starting WiFi... Done.
  Loading piCorePlayer configuration file... Done.
  Loading pcp-lms-functions... Done.
  Waiting for sound card sndrpihifiberry to populate......................................... Failed to find sndrpihifiberry... Done (42).
  Waiting for network. Done (1).
  Starting OpenSSH server... Done.
  Mounting USB Drives...
  Mounting USB Drive: dcf19a53-9d0a-44e7-92b6-2ae4089c815f...
  mount: /dev/mmcblk0p3 mounted on /mnt/data.
  Disk Mounted at /mnt/data.
  Done.
  Waiting for valid date before starting LMS... Done. (0)
  Starting LMS, this can take some time...[22-01-20 12:00:40.1857] main::init (390) Starting Logitech Media Server (v8.2.0, 1627922070, Tue Aug 3 11:43:18 CEST 2021) perl 5.032001 - aarch64-linux-thread-multi

  Slimserver Running pid:9011
  Done.
  Waiting for LMS to initiate... Done (3).
  Starting Squeezelite and/or Shairport-sync... Done.
  Starting httpd web server... Done.
  Starting to advertise pcp.local... Done.
  Setting CPU scaling governor to ondemand... Done.
  Creating static footer... Done.

  Finished piCorePlayer v8.1.0 startup.

  To setup piCorePlayer, use the web interface via a browser:
  - http://192.168.178.48 (wlan0)
  - http://pcp.local (mdnsd)

  Press [Enter] to access console.

  In the background, ntpd is syncing time between piCorePlayer and the internet.
  A large offset between 1970 and now is normal.

  After this, I installed HifiberryOS and after connecting to the device via Ethernet, I was presented with a "Beocreate" surface where I could choose which speaker to amplify.

  I am open to use more images to properly diagnose.

• 0
  
  sheeple January 21, 2022 15:30

  Today I tried pICorePlayer ver. 6.1, 7, 8, 8.1 all in 32 Bit Kernel, after using 64 Bit Kernel yesterday with ver 8.1.

  I could not connect to piCorePlayer versions 6.1 and 7 over Ethernet and had no patience to troubleshoot the reason why it was not active. The versions 8 and 8.1 do all show squeezelite not running, they do not detect the board. With 8.1 I once added force_eeprom_read=0 to the config.txt but this did not change a thing.

• 0
  
  sheeple January 21, 2022 20:31

  I went to the submenu "HAT information" and this baffles me: although piCorePlayer cannot start it, there is information in that it is indeed a Digi2 Pro, how comes this?

   

  HAT information name hat product Digi2 Pro product_id 0x0000 product_ver 0x0000 uuid 5af941bb-4dcf-4eac-82a8-e36e84fcabef vendor HiFiBerry DATA: "hat", "Digi2 Pro", "0x0000", "0x0000", "5af941bb-4dcf-4eac-82a8-e36e84fcabef", "HiFiBerry",

  dmesg | grep soc:sound [ INFO ] dmesg

  Overlays in /mnt/mmcblk0p1/config.txt [ INFO ] Overlays dtoverlay=disable-bt dtoverlay=hifiberry-digi-pro

• 0
  
  Kevpar66 January 28, 2022 17:06

  I'm having the same issues in Picoreplayer with a 4b, standard PS. The 'hat information' shows that the digi2 pro is being recognized but squeezelite can't start it.

  Edit: I have fished around and think I have a somewhat logical answer. You can choose the 'ESS9023 DAC' as your output and squeezlite will run. These dacs seem to have a I2S sound port that the digi2 pro also happens to have. So I think the picoreplayer people have just designated all hats like this here

  Edited by Kevpar66 January 28, 2022 17:25
• 0
  
  sheeple January 28, 2022 17:40

  This is interesting, but sadly I already returned the article. Now I have to see what the vendor is going to say. My troubleshooting log is available at the slimdevices forum "Linux/Unix -> HifiBerry Digi2 Pro" thread

  Edited by sheeple January 28, 2022 17:40
• 0
  
  Kevpar66 January 29, 2022 00:47

  not working either unfortunately, this seems really odd

• 0
  
  sheeple February 10, 2022 11:46

  After returning my Digi2 Pro to the vendor, today I have received the previous version Digi+ Pro. The downgrade was intentional to avoid incompatibility issues, which I assumed where causing the behavior of the Digi2. Yet, the Digi+ Pro is not recognized by piCorePlayer either, it will not start squeezelite. I can run the whole set of diagnostics that I did on the Digi2 again and which I have documented under the following link https://forums.slimdevices.com/showthread.php?115381-HifiBerry-Digi2-Pro&p=1044692&viewfull=1#post1044692
  But to me the serious question arises and which I want to see a reply to, whether the HiFiBerry boards are incompatible with some Raspberries, in my case the Pi4b 2GB. This is a real problem. I bought a case, the computer and accessories for about 70 Euros which cannot be returned anymore. I need to get this working on the machine and want to get statements on what is going on.

• 0
  
  HiFiBerry team February 10, 2022 11:49

  There are no known incompatibilities to the Pi4. We have this running here without problems. My best guess is that your Pi is causing the problem, not the Digi. However, that's the best "statement" I can give you. I can offer that you send the Pi and the Digi to us for a check. If you want to do this, contact us at support@hifiberry.com