0

DAC2 Pro + DSP + Raspberry Pi OS DSP Fail After Reboot

kymok

March 03, 2021 13:52

None

Follow

Recently I bought the following models. It works just after the first installation, but no sound after rebooting.

Environment

• DAC2 Pro
• DSP
• Pi 4 2GB
• Raspberry Pi OS 2021-01-11-raspios-buster-armhf-lite
• DSP Profile: https://raw.githubusercontent.com/hifiberry/hifiberry-os/master/buildroot/package/dspprofiles/dsp-addon-96-13.xml
• shairport-sync

Problem

After rebooting, I could not install the DSP profile because following error was returned:

Failed to install DSP profile dsp-addon-96-13.xml

Disabling shairport-sync, sigmatcpserver, start sigmatcpserver manually, then install dsp profile yields following error log.

sudo /usr/local/bin/sigmatcpserver -v

[...]
DEBUG:root:writeXbytes 49152 1116
ERROR:root:exception during EEPROM write: [Errno 110] Connection timed out
ERROR:root:[Errno 110] Connection timed out
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/hifiberrydsp/server/sigmatcp.py", line 448, in write_eeprom_content
    SigmaTCPHandler.spi.write(addr, data)
  File "/usr/local/lib/python3.7/dist-packages/hifiberrydsp/hardware/spi.py", line 79, in write
    SpiHandler.spi.xfer(spi_request)
TimeoutError: [Errno 110] Connection timed out
DEBUG:root:Sending 1 bytes answer to client
DEBUG:root:finish

Executing "dsptoolkit reset" makes it possible to output sound from DAC, but still no DSP profile uploading is possible.

• Facebook
• Twitter
• LinkedIn

5 comments

• 0
  
  HiFiBerry team March 04, 2021 05:49

  Looks like something on your SPI isn't configured corrected. Either SPI is not enabled or you might have some other software running that blocks access to SPI.

• 0
  
  kymok March 04, 2021 06:25

  Thank you for your reply.

  After disabling shairport-sync and rebooting it's working. To get shairport-sync work together with dsptoolkit I added after=sigmatcp.service to /lib/systemd/system/shairport-sync.service. (Not tested this solution for a clean-installed image though)

• 0
  
  HiFiBerry team March 04, 2021 06:26

  In general, these should not affect each other. However, your shairport might be configured in a way that it reconfigured some GPIOs. You might have a look at the configuration.

• 0
  
  kymok March 04, 2021 06:33

  Sure, will look into the configuration when I have spare time. Thanks.

  For information, my configuration procedure for shairport was like below.

  apt-get install build-essential git xmltoman autoconf automake \
  libtool libpopt-dev libconfig-dev libasound2-dev avahi-daemon \
  libavahi-client-dev libssl-dev libsoxr-dev \
  libsndfile1-dev libglib2.0-dev

  $ git clone https://github.com/mikebrady/shairport-sync.git
  $ cd shairport-sync $ autoreconf -fi
  $ ./configure --sysconfdir=/etc --with-alsa --with-soxr \
   --with-avahi --with-ssl=openssl --with-systemd --with-convolution \
   --with-dbus-interface
  $ make
  $ sudo make install

  # /etc/shairport-sync.conf
  alsa = {
  mixer_control_name = "Digital";
  };

   

• 0
  
  kymok March 04, 2021 14:22

  Tried clean install with standard shairport-sync install procedure (below), and with it everything runs with no problem. Now the problem is very likely the configuration of shairport-sync.

  https://github.com/mikebrady/shairport-sync/blob/master/INSTALL.md

  Thank you for your time!