Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • Replies 165 replies
  • Subscribers 684 subscribers
  • Views 22737 views
  • Users 0 members are here
Related

Cirrus Logic Audio Card working on the Raspberry Pi 2

Former Member

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 image

 

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
  • Okay, so I have Raspbian 3.18 installed on my Pi2 and my Cirrus Logic Audio Card connected.  Not that I think it matters, but I'm using berryboot for the bootloader.  At any rate, I downloaded the tarball with the 3.18 kernel containing the CL drivers and untarred it into the root directory.

    The contents of /boot/config.txt
    core_freq=500

    sdram_freq=500

    over_voltage=2

    arm_freq=1000

    dtparam=spi=on

    dtparam=i2c_arm=on

    dtoverlay=rpi-cirrus-wm5102-overlay

    kernel=kernel7_CL.img

    The contents of /etc/modprobe.d/raspi-blacklist.conf

    softdep arizona-spi pre: arizona-ldo1

    softdep spi-bcm2708 pre: fixed

    And when I reboot and run the following commands, the card isn't recognized and it looks like the new kernel is being used either.  What am I missing?
    pi@raspberrypi ~ $ cat /proc/sys/kernel/osrelease
    3.18.6-v7i-aufs
    pi@raspberrypi ~ $ aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
      Subdevices: 7/8
      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]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    pi@raspberrypi ~ $ aplay -L
    null
        Discard all samples (playback) or generate zero samples (capture)
    pulse
        PulseAudio Sound Server
    default:CARD=ALSA
        bcm2835 ALSA, bcm2835 ALSA
        Default Audio Device
    sysdefault:CARD=ALSA
        bcm2835 ALSA, bcm2835 ALSA
        Default Audio Device
    pi@raspberrypi ~ $ cat /proc/asound/cards
    0 [ALSA          ]: bcm2835 - bcm2835 ALSA
                          bcm2835 AL
Reply
  • Okay, so I have Raspbian 3.18 installed on my Pi2 and my Cirrus Logic Audio Card connected.  Not that I think it matters, but I'm using berryboot for the bootloader.  At any rate, I downloaded the tarball with the 3.18 kernel containing the CL drivers and untarred it into the root directory.

    The contents of /boot/config.txt
    core_freq=500

    sdram_freq=500

    over_voltage=2

    arm_freq=1000

    dtparam=spi=on

    dtparam=i2c_arm=on

    dtoverlay=rpi-cirrus-wm5102-overlay

    kernel=kernel7_CL.img

    The contents of /etc/modprobe.d/raspi-blacklist.conf

    softdep arizona-spi pre: arizona-ldo1

    softdep spi-bcm2708 pre: fixed

    And when I reboot and run the following commands, the card isn't recognized and it looks like the new kernel is being used either.  What am I missing?
    pi@raspberrypi ~ $ cat /proc/sys/kernel/osrelease
    3.18.6-v7i-aufs
    pi@raspberrypi ~ $ aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
      Subdevices: 7/8
      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]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    pi@raspberrypi ~ $ aplay -L
    null
        Discard all samples (playback) or generate zero samples (capture)
    pulse
        PulseAudio Sound Server
    default:CARD=ALSA
        bcm2835 ALSA, bcm2835 ALSA
        Default Audio Device
    sysdefault:CARD=ALSA
        bcm2835 ALSA, bcm2835 ALSA
        Default Audio Device
    pi@raspberrypi ~ $ cat /proc/asound/cards
    0 [ALSA          ]: bcm2835 - bcm2835 ALSA
                          bcm2835 AL
Children
  • in reply to notorious.dds

    Hi Walter!

    Not that I think it matters, but I'm using berryboot for the bootloader.

    I have no experience of Berryboot, but I found this on the PLEX forums,  https://forums.plex.tv/index.php/topic/145555-want-rasplex-on-rpi2-try-the-berryboot-method/

     

    "When a compatible image is booted by BerryBoot, most of its kernel routines and drivers are replaced by those supplied by BerryBoot, which is necessary for these images to use the virtual filesystems needed to allow multiple images to coexist on the same card. But this also means that it is the drivers and kernel of BerryBoot which determine the hardware compatibility, as the system calls of the installed image are handled by the BerryBoot kernel and drivers, even if the installed image was compiled for other hardware."

     

    And, from Berryboot's own pages, http://www.berryterminal.com/doku.php/berryboot/adding_custom_distributions

     

    "Most Raspberry Pi operating system images are disk images containing two partitions. A FAT partition with the boot loader and kernel files, and a second ext4 partition with everything else. We are interested in the second partition...

    ... We are excluding /lib/modules from the image, because the kernel modules shipped with Berryboot are used instead..."

     

    It looks like Berryboot substitutes its own kernel and drivers.

    --

    Ragnar

  • in reply to Former Member

    It looks like Berryboot substitutes its own kernel and drivers.

    --

    Ragnar

     

    Ragnar, thank you so much for your efforts and helpful replies.  Upon reading your response, I did some playing around with Berryboot and discovered that although berryboot allows you to multiboot your RPi, the way that it achieves this by running each OS directly from the img file.  Any changes you make are saved in separate folder - much like when you live boot and OS on a USB stick with persistence.  At any rate, this was never going to permit updating the kernel used to boot Raspbian.  I've sinced used your img file with the updated kernel and all is well.  THANK YOU!

     

    One thing I did notice is that the default Broadcom sound card was commented out of the /etc/modules file.  Was that a setting you made or the result of something I did?  I've since removed the comment from the line in the /etc/modules file.  Is that an issue?

  • in reply to notorious.dds

    One thing I did notice is that the default Broadcom sound card was commented out of the /etc/modules file. Was that a setting you made or the result of something I did?

    I actually anticipated that someone would ask that very question image

     

    I did it on purpose. I commented out the Broadcomm sound card to make sure that the Wolfson/Cirrus card is the only visible card.

    During the last year, I have seen a lot of questions about how to select the Wolfson/Cirrus card in various applications.

    If there is only one card, many player and recording applications will have a much easier time finding it, since it becomes the default card.

     

    Feel free to remove the comment to enable the Broadcomm sound card. They will happily co-exist.

    --

    Ragnar