0

Fix: Digi+ Standard not playing at correct speed

HiFiBerry team

January 28, 2020 07:04

None

Follow

Some HiFiBerry Digi+ have been shipped with incorrect product identification in the onboard EEPROM. In this case, the card will use the wrong driver and playback speed will be incorrect (too fast).

You will notice this when running the command aplay -l:

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HiFiBerry Digi+ Pro HiFi wm8804-spdif-0 [HiFiBerry Digi+ Pro HiFi wm8804-spdif-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

You will see that it says "Digi+ Pro". In this case, it's using the wrong driver. To fix this, there are 2 ways:

Load the correct overlay "by hand".

Modify the file /boot/config.txt and add the following 2 lines:

force_eeprom_read=0
dtoverlay=hifiberry-digi

And reboot.

Flash the EEPROM with the correct data

Boot HiFiBerryOS. Make sure, you're using at least version 20200127:

Now enable SSH:

Login via SSH with username root and the password you selected.

Run the command

/opt/hifiberry/contrib/flash.sh digiplus

The software needs to change some settings to prepare for the flash process and will reboot. Login again and run the same command again.

You should now see the following:

# /opt/hifiberry/contrib/flash.sh digiplus
This script comes with ABSOLUTELY no warranty. Continue only if you know what you are doing.
Writing...
2+1 records in
2+1 records out
Done.
Cleaning up /boot/config.txt again
Rebooting in 5 seconds

That's it. You have sucessfully flashed the EEPROM on the board

Result

Both versions work equally well. If you don't want to re-flash the EEPROM, that's fine. 
The correct result now looks like this:

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HifiBerry Digi HiFi wm8804-spdif-0 [HifiBerry Digi HiFi wm8804-spdif-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

• Facebook
• Twitter
• LinkedIn

12 comments

• 0
  
  Sean Dowling April 18, 2020 21:06

  This guide is either completely out-of-date, or incomplete, because I can't make any of this work.

  This command "/opt/hifiberry/contrib/flash.sh digiplus" does nothing with the following errors:

  Need to modify config.txt and reboot
  /opt/hifiberry/contrib/flash.sh: line 7: /boot/config.txt: Read-only file system
  /opt/hifiberry/contrib/flash.sh: line 8: /boot/config.txt: Read-only file system
  /opt/hifiberry/contrib/flash.sh: line 9: /boot/config.txt: Read-only file system
  Rebooting in 5 seconds

  The first method has the same issue as its a read-only FS. I realize for some folks, working with Linux based stuff and making things readable is 2nd nature, but for the rest of us, can someone please update this to have all the steps necessary? I've had to do this stupid fix like 5 times now, each several weeks apart and have to solve all the same problems each time I flash the SDcard. Needless to say...a giant PITA.

   

   

• 1
  
  HiFiBerry team April 19, 2020 05:09

  Run the command "mount -o remount,rw /boot" before starting the "flash.sh" command.
  
  This is a one-time fix. If you did it already 5 times, there's something else wrong in your setup. Are you using it with HiFiBerryOS or with another distribution?

• 0
  
  Sean Dowling April 19, 2020 07:45

  I'm using latest HiFiBerry OS. PuTTY output:

   

  # aplay -l
  **** List of PLAYBACK Hardware Devices ****
  card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HiFiBerry Digi+ Pro HiFi wm8804-spdif-0 [HiFiBerry Digi+ Pro HiFi wm8804-spdif-0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  # /opt/hifiberry/contrib/flash.sh digiplus
  This script comes with ABSOLUTELY no warranty. Continue only if you know what you are doing.
  /opt/hifiberry/contrib/hbflash.sh: line 95: /sys/class/i2c-adapter/i2c-3/new_device: No such file or directory
  Writing...
  dd: failed to open '/sys/class/i2c-adapter/i2c-3/3-0050/eeprom': No such file or directory
  Error doing I/O operation.

• 1
  
  HiFiBerry team April 19, 2020 16:29

  Unfortunately I can't say why the flash isn't working here. Easiest workaround is
  
  mount -o remount,rw /boot
  
  Then add the following lines to /boot/config.txt:
  
  

  force_eeprom_read=0
  dtoverlay=hifiberry-digi

   

• 0
  
  Sean Dowling April 21, 2020 01:48

  This has definitely not been a one-time fix for me. Every time I flash a stock HiFiBerry image onto an SD card, I have to do this fix, otherwise it sounds like Alvin & the Chipmunks.

  In my latest attempt, I took a brand new 32GB SD Card, flashed with the May 3 release for RasPi 4. Enabled remote through the web interface (wired LAN), and then issued the following sequence:

  1) Open PuTTY, login as root
  2) # mount -o remount,rw /boot
  3) # /opt/hifiberry/contrib/flash.sh digiplus
  4) system reboots
  5) Open PuTTY, login as root
  6) #/opt/hifiberry/contrib/flash.sh digiplus

  results in output:

  This script comes with ABSOLUTELY no warranty. Continue only if you know what you are doing.
  /opt/hifiberry/contrib/hbflash.sh: line 95: /sys/class/i2cadapter/i2c-3/new_device: No such file or directory
  Writing...
  dd: failed to open '/sys/class/i2c-adapter/i2c-3/3-0050/eeprom': No such file or directory
  Error doing I/O operation.

  I've manually edited boot config as the guide suggests, and that does fix things (once you find out how to make things readable), but as soon as I reflash the SD Card with stock HiFiBerry image, I'm back to square one, as shown below:

  # aplay -l
  **** List of PLAYBACK Hardware Devices ****
  card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HiFiBerry Digi+ Pro HiFi wm8804-spdif-0 [HiFiBerry Digi+ Pro HiFi wm8804-spdif-0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  OK, so now:

  1) Can someone from the HiFiBerry team please update this guide with steps that work for the latest HiFiBerry image on RasPi 4?
  2) Is there a permanent fix to this setup so that I don't have to keep doing this every time I reflash an SD card? Does the board need to be replaced?

• 1
  
  HiFiBerry team April 21, 2020 04:54

  Unfortunately I can't say why this isn't working in your setup. I think that best is to send us the board and we'll update it here. This might also help us to find out why this isn't working for you.

  BTW: Why do you re-flash your SD card so often?

• 0
  
  Sean Dowling April 21, 2020 22:56

  Sounds good, will initiate an RMA for the board, thanks for the help so-far.

  As for why I'm flashing the SD card so often...bit of a long story, but in short, I had two SD cards available when I got the kit, both were fairly old. I started off with HiFiBerry OS, but it would sometimes die (and also had the playback speed issue), and I would re-flash it to bring it back to life. Also, tried RoPieee to see if that would be more stable (it was, but in hindsight, I don't think its OS related). Bounced around between cards and distros over the last few months, until ultimately concluding the cards are on the way out. Ordered two new, high endurance cards and have flashed HiFiBerry on one, RoPieee on the other. So, in total since January, I've had to "fix" this issue many times, and just long enough between to forget the steps...frustration ensues.

• 0
  
  Sean Dowling May 05, 2020 03:25

  Hi again...

  Still trying to debug this thing. I'm confused as to why you think this issue is related to the board...and not the HiFiBerry image? The errors I'm getting now are simply related to the fact that the OS is in Read-Only mode (I can't simply edit config.txt from SSH). Issuing "mount -o remount,rw /boot" before the first issue of "/opt/hifiberry/contrib/flash.sh digiplus", helps get to the second step, but the second issue of this command ends with this error:

  # /opt/hifiberry/contrib/flash.sh digiplus
  This script comes with ABSOLUTELY no warranty. Continue only if you know what you are doing.
  /opt/hifiberry/contrib/hbflash.sh: line 95: /sys/class/i2c-adapter/i2c-3/new_device: No such file or directory
  Writing...
  dd: failed to open '/sys/class/i2c-adapter/i2c-3/3-0050/eeprom': No such file or directory
  Error doing I/O operation.

  Which tells me the script simply cannot find the required files in that location of the file system. I looked...they're definitely not there. The only directories there are i2c-1 and i2c-7, no sign of i2c-3.

  So...is this something that is missing from the image? Any other thoughts on how I can fix this?

• 0
  
  HiFiBerry team May 05, 2020 04:44

  /sys is a pseudo-filesystem: http://man7.org/linux/man-pages/man5/sysfs.5.html
  
  There are no files there.

• 0
  
  Sean Dowling May 05, 2020 05:44

  In case you couldn't tell, I'm not a Linux programmer...but good info, and thanks.

  Scanning the content is informative on pseudo-filesystems, but it was not immediately clear how that helps this issue?

  Can I alter some script to point to somewhere else that has the info its looking for? If so, what script, and where do I point it to? I'm guessing the i2c-3 did not show up because the Digi+ board is misrepresenting itself as a Digi+ Pro?

  Is there someway to fundamentally fix how the board presents itself? Is there some f/w on board the hat I can update through serial console or something?

  I'm also still confused as to how the above instructions have worked for anyone in my position. Can anyone confirm a sequence of commands using SSH to a Raspi 4 (and the latest HiFiBerry OS) that lets me manually edit /boot/config.txt? I can forego the script sequence at this point.

  I can do this no problem using RoPieeeXL and have a different identical SD card working perfectly for that distro, but for the life of me, I can't get the HiFiBerry OS to let me edit /boot/config.txt.

• 0
  
  HiFiBerry team May 05, 2020 05:48

  As I said 2 weeks ago, I can't say why the flashing not working in your setup. Therefore I recommended to send the board to us. 

  To edit /boot/config.txt by hand, you need to make the file system read-writable first:
  mount -o remount,rw /boot
  
  However, this won't fix the flashing problem. Please send the board to us and we'll have a look.

• 0
  
  AdReD June 24, 2020 06:48

  I have a simple solilution. I had the same problem with HiFi digi + Pro. In the settings of Volumioo DAC model, I set HiFiBerry DiGi. The speed of music came back to normal.