My Hifiberry-Digi is not working anymore with Openelec.
The error is got in dmesg is:
[ 4.420180] snd-hifiberry-digi sound: ASoC: CPU DAI (null) not registered
[ 4.420215] snd-hifiberry-digi sound: snd_soc_register_card() failed: -517
[ 4.420599] snd-hifiberry-digi sound: ASoC: CODEC DAI wm8804-spdif not registered
[ 4.420617] snd-hifiberry-digi sound: snd_soc_register_card() failed: -517
I tried the testtone image and that one is working fine. So there is in my opinion no hardware error.
The version op OpeneElec I'am using is: 5.95.3. I tried also the version 5.0.8. Same problem.
My Raspberry is a Model B 1024MB.
Output aplay -
aplay: device_list:268: no soundcards found...
Files:
/flash/config.txt contains:
dtoverlay=hifiberry-digi
dtdebug=1
Output of vcdbg log msg contains:
001601.195: Loaded overlay 'hifiberry-digi'
001611.786: dtdebug: Found fragment 0 (offset 36)
001612.915: dtdebug: merge_fragment(/sound,/fragment@0/__overlay__)
001612.940: dtdebug: +prop(compatible)
001614.084: dtdebug: +prop(i2s-controller)
001615.497: dtdebug: +prop(status)
001616.709: dtdebug: merge_fragment() end
001616.770: dtdebug: Found fragment 1 (offset 168)
001619.651: dtdebug: merge_fragment(/soc/i2s@7e203000,/fragment@1/__overlay__)
001619.676: dtdebug: +prop(status)
001620.593: dtdebug: merge_fragment() end
001620.679: dtdebug: Found fragment 2 (offset 244)
001624.980: dtdebug: merge_fragment(/soc/i2c@7e804000,/fragment@2/__overlay__)
001625.004: dtdebug: +prop(#address-cells)
001625.760: dtdebug: +prop(#size-cells)
001626.523: dtdebug: +prop(status)
001629.369: dtdebug: merge_fragment(/soc/i2c@7e804000/wm8804@3b,/fragment@2/__ov
001629.395: dtdebug: +prop(#sound-dai-cells)
001630.225: dtdebug: +prop(compatible)
001630.961: dtdebug: +prop(reg)
001631.751: dtdebug: +prop(status)
001632.574: dtdebug: merge_fragment() end
001632.600: dtdebug: merge_fragment() end
001632.773: dtparam: arm_freq=900000000
001634.276: dtdebug: Found override arm_freq
001634.320: dtdebug: override arm_freq: cell target clock-frequency @ offset 0
001639.002: dtdebug: override arm_freq: cell target clock-frequency @ offset 0
001643.761: dtdebug: override arm_freq: cell target clock-frequency @ offset 0
001648.645: dtdebug: override arm_freq: cell target clock-frequency @ offset 0
001653.597: dtparam: cache_line_size=64
001655.302: dtdebug: /__overrides__ has no cache_line_size property
001655.314: Unknown param 'cache_line_size' - ignored
001727.183: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
002550.301: vchiq_core: vchiq_init_state: slot_zero = 0xeec80000, is_master = 1
Anyone any idea what could cause this problem?
Greetz,
Karl
Date
Votes
10 comments
-
HiFiBerry team Hi Karl,
on the RPI1 and OpenElec, the configuration is still the old way without device tree overlays:
https://www.hifiberry.com/guides/openelec-configuration/
Best regards
Daniel -
jl_bonnaffe Hi Hifiberry team,
Similar issue here. However, my configuration is a bit different :
- RasPi A+ with Hifiberry DacPlus standard phone
- Buildroot custom distrib with :
- raspberry-pi firmware (git://github.com/raspberrypi/firmware.git) - latest to date
- raspberry-pi linux (git://github.com/raspberrypi/linux.git) - tag 3.18.y and bcmrpi_defconfigThe DAC worked correctly when I was using a config without the device tree.
But now that it's activated, I get (- and sorry I can't get the dtdebug to print -) :[ 22.602836] snd-rpi-hifiberry-dacplus sound: ASoC: CPU DAI (null) not registered
[ 22.629977] i2c 1-004d: Driver pcm512x requests probe deferral
[ 22.648160] bcm2708_i2c 20804000.i2c: BSC1 Controller at 0x20804000 (irq 79) (baudrate 100000)
[ 22.668057] snd-rpi-hifiberry-dacplus sound: snd_soc_register_card() failed: -517
[ 22.712692] platform sound: Driver snd-rpi-hifiberry-dacplus requests probe deferral
[ 22.723112] i2c 1-004d: Driver pcm512x requests probe deferral
[ 22.737370] i2c 1-004d: Driver pcm512x requests probe deferral
[ 22.774805] i2c 1-004d: Driver pcm512x requests probe deferral
[ 22.787253] snd-rpi-hifiberry-dacplus sound: ASoC: CODEC DAI pcm512x-hifi not registered
[ 22.807923] snd-rpi-hifiberry-dacplus sound: snd_soc_register_card() failed: -517
[ 22.826927] platform sound: Driver snd-rpi-hifiberry-dacplus requests probe deferraland my lsmod :
snd_soc_hifiberry_dacplus 2657 0
snd_soc_pcm512x_i2c 1710 0
snd_soc_pcm512x 6564 1 snd_soc_pcm512x_i2c
regmap_i2c 2320 1 snd_soc_pcm512x_i2c
snd_soc_bcm2708_i2s 6142 0
snd_soc_hifiberry_dac 2376 0
regmap_mmio 2674 1 snd_soc_bcm2708_i2s
snd_soc_core 136015 4 snd_soc_hifiberry_dacplus,snd_soc_pcm512x,snd_soc_bcm2708_i2s,snd_soc_hifiberry_dac
snd_compress 7235 1 snd_soc_core
i2c_bcm2708 5263 0
snd_pcm_dmaengine 3916 1 snd_soc_core
snd_usb_audio 101546 0
snd_usbmidi_lib 18707 1 snd_usb_audio
snd_hwdep 5554 1 snd_usb_audio
snd_rawmidi 19121 1 snd_usbmidi_lib
snd_seq_device 5205 1 snd_rawmidi
snd_pcm 72429 4 snd_soc_hifiberry_dac,snd_soc_core,snd_pcm_dmaengine,snd_usb_audio
snd_timer 19060 1 snd_pcm
snd 50446 9 snd_soc_core,snd_compress,snd_usb_audio,snd_usbmidi_lib,snd_hwdep,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer
uio_pdrv_genirq 3062 0
uio 7308 1 uio_pdrv_genirqWill I also have to stick with the old way ?
-
HiFiBerry team Configuration with device tree is different:
http://support.hifiberry.com/hc/en-us/articles/205377651-Configuring-Linux-3-18-x-or-higher
If this isn't working, I can't say what is the specific problem in your installation. We recommend to use the standard distribution. With customs build there can be all kinds of problems that we don't know.
If you want to have a clean working installation, I recommend using our installer:
http://support.hifiberry.com/hc/en-us/articles/205389831-HiFiBerry-installer
Best regards
Daniel Matuschek -
jl_bonnaffe Alright, thanks for the reply. That was quick.
Would you by any chance have a working kernel config file (ideally, close to 3.18.16) ? That would be extremely helpful.Cheers,
_jean-louis -
HiFiBerry team The default configuration should work fine. Why are you still using 3.18? 4.x is stable for quite some time.
Best regards
Daniel -
jl_bonnaffe Because my project was created long before 4.x was out, and upgrading my config to 3.18 was already a pain.
Sorry, by default configuration, do you mean 'bcmrpi_defconfig ?'
-
-
HiFiBerry team bcmrpi_defconfig
Did you check if your kernel is using device tree overlays?
Best regards
Daniel -
jl_bonnaffe Yes for the device tree (Machine identified as Raspberry Pi, /proc/device-tree/ available, etc).
And yes for the device tree overlay (hifiberry_dac_plus module inserted without the *.ko file). -
HiFiBerry team Then I guess you have to start debugging the device tree load process.
Best regards
Daniel
Please sign in to leave a comment.