Pi3 and DAC+ Pro

jimmeuh

Hi All

First I wanna thank you guys for this awesome looking software!

I'm experimenting with my brand new Pi3 and DAC+ Pro board.
Wanting not to pollute the main Pi3 thread to much with this issue a seperated thread, as it seems a DAC+ Pro problem.

Besides the more common wireless problems more people are experiencing i'm also having an audio issue.
The music coming out of the RCA is really disturbed (read : noise). The strange thing is when I'm skip forward in a track, it sometimes gets ok.

I'm using the test image from Frank (thanks!).

/boot/config.txt :
dtparam=i2c_arm=on
dtparam=i2s=on
dtoverlay=hifiberry-dacplus
dtoverlay=pi3-disable-bt

Based on:
https://support.hifiberry.com/hc/en-us/community/posts/207234405-RPi3-and-DAC-Pro-Linux-not-working-Working-on-a-fix-
#2954

# uname -a
Linux runeaudio 4.1.18-v7+ #846 SMP Thu Feb 25 14:22:53 GMT 2016 armv7l GNU/Linux

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

After this I was able to choose the "HifiBerry Dac+ I2c" option in the MPD settings in the UI.
I've added the disable bluetooth option to try and prevent the noise, but that didn't help.

Any ideas?

Greatly appreciated

(If I can help debug the wifi issue, let me know what I can test - it appeared after I enabled the DAC settings in my setup)

hondagx35

dtparam=i2c_arm=on
dtparam=i2s=on

No need for this settings.

As i do not own a DAC + pro i can not help at the moment, sorry.

Frank

jimmeuh

No problem Frank.

I'll try to delete those settings (I think i've tried already though)
Keep u posted If I find a solution.

jimmeuh

On the Hifiberry forum, they seem to have found a solution:

https://support.hifiberry.com/hc/en-us/community/posts/207256895-Fix-for-DAC-Pro-on-RPi3-disable-bluetooth

Is it possible to test it on my Runeaudio setup?

hondagx35

Hi,

see also here.

Is it possible to test it on my Runeaudio setup?

Yes, you have to add this:

dtoverlay=pi3-disable-bt

to your /boot/config.txt

Frank

jimmeuh

Hi Frank

Yes I know I've tried to disable the BT.
But they seem to have a updated kernel now, with a fix for the issue.
See the github links in the post:

https://github.com/raspberrypi/linux/pull/1340
https://github.com/raspberrypi/linux/issues/1321

ingohz

You may try

pacman -Sy --force raspberrypi-firmware-bootloader linux-raspberrypi

This updates to the latest kernel/firmware, but could result in other problems.

jimmeuh

I've removed those first:

dtparam=i2c_arm=on
dtparam=i2s=on

reboot -> no difference

I've tried the update

pacman -Sy --force raspberrypi-firmware-bootloader linux-raspberrypi

reboot ->..... yeah! it works

Thanks for the great support!

jimmeuh

Been playing some with the software which now works great!

Next issue to tackle.. the wifi issue.

I can setup a wifi connection fine. The PI3 is available afterwards through the wifi connection. No problems at all...
Until I reboot the PI. The wireless interface won't respond anymore. I need to delete the wireless profile, add it again, and then works fine again.

I've tried the fix for the power issue from Frank:

cd /srv/http
git stash
git pull

But no difference.

A problem with the combination of the DAC?

Looking in the debug log:

Network interfaces:

3: wlan0:  mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000
    link/ether b8:27:eb:4d:d9:f8 brd ff:ff:ff:ff:ff:ff

Dmesg:

[    7.393567] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[    7.393580] brcmfmac: brcmf_add_if: ignore IF event
[    7.397469] brcmfmac: power management disabled

Thanks again...

hondagx35

Hi jimmeuh,

i have the same error message, but my wifi works.
I did a web search for this error, but couldn't find a solution / fix.

The build in wifi isn't great at all.
Please try to move your Pi, maybe the signal strength is not good enough.

