0

Can't get Raspberry Pi 4B to detect DAC+ ADC

Randolf Eshu

July 01, 2024 21:14

None

Follow

Hello, I have been trying to use an DAC+ ADC with a Raspberry Pi 4B, and while previously the computer had been detecting the HAT, this is suddenly not the case (I think I may have updated something). I have I2C enabled via raspi-config and have added all the suggested lines to my config.txt file that were recommended on the website, but nothing so far has worked.

Below is my config.txt file. I have tried many iterations of this and am running out of configurations to try. Does anyone know why this might not work?

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=spi=on

# Additional overlays and parameters are documented
# /boot/firmware/overlays/README

# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Automatically load initramfs files, if found
auto_initramfs=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d,noaudio
max_framebuffers=2

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Disable compensation for displays with overscan
disable_overscan=1

# Run as fast as firmware / board allows
arm_boost=1

# Disable the onboard EEPROM
force_eeprom_read=0

[all]

# Enable HiFiBerry DAC+ADC HAT
dtoverlay=hifiberry-dacplusadc

• Facebook
• Twitter
• LinkedIn

7 comments

• 0
  
  HiFiBerry team July 02, 2024 07:29

  Common problems are SD card corruption or incorrect updates. If this was working fine before, I recommend to try a fresh installation on a new SD card.

• 0
  
  Randolf Eshu July 02, 2024 17:06

  I reimaged the SD card but the Raspberry Pi still can't detect any I2C interface. I've tried loading the hifiberry-dacplusadc dtoverlay manually as well as followed all the instructions on the Configuration changes in Linux 5.4 page as well as many other troubleshooting steps but nothing so far has made a difference. Last time I had this problem it was only fixed by replacing the first HiFiBerry HAT I'd bought with another, which made me think that the first one had a manufacturing defect, so I'm worried that somehow this one has bricked as well.

• 0
  
  HiFiBerry team July 03, 2024 06:28

  It could be also a problem of the Pi. While defective GPIOs are rare, but we see these regularly. If you have another Pi, try it.

• 0
  
  Randolf Eshu July 09, 2024 21:59

  I ordered a different SD card and that didn't fix the problem. I have also tried with a different Pi this also didn't make a difference. Is there some other step I need to take?

• 0
  
  HiFiBerry team July 10, 2024 06:00

  One thing you can do is to boot HiFiBerryOS (https://hifiberry.com/os) and check what sound card is detected. This will help figuring if it's a hardware or software issue.

• 0
  
  Randolf Eshu July 10, 2024 20:41

  I reflashed the SD card and it does appear to pick up the HAT. I went to system diagnostics to check for the sound card and I got the following information:

  HiFiBerryOS Version: 20230404

  Pi type: 4

  Pi model: Raspberry Pi 4 Model B Rev 1,5

  Compatibility: No known problems

  Sound card: DAC+ Zero/Light/MiniAmp

  Sound card ID: 0

  aplay 1: card 0 sndrpihifiberry [snd_rpi_hifiberry_dac]

  aplay 2: device 0 HifiBerry DAC HiFi pcm5102a-hifi-O [HifiBerry DAC HiFi pcm5102a-hifi-0]

  Mixer: Softvol

  Features: pi localui bluetooth pisorlater arm7

  Power controller: not detected

  Linux version: Linux hifiberry 5.15.78-v71 #1 SMP Mon Apr 3 20:04:51 UTC 2023 armv7| GNU/Linu

  Date and time: Tue Oct 12 15:33:31 UTC 2021

  /data mounted: OK

  /dev/dri/cardO: OK

  BT devices: hcio - Cypress Semiconductor (305)

  WiFi devices: wlano

   

  I also got the config.txt from the , which was as follows:

  # Please note that this is only a sample, we recommend you to change it to fit
  # your needs.
  # You should override this file using a post-build script.
  # See http://buildroot.org/manual.html#rootfs-custom
  # and http://elinux.org/RPiconfig for a description of config.txt syntax
  
  # We always use the same names, the real used variant is selected by
  # BR2_PACKAGE_RPI_FIRMWARE_{DEFAULT,X,CD} choice
  start_file=start.elf
  fixup_file=fixup.dat
  
  kernel=zImage
  
  # To use an external initramfs file
  #initramfs rootfs.cpio.gz
  
  # Disable overscan assuming the display supports displaying the full resolution
  # If the text shown on the screen disappears off the edge, comment this out
  disable_overscan=1
  
  # How much memory in MB to assign to the GPU on Pi models having
  # 256, 512 or 1024 MB total memory
  gpu_mem_256=100
  gpu_mem_512=100
  gpu_mem_1024=100
  # Enable I2C and SPI
  dtparam=i2c=on
  dtparam=spi=on
  dtoverlay=i2c-gpio,i2c_gpio_sda=0,i2c_gpio_scl=1
  dtoverlay=vc4-fkms-v3d,audio=off
  dtoverlay=hifiberry-dac

  When I went to the console and used i2c detect, it didn't detect anything. It also didn't detect anything when I used arecord -l. aplay -l did pick up on the hat, though.

  Is there any information in here that would affect how I should set up the HiFiBerry on the Raspbian OS, or that would indicate whether this is a hardware or software issue? I found it unusual that the HAT is listed as the hifiberry-dac instead of the hifiberry-dacplusadc.

  Some more information: I went back to the standard Raspbian OS and added "dtdebug=1" to config.txt, rebooted, and ran dmesg, and got the following errors:

  [    9.055295] i2c-bcm2835 fe804000.i2c: i2c transfer timed out
  [    9.055340] pcm512x 1-004d: Failed to reset device: -110

  Let me know if any of this information helps elucidate what the problem is.

  Edited by Randolf Eshu July 10, 2024 23:14
• 0
  
  HiFiBerry team July 11, 2024 04:07

  This show that the DAC isn't detected. Looks like a hardware problem. Either wit the Oi, the DAC or the connection between both. If you tested with multiple Pi's alsready, there is a good chance that there's a hardware problem with the DAC.