element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Raspberry Pi Forum Cirrus Logic Audio Card working on the Raspberry Pi 2
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 165 replies
  • Subscribers 684 subscribers
  • Views 22753 views
  • Users 0 members are here
  • wolfson
  • raspberry
  • audio
  • pi
  • cirrus
  • raspberry_pi
  • rpi2
  • raspeberry_pi_accessories
  • pi2
Related

Cirrus Logic Audio Card working on the Raspberry Pi 2

Former Member
Former Member over 10 years ago

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

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    Former Member over 10 years ago

    Hello all, especially Ragnar,

     

    so I've tried really hard to get the 3.18.9 kernel on a RPiB+ to work but with no success. Maybe someone can give me a hint.

    A brief summary what I tried:

    • Installed the original CL image (cirrus_audio.zip) according the instruction in "Cirrus Logic Audio Card for B+ and A+ onwards V1.02.pdf" --> OK worked out, I got sound out of the CL card
    • Installed the original 2015-02-16-raspbian-wheezy image --> OK RPiB+ is working fine
    • Nothing else touched except expanding the SD card via raspi-config
    • Installed the patches according to Ragnars description above, edited the config.txt & raspi-blacklist.conf and made sure that the RPiB+ kernel is chosen (kernel=kernel_CL.img)

     

    On reboot the RPi is not coming to an end. You see the green led (of the RPi (not the CL-card)) blinking shortly then de-illuminated and only the red led illuminated permanently, the RPi not reactin, not visible on the ethernet.

    Any ideas what I made wrong?

     

    The reason why I want to have the kernel update procedure working is that I want to install the musicbox package --> this would mean install the musicbox first and then the CL kernel patch afterwards.

     

    Txs for your help!

     

    Edit: Myybe something important: I got a warning message after the tar .../kernel_3_18_9_W_CL.tgz command. Something like "finished with failures due to previous errors". Could this give a hint?

    Frank

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to Former Member

    ebefra

     

    Do you have all this in /boot/config.txt ?

    dtparam=spi=on
    dtparam=i2c_arm=on
    dtoverlay=rpi-cirrus-wm5102-overlay

    And you do have the overlay file in place?

    $ ls -l /boot/overlays/rpi-cirrus-wm5102-overlay.dtb
    -rwxr-xr-x 1 root root 3334 Mar 27 18:59 /boot/overlays/rpi-cirrus-wm5102-overlay.dtb

    --

    Ragnar

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to Former Member

    Hi Ragnar

     

    yes, both items verified, the config.txt is exactly as your example, all other lines only comments (and by the way if I put the # kernel.... the original kernel is working again)

      -rwxr-xr-x 1 root root 0 Mar 27 17:59 /boot/overlays/rpi-cirrus-wm5102-overlay.dtb is my answer on ls -l /boot/overlays/rpi-cirrus-wm5102-overlay.dtb

     

    Have you seen my added hint on a failure message after using the tar command?

    Txs for your help!!!

    Frank

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Former Member
    Former Member over 10 years ago in reply to Former Member

    Hi Ragnar

     

    yes, both items verified, the config.txt is exactly as your example, all other lines only comments (and by the way if I put the # kernel.... the original kernel is working again)

      -rwxr-xr-x 1 root root 0 Mar 27 17:59 /boot/overlays/rpi-cirrus-wm5102-overlay.dtb is my answer on ls -l /boot/overlays/rpi-cirrus-wm5102-overlay.dtb

     

    Have you seen my added hint on a failure message after using the tar command?

    Txs for your help!!!

    Frank

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • Former Member
    Former Member over 10 years ago in reply to Former Member

    No, I didn't see that. It definitely hints at a corrupt download, though. There shouldn't be any complaints from tar.

     

    $ md5sum kernel_3_18_9_W_CL.tgz 
    ce65d837280659e90ea99b5b6aba8566 kernel_3_18_9_W_CL.tgz

     

     

    EDIT: I missed this at first:

      -rwxr-xr-x 1 root root 0 Mar 27 17:59 /boot/overlays/rpi-cirrus-wm5102-overlay.dtb is my answer on ...

    That doesn't look right, the overlay file is zero bytes, it should be 3334 bytes.

    --

    Ragnar

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to Former Member

    Hello Ragnar,

    finally solved as you gave me the hint and you were right --> the overlay file was empty.

    And I found out why and want to post it here as this might happen to other folks as well:

    • The md5 checksum was OK on the windows machine as well as on the RPi
    • The error message while extracting the tgz file was:     tar: Exiting with failure status due to previous errors

    Reason for that:

    • While downloading the kernel...._CL.tgz file on a windows machine and copying the file to the SD card to the /boot directory (as this is the only visible directory under windows)
    • The /boot directory was 100% used and consequently no file could be really writen into this dir --> above error message generated

     

    root@raspberrypi:/# df -h

    Filesystem      Size Used Avail Use% Mounted on

    rootfs          15G 2.6G  12G  19% /

    /dev/root        15G 2.6G  12G  19% /

    devtmpfs        214M 0  214M  0% /dev

    tmpfs            44M 232K  44M  1% /run

    tmpfs          5.0M    0 5.0M  0% /run/lock

    tmpfs            88M    0 88M  0% /run/shm

    /dev/mmcblk0p1 56M  56M    0 100% /boot


    After removing the kernel..._CL.tgz file to another location everything operated perfectly. I got the CL card to work, yipiyeah


    Txs for your hints!!


    Frank

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube