0

Pi 5 compatibility question for all cards

Hans van Zutphen

February 26, 2024 22:27

None

Follow

Hi, we have a software image with our software, that supports all the different HifiBerry cards. Users can select which card they have, and our software then updates the dtoverlay= setting in /boot/config.txt (now /boot/firmware/config.txt) and reboots.

This works fine on a Pi 3 or 4, but not on a Pi 5. I managed to get my own card (HifiBerry DAC+ADC, NOT Pro) to work by adding ",slave" after it, as described here: https://www.hifiberry.com/blog/dac-pro-dac2-pro-dac-adc-pro-on-pi5/ . That blog post says that this is needed for Pro cards specifically, but mine is not a Pro card. Without the ,slave the card isn't detected (error -22 on startup).

Since I don't have all the diffrent cards, I cannot test which of the cards would need a ",slave" and which wouldn't. I can add a check if we're running on a Pi 5 and then always add it, but I don't know if that breaks the behavior for other cards.

So I would like to know how to handle this, until the new drivers are available.

• Facebook
• Twitter
• LinkedIn

5 comments

• 0
  
  HiFiBerry team February 27, 2024 20:40

  The .slave isn't necessary. Just make sure, EEPROM usage is disabled:
  
  

  force_eeprom_read=0

• 0
  
  Hans van Zutphen February 28, 2024 09:54

  I tried, but it doesn't work. Here are some test cases:

  eeprom_read=0, no slave

  dtdebug=1
  force_eeprom_read=0
  dtoverlay=hifiberry-dacplusadc

  Fails, aplay -l shows no sound cards, dmesg -S output:

  [    8.523331] designware-i2s 1f000a4000.i2s: ASoC: error at snd_soc_dai_set_fmt on 1f000a4000.i2s: -22
  [    8.523529] snd-rpi-hifiberry-dacplusadc soc:sound: snd_soc_register_card() failed: -22
  [    8.523534] snd-rpi-hifiberry-dacplusadc: probe of soc:sound failed with error -22

   

  eeprom_read=0, with slave

  dtdebug=1
  force_eeprom_read=0
  dtoverlay=hifiberry-dacplusadc,slave

  aplay -l output:

  **** List of PLAYBACK Hardware Devices ****
  card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplusadc], device 0: HiFiBerry DAC+ADC HiFi multicodec-0 [HiFiBerry DAC+ADC HiFi multicodec-0]
    Subdevices: 0/1
    Subdevice #0: subdevice #0

   

  No eeprom_read=0, with slave

  dtdebug=1
  #force_eeprom_read=0
  dtoverlay=hifiberry-dacplusadc,slave

  aplay -l output:

  **** List of PLAYBACK Hardware Devices ****
  card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplusadc], device 0: HiFiBerry DAC+ADC HiFi multicodec-0 [HiFiBerry DAC+ADC HiFi multicodec-0]
    Subdevices: 0/1
    Subdevice #0: subdevice #0

   

  So the force_eeprom_read appears to have no effect, and it only works with ",slave".

  Edited by Hans van Zutphen February 28, 2024 09:56
• 0
  
  HiFiBerry team February 29, 2024 05:35

  According to this the driver is loaded in both cases.

• 0
  
  Hans van Zutphen February 29, 2024 13:36

  In both cases with ,slave, yes. But not with only force_eeprom_read=0.

• 0
  
  HiFiBerry team March 01, 2024 12:53

  Looks like this now happens with the standard cards (not Pro). I couldn't test it with many cards, but I would expect it to be a problem with the DAC+ Standard, Amp2, Amp4 and DAC+ ADC
  We need to have another look into this to finally fix it for all cards.