1

problem with Digi+ standard and raspberry pi2 B

mikolaj

August 29, 2017 21:42

None

Follow

I have a  problem with the newly bought Digi+ standard.

I have the freshly installed latest Raspbian Stretch Lite with kernel 4.9

I configured as described in manual:

/boot/config.txt

commented out:

# dtparam=audio=on

added:
dtoverlay=hifiberry-digi
dtdebug=1

 

after reboot, the result is:

$ aplay -l
aplay: device_list:270: no soundcards found...

 

interesting part of dmesg output:

[    4.902470] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    5.010808] snd-hifiberry-digi soc:sound: ASoC: CPU DAI (null) not registered - will retry
[    5.021924] snd-hifiberry-digi soc:sound: ASoC: CODEC DAI wm8804-spdif not registered - will retry
[    5.326902] smsc95xx 1-1.1:1.0 enxb827eb57a4a5: renamed from eth0
[    5.613587] wm8804 1-003b: Failed to read device ID: -121
[    5.613920] wm8804: probe of 1-003b failed with error -121

 

The output of:

vcdbg log msg 2>&1 | grep -i hifi

001580.559: dtdebug: Opened overlay file 'overlays/hifiberry-digi.dtbo'
001580.899: brfs: File read: /mfs/sd/overlays/hifiberry-digi.dtbo
001596.000: Loaded overlay 'hifiberry-digi'

 

So far i haven't found any solution on this forum.

I would be grateful for any advice.

Regards

Mik

• Facebook
• Twitter
• LinkedIn

2 comments

• 1
  
  Jim Mitchell August 29, 2017 22:29

  Mikoaj -

   

  What is the output of:

  [ uname -r  ] ?

  I've several Pi's running here & ones running the Stretch kernel '4.9.43-v7+' load the overlays with no problem.

  OTOH, a fresh install of Stretch from the Rasbian site uses kernel '4.9.41-v7+' - which doesn't load correctly - with multiple failures in the vcdbg log.

  If you perform a [ sudo rpi-update ] then the firmware updates to 4.9.44-v7+ and the Digi loads well - unfortunately, this breaks most of the Realtek 802.11AC wireless drivers that work under Jessie & the necessary kernel headers to recompile haven't been released yet.

  Cheers

  Jim

   

  Edited by Jim Mitchell August 29, 2017 22:32
• 0
  
  mikolaj August 30, 2017 07:08

  Thank you for response and information.

  The problem is already solved - and appeared to be trivial - connection. I detached dac+ from rbpi then attached again - and now it works perfectly! :) I should do this before spending time on software configuration.