Thanks Marcel I will download winimage and try that.
I'll let you know how it goes.
I downloaded winimage and wrote your image to an SD card.
The image boots, but the card still does not work. I've tried with USB power and 5V directly to the CLAC via the power connector. I get this in dmesg
[ 13.918723] arizona spi0.1: Failed to get mclk1: -2
[ 13.918750] arizona spi0.1: Failed to get mclk2: -2
[ 13.919311] arizona spi0.1: Failed to request DCVDD: -517
[ 13.994895] arizona spi0.1: Failed to get mclk1: -2
[ 13.994924] arizona spi0.1: Failed to get mclk2: -2
[ 13.995465] arizona spi0.1: Failed to request DCVDD: -517
[ 14.117710] arizona spi0.1: Failed to get mclk1: -2
[ 14.117738] arizona spi0.1: Failed to get mclk2: -2
[ 14.118266] arizona spi0.1: Failed to request DCVDD: -517
[ 14.130951] arizona spi0.1: Failed to get mclk1: -2
[ 14.130979] arizona spi0.1: Failed to get mclk2: -2
[ 14.131523] arizona spi0.1: Failed to request DCVDD: -517
[ 14.137172] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
[ 14.239109] wm8804 1-003b: revision E
[ 14.242608] arizona spi0.1: Failed to get mclk1: -2
[ 14.242635] arizona spi0.1: Failed to get mclk2: -2
[ 14.243212] arizona spi0.1: Failed to request DCVDD: -517
[ 14.243928] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
[ 15.994324] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 16.107111] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 17.614397] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 22.049458] arizona spi0.1: Failed to get mclk1: -2
[ 22.049484] arizona spi0.1: Failed to get mclk2: -2
[ 22.068041] LDO1: supplied by RPi-Cirrus 1v8
[ 22.091171] arizona spi0.1: Unknown device ID: 0
[ 22.094043] arizona spi0.1: Failed to get mclk1: -2
[ 22.094073] arizona spi0.1: Failed to get mclk2: -2
[ 22.094585] LDO1: supplied by RPi-Cirrus 1v8
[ 22.101165] arizona spi0.1: Unknown device ID: 0
[ 22.102386] snd-rpi-cirrus soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered - will retry
[ 27.739711] random: crng init done
And this from aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
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]
Subdevice #0: subdevice #0
I think my CLAC must be broken
I am sorry to bother you, but I am seeking to set up a mysql database of the current parameter set of the Wolfson driver, that way I can serve (via LAMP) HTML pages showing the current status of the device and, using amixer calls, change driver settings.
I can sed the output of "amixer contents" and import much of it into a mysql DB, but I have one great problem with this approach. The first value in the "values" field is sometimes decimal and sometimes hex. This makes importation very difficult. Is there some other way of accessing the parameter set?
I am not a coroner but I too suspect the card is dead.
Perhaps Mathias can confirm , with all my setups and boots after the :
[ xx ] LDO1: supplied by RPi-Cirrus 1v8
your wolfsonchip should be recognized.:
[ xx ] arizona spi0.1: WM5102 revision C.
I am sorry for your loss.
I am trying to get the Cirrus board to work on RPi 3, but I am also experiencing some problems. I have tried several approaches including the one described here.
I sincerely hope someone will be able to help. Please be aware that I am quite a newbie to RPi and Linux :-)
vcgencmd version https://paste.ubuntu.com/24847306/
sudo vcdbg log msg 2>&1 https://paste.ubuntu.com/24847316/
aplay -l https://paste.ubuntu.com/24847329/
**Additionally** Since the Cirrus board has been discontinued, I am looking for another RPi sound card. I need as many digital inputs as possible and preferably 96kHz/24 bit. Does anyone have any suggestions?
It seems your last 3 paste files contain the same.
From that I suspect the driver is not loaded properly ,but not sure what causes it .
I assume the red led on the Cirrus is lit after the full boot, and might be off during some period during the boot process.
You can try to manually unload reload a driver to try again:
If done from a script use :
sudo modprobe -r arizona_spi
sudo modprobe arizona_spi
Else you can omit the sleep statements.
If you read back in the trail I offered a prebuild image to Matt, It is still available to test the set with a preconfigured PiCorePlayer install.
Write it to a small SD and you should get a working install in minutes.
Thanks for your quick answer! I made a mistake when copying the links, but they should be updated now.
Actually, both LEDs are on all the time, even during reboot. I tried the commands you suggested, but I dont see any difference.
I will try the prebuild image you mention and report back with the results.
Thanks for your help.
I've been working on a driver rework, mainly to get rid of the requirement to carry around a bunch of patches to upstream driver code, and also to fix some outstanding issues and introduce some new features.
Most issues have been ironed out so here's the first public release.
Edit: the driver has been included in official RPi kernels. Just run sudo rpi-update to install it.
You still have to install the mixer scripts and add the /etc/modprobe.d file. See my website for details
Precompiled kernel: http://www.horus.com/~hias/tmp/cirrus/cirrus-ng-linux-4.9.0.tgz
New mixer scripts: http://www.horus.com/~hias/tmp/cirrus/cirrus-ng-scripts.tgz
- The new driver bases on the rather fresh kernel 4.9.0 which means there's some risk of (yet unknown) issues. Use it at your own risk and please run "rpi-update" to get the latest firmware before installing the new driver.
- The soundcard name has been changed from "snd_rpi_wsp" to "RPi-Cirrus", also several ALSA controls have been removed and new ones were added. This means the old usecase scripts and any custom-made scripts will no longer work. Use the new mixer scripts instead of the old usecase/listen scripts.
- The new driver supports setting (and receiving) of the S/PDIF channel status bits (aka AES bits). If you add an ALSA card configuration file this means applications like Kodi can do proper AC3/DTS passthrough. A sample card configuration file (plus the mixer scripts) can be found here: https://github.com/HiassofT/rpi-cirrus-config
- I haven't fully updated the documentation on my website RPi Linux driver for Wolfson / Cirrus Logic Audio Card yet, will do that during the next weeks/months. But except for the things noted above most stuff should still work as in previous driver versions.
Please report back if you tested the driver (either successfully or unsuccessfully), any feedback will help me!