Cirrus Logic Audio Card working on the Raspberry Pi 2

Hi all!

As you might know, Cirrus Logic's main kernel source branch recently switched to 3.18.

My first thought was "Hmm, that means the Cirrus Logic card could finally work on the RPi2..."

I have built a couple of 3.18 kernels for my B+ and RPi2 and I have managed to get both models to produce sound

It's still early days, i.e. there are possibly bugs and glitches to fix, but for those of you who would like to try it out I've made an image file that you can download here:

https://drive.google.com/file/d/0BzIaxMH3N5O1cmJ1bFhMcG1hc0E/view?usp=sharing

The file is a 1.3 GB zip. Uncompressed size is 3.1 GB, so it fits comfortably on a 4 GB card.

The image is based on the standard 2015-02-16-raspbian-wheezy image from the Foundation that you flash to a SD card for a fresh install.

I have only added my kernels and set up the configuration files to get the card going.

It should work on the older B model with a Wolfson Audio Card too, but I haven't tested that yet.

Have fun!

Ragnar

Parents

Former Member over 10 years ago
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
Cancel
Vote Up +2 Vote Down

Sign in to reply

Cancel
Former Member over 10 years ago in reply to Former Member

hi jeremy,

I ended up purging all the cirrus packages (apart from the linux-libc6-dev, which had dependencies). while doing this I noticed that some of the packages where in iU state before I purged them.
may be a relict from the first installation and the first update.

after updating the repository I had all packages on ii, the config.txt was updated (I noticed that you use a different image name, since the upgrade adds the image and overlay section again
- it is -v7 now, but I don't know what the statement was like in the first install. the non -v7 shouldn't boot on pi2 anyway - is that the source of my error, maybe?)

anyway, it boots now with the correct image, so I have to deal with the input/output scripts now, I suppose.

thanks a lot for your efforts!

-greetings, markus-
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Former Member over 10 years ago in reply to Former Member

hi jeremy,

I ended up purging all the cirrus packages (apart from the linux-libc6-dev, which had dependencies). while doing this I noticed that some of the packages where in iU state before I purged them.
may be a relict from the first installation and the first update.

after updating the repository I had all packages on ii, the config.txt was updated (I noticed that you use a different image name, since the upgrade adds the image and overlay section again
- it is -v7 now, but I don't know what the statement was like in the first install. the non -v7 shouldn't boot on pi2 anyway - is that the source of my error, maybe?)

anyway, it boots now with the correct image, so I have to deal with the input/output scripts now, I suppose.

thanks a lot for your efforts!

-greetings, markus-
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data