Frank

Superkikim

Hi,

I also have the wifi issue with RPI3 and HiFiBerry DAC+Pro.

Wifi on RPI3 works fine. At least as long as the HiFiBerry DAC+Pro is not powered up. It is very stable, and latency is fine. The problem only appears when the DAC is powered up. I'm not equiped to test the power fluctuations on the RPI, I don't know if it's a problem of power, or a bug/conflict between HIFiberry DAC+Pro and integreated WIFI.

My power supply is "official" 2.5A PSU. I tried with a 2.1A PSU as well, and with a 2.1A output powerbank, all with the same result.

jimmeuh

@[deleted]:
Wifi reception is fine.

@[deleted]
Thanks for your reply.
Are you using RuneAudio as well? If not, it's clearly an issue with the hardware and we should probably discuss this further with the guys from Hifiberry:

https://support.hifiberry.com/hc/en-us/community/posts/207234405-RPi3-and-DAC-Pro-Linux-not-working-Working-on-a-fix-

Superkikim

Nope. I've been trying Raspbian Lite, and Archi Linux. Same issue with both.

hondagx35

Hi all,

a new image is on the way.

The problems with "HiFiBerry DAC+Pro" should be fixed with it.

Frank

hondagx35

Hi all,

a new image is on the way.

see here.

Frank

jimmeuh

Thanks Frank! Will try this evening.

jimmeuh

I'm just testing the new image.
The Hifiberry DAC+ Pro now works out of the box. Thanks!

Wifi still has issues though.
Will need to test further but something very strange is happening:

1) Everything online: LAN connected, wifi connected. Music is playing fine.
2) start 2 continous ping tests to the 2 ip addresses. no drops nor timeouts
3) I login with SSH to the wifi interface and issue a reboot command
4) the ping to the LAN IP address stops immediatly
5) after +-5 minutes the wifi connection drops (why does this takes so long?)
6) after a minute or so the LAN connection is back
7) wifi stays out
8) I go to the Rune UI through the LAN connection and browse to the mpd settings page...
9) pings to the wifi connection are back

Afterwards I play some tracks, and the pings keep running to both interfaces.
Only playback stops all of a sudden. UI gets unresponsive and I have to issue a reboot command again.

Sorry

hondagx35

Hi jimmeuh,

with the current implementation it is not possible to use both connections at the same time.
Having both up at the same time on the same network could be confusing because both IP's would answer on both interfaces and applications may not know which IP to bind to or which interface to route through.
It even gets worse with the use of avahi (http://runeaudio) because it will respond on both interfaces.

This may change in the future, but at the moment you only should use ethernet or wifi but not both.

Frank

jimmeuh

Frank:

When I boot the PI with the LAN cable disconnected, the wifi won't turn up.

When I connect the LAN cable, I can go to the UI (mpd settings) and the wifi gets active.
So it's not possible to only use the wifi connection at this moment.

hondagx35

Hi jimmeuh,

booting with ethernet disconnected works for me without issues.
So it is not a general problem!

: wifi.png (48.88 KiB) Viewed 2405 times

- Is your wifi connection configured via UI or manually?
- static IP or DHCP?
- you are connected to the same router with ethernet and wifi?

Please post your debug data.

Here are the steps i did:
- downloaded latest image.
- copied it to my sd card
- connected all cables and usb devices
- booted the Pi
- figured out the IP address (router)
- connected via browser to my device
- navigated to menu->network

selected the wlan0

- after the scan has finished i clicked on the SSID i want connect to

- entered all necessary data

- saved the profile

after a few seconds the scan shows that i'm connected

- connected via browser to my device (using the wlan0 IP)
- pulled the ethernet cable
- rebooted via menu->Turn off

And my Pi comes up with wifi connection.
Then i plug in the ethernet cable my Pi activates eth0 and gets an IP.
I can do all this with DHCP or static IP.

Frank