Cirrus Logic Audio Card working on the Raspberry Pi 2

For those interested I've uploaded the following packages to my Raspbian repository (http://rpi.autostatic.com/):

• linux-image-cirrus: meta package that installs a kernel with Wolfson/Cirrus Logic audio interface support
• cirrus-config-overlay: package that installs the device tree overlay file for the Wolfson/Cirrus Logic audio interface
• cirrus-config-modprobe: package that installs the modprobe config file for the Wolfson/Cirrus Logic audio interface
• cirrus-config-scripts: package that installs the playback, record and reset scripts for use with the Wolfson/Cirrus Logic audio interface
• cirrus-config: meta package that installs all the above packages

If anyone is interested in testing these packages, go ahead, feedback is greatly appreciated. On a clean Raspbian install adding my repo, installing the cirrus-config package and rebooting your RPi should enable the Wolfson/Cirrus Logic audio interface. No need to edit any config files.

Jeremy

I tried, jeremy. it rendered my pi (temporarily) unusable after reboot. something must have gone wrong, I figure. this was a (quite fresh) 2015-05-05 image on a pi2.

fortunately I have a spare sd card where I will put the clean image onto and see where I can find a difference.

I tried, jeremy. it rendered my pi (temporarily) unusable after reboot. something must have gone wrong, I figure. this was a (quite fresh) 2015-05-05 image on a pi2.

fortunately I have a spare sd card where I will put the clean image onto and see where I can find a difference.

Hi Markus, sorry about that. I already know what the cause is, working on it.

jeremy, no problem. any quick hint for me to fix that manually while you prepare new debs? don't have access to the file system right now, though (I could, of course, boot the spare card and access the other via usb card reader).

You will need to comment the

kernel=vmlinuz-3.18.9-cirrus

line in /boot/config.txt so that your RPi loads kernel7.img again. So you will need to access the file system.

well, that part was easy. you can access it via the fat32 partition even in windows and modify that file. I was afraid I had to fiddle with the ext3 (or 4).

it's up again (could have figure myself, of course ), but thanks anyway! awaiting the updated packages now...

-greetings, markus-

Hi Markus, I've updated the packages. Thanks a lot for testing and providing feedback!

the update went fine until it reached the point where the hardlink to the initrd bak file is supposed to be created. then it bails out.it booted fine after that, but I realized that this is the standard 3.18.11 kernel.

the package update does not comment the alternate kernel and overlay back in, so I did. but after that it doesn't boot again. any helping information I should provide?

That shouldn't happen, I probably made a mistake somewhere. The problem

is that /boot lives on a FAT32 partition and apt/dpkg doesn't really

like that. I have to work a bit around that limitation and the solution

I'm using now is a bit hacky and apparently it doesn't work flawlessly

yet. If you could provide me with the warnings/error messages that'd be

great.

Jeremy

the hardlink creation fails with "permission denied" - it happens in /boot where the fat32 is mapped into, then. while the alternate kernel is commented in, you'll see colour gradient screen only. it doesn't even try to boot that kernel.

either there is some additional magic used to tell the pi to boot that specific kernel, or it just doesn't find it (as it recognises the vanilla kernel that obviously doesn't even have to be referenced in the config.txt).

Found the problem and I'll fix it. The linux-cirrus-image package merrily does a rm -f *3.18.9*cirrus on install but should only do that on upgrade. Thanks again for the feedback.