RPI B+ and Hifiberry DAC+ -- anybody??

[soundcheck]

Hi folks.

I'm trying to get a Hifiberry DAC+ on a 3.12.28 resp. 3.16.3-1-ARCH going.

I don't manage to get it running.

The required Hifiberry kernel modules can be loaded. And that's about it. The system (Alsa) won't recognize the device.

Raspbian works out of the box.

Anybody around who made that Hifiberry module work??

Does Arch use the same kernel sources as Raspbian?


Unfortunately: The Hifiberry support refuses to support Arch btw.

Thx

[pepedog]

Looks like the Hifiberry people may be wankers?
Yes, we share same kernel source, config may.differ

[soundcheck]

Hi.

I did have a brief conversation with them:

http://www.hifiberry.com/forums/topic/h ... t-working/

The documentation is all but reliable.
It took quite a while to figure out what modules are needed and that modules were renamed in most current kernels.
I'm still not sure if my setup is correct. They even refuse to post their lsmod output.

I'd better stayed with an USB DAC.

Anyway. Now I have it here. I'll keep trying. The module is nicely made, price is OK.

[moonman]

Compare the modules loaded on rasbian vs arch.

The support is compiled in (as you mentioned the module is there) https://github.com/archlinuxarm/PKGBUIL ... nfig#L2830

This is their commit to rpi kernel https://github.com/raspberrypi/linux/co ... 2c078347bc

We usually have to go and check what they enable/disable using their git logs. Maybe increasing kernel loglevel will give you more info.

[soundcheck]

I just have the menuconfig of the 3.16-arch open:

CONFIG_SND_BCM2708_SOC_HIFIBERRY_DACPLUS:
Selects: SND_SOC_PCM512x =m

There is no such module.

I do find:

SND_SOC_PCM512x_I2C ||
SND_SOC_PCM512x_SPI

Hmmh.

[moonman]

https://github.com/archlinuxarm/PKGBUIL ... nfig#L2839

[soundcheck]

Yep. THX.

Just made it one step further down the road, after looking up all the related module dependencies in the kernel.

Result:

/etc/modules-load.d/raspberrypi.conf
snd_soc_hifiberry_dacplus

/etc/modprobe.d/modules.conf
blacklist snd_soc_wm8804
blacklist snd_soc_tas5713

That's it.

I'm running Linux archie 3.16.3-1-ARCH

My lsmod looks like:

$this->bbcode_second_pass_code('', '
[root@archie ~]# lsmod
Module Size Used by
snd_soc_pcm512x_i2c 1933 1
snd_soc_pcm512x 8142 1 snd_soc_pcm512x_i2c
regmap_i2c 2554 1 snd_soc_pcm512x_i2c
spi_bcm2708 5458 0
snd_soc_bcm2708_i2s 6182 2
i2c_bcm2708 5468 0
regmap_mmio 3270 1 snd_soc_bcm2708_i2s
snd_soc_hifiberry_dacplus 2469 0
snd_soc_core 155635 3 snd_soc_pcm512x,snd_soc_hifiberry_dacplus,snd_soc_bcm2708_i2s
snd_compress 8109 1 snd_soc_core
snd_pcm_dmaengine 5443 1 snd_soc_core
snd_pcm 85710 2 snd_soc_core,snd_pcm_dmaengine
snd_timer 20710 1 snd_pcm
snd 61424 4 snd_soc_core,snd_timer,snd_pcm,snd_compress

')


Playback of 16/44.1 is working now.

$this->bbcode_second_pass_code('', '
aplay -D plughw:0,0 -r 44100 -c 2 -f S16_LE test16.wav
')

HOWEVER:

24/44.1 is causing a dump and knocks the DAC+ module hard off (LED turns off)

$this->bbcode_second_pass_code('', '
root@archie ~]# aplay -D plughw:0,0 -r 44100 -c 2 -f S24_3LE test24.wav
Playing WAVE ‘test.wav’ : Signed 24 bit Little Endian in 3bytes, Rate 44100 Hz, Stereo
aplay: set_params:1297: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S24_3LE
SUBFORMAT: STD
SAMPLE_BITS: 24
FRAME_BITS: 48
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (125011 125012)
PERIOD_SIZE: 5513
PERIOD_BYTES: 33078
PERIODS: 4
BUFFER_TIME: (500045 500046)
BUFFER_SIZE: 22052
BUFFER_BYTES: 132312
TICK_TIME: 0

')

Beside that there are some - non documented - weired Alsa controls to be looked at with Alsamixer.
E.g. "Playback Digital" needs to be enabled to get sound on the anlog output (The PCM5102 chip also
offers a digital SPDIF output.) .

I'll keep digging.

Cheers

[soundcheck]

Hi there.

Today - better late then never - I learned that the current driver does not support 24bit. Just 16 and 32bit.
No word about those weired Alsamixer controls. There are some apps that might work. Others - even basic aplay - won't.

They say, they are working on it.

Hmmh. That's one of the major issues with custom drivers and small companies.
If they manage to get things working properly one day -- if that ever happens -- you don't know if the whole thing
breaks after the next kernel upgrade.

I better stay away. I'll stick with a class compliant USB DAC or USB I2S interface.

Module goes back.

Subject closed.

Enjoy.