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
    About the element14 Community
  • 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
Blog Cirrus Logic Audio Card 2015 Update
  • 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
GPIO Pinout
Raspberry Pi Wishlist
Comparison Chart
Quiz
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: Former Member
  • Date Created: 16 Jan 2015 3:12 PM Date Created
  • Views 4809 views
  • Likes 4 likes
  • Comments 62 comments
Related
Recommended
  • raspberry_pi
  • raspeberry_pi_accessories

Cirrus Logic Audio Card 2015 Update

Former Member
Former Member
16 Jan 2015

Introduction to the Cirrus Logic Audio Card

With the launch of the Model B+ there was one significant, yet highly appreciated change which meant the existing audio card with the P5 pogo pins was no longer compatible with the Model B+. This is a mechanical limitation and unfortunately it wasn't possible to find a neat solution for the existing card.

To deliver the same audio experience we have updated and created a new audio card for Model B+, called the Cirrus Logic audio card. For anyone who may have missed it Wolfson Microelectronics was acquired by Cirrus Logic in the summer of 2014, hence the name change for the audio card.

This short blog introduces the new Cirrus logic audio card and provides some background on hardware and software developments.

 

Hardware

From a hardware perspective if it isn't broke then don’t mess with it - that was the simple approach we took to the hardware design.

So the updated audio card uses the same core components (WM5102 and WM8804) and has the same core architecture as the original card. From a features perspective there is no significant change however we have listened to the feedback and made some minor improvements. This is mainly around a back powering option, changing the expansion header to 2.54mm pitch, increasing the expansion header to make the unused GPIO pins from the Raspberry Pi accessible and adding the option to connect external stereo ECM microphones to the line input.  

This ensures that users can experience the same high quality audio experience using Model B / B+ or A+.

 

Please refer to the table on the main Cirrus Audio card community page, this provides a good summary of the feature comparison between cards.

 

The key take away on hardware is that the same primary functions remain on both audio cards with only minor changes in hardware design.

 

Software

From a software perspective we continue to update and improve.

Firstly the software for Model B and Model A+/B+ is exactly the same, automatic detection and pin mapping is included so there is no need for different compiled software kernels for the two boards. You can use the Cirrus 3.12 kernel image on either the Wolfson or Cirrus boards with no manual configuration or setup required.

 

What is currently available from a software perspective

  • A Raspbian image is available for download from the E14 community website using kernel 3.12. This will support the Model B,  B+ and A+ using either the Wolfson or Cirrus audio cards.
  • We have also published our source code for the 3.12 kernel on our own newly created github repository. You can find details and the source code here - https://github.com/CirrusLogic/rpi-linux/wiki

 

From the existing Raspberry Pi pull request we received good feedback on issues that users discovered, we have where possible addressed the issues and these are incorporated in the Cirrus github.


With regards to upstreaming into the Raspberry Pi kernel and in particular Kernel 3.12, we have encountered issues relative to how the kernel operates when the card is not connected, there are also issues which impact other audio cards. We have tried to find a solution to this but unfortunately the effort is not insignificant and reaches further than our own drivers. Therefore we are currently unable to support inclusion into the official Raspberry Pi 3.12 kernel.

We have discussed this with the maintainer and he is in support of this limitation and also with regards to our plans going forward.

 

What is our current plan going forward

Integration into the Raspberry pi kernel and in turn the Raspbian distribution remains our end goal. With the issues we have encountered integrating into the 3.12 kernel we are now focusing our efforts on integration to the latest kernel (3.18). The 3.18 kernel in particular adds support for device tree, this in turn provides support for add on modules and in particular will allow the issues with multiple I2S audio cards in 3.12 to be addressed. The Raspberry Pi kernel is planning to move from the current 3.12 kernel in the future so this provides an opportunity to add future support as part of the standard distribution.

 

 

There are now two audio cards available for the appropriate model of Raspberry Pi, both cards use the same software and most importantly both will deliver the same HD audio experience for both capture and playback.

 

We hope you find the new audio card a worthwhile addition to your Raspberry Pi Model B+ experience.

  • Sign in to reply

Top Comments

  • Former Member
    Former Member over 11 years ago in reply to Former Member +1
    It's unfortunate that we all have to engage in wishful thinking when it comes to looking for driver updates. Right now we're all scouring the internet, hoping to find things like updated drivers, better…
  • shabaz
    shabaz over 10 years ago in reply to Former Member +1
    bob p wrote: It's CirrusLogic's responsibility to fix their hardware/software problems. A minor point, but legally, that is likely not the case in most jurisdictions. I guess you mean some moral responsibility…
  • timg73
    timg73 over 11 years ago in reply to Former Member

    Element-14 should not be advertising the audio card as being compatible with the RPi-2:

    image

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

    It's unfortunate that we all have to engage in wishful thinking when it comes to looking for driver updates.  Right now we're all scouring the internet, hoping to find things like updated drivers, better instructions for how to build a compatible kernel/driver, etc.  The bad news is that we're not finding any updated drivers, or any better compiling instructions, because CirrusLogic is doing a crummy job of supporting this product.

     

    Consider this: If CirrusLogic had already solved this problem, and they had the working driver, they wouldn't be keeping it a secret.  It would be released with fanfare and everyone would know about it.  The fact that they aren't announcing it should tell you something.

     

    Also consider that we are failing to recognize the root of the problem when we hope that there is some Linux guru out there in the community who might want to help.  We've already got several linux gurus participating here, but the amount of help that any of them can give is limited by CirrusLogic failing to release the information that's necessary to fix the problem.  The second part of the problem is that it's not really the community's responsibility to fix CirrusLogic's driver problem.  It's CirrusLogic's responsibility to fix their hardware/software problems.  CirrusLogic is a large publicly-traded company (NASDAQ:CRUS) that has a market capitalization of $2,800,000,000.  They can certainly afford to pay a developer to solve this problem for them.  But we're not seeing any results.  That sends a clear message that fixing the problems in the CirrusLogic audio card isn't important to them.

     

    Fast-learners would stop buying the product.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • clem57
    clem57 over 11 years ago in reply to Former Member

    I can help you if you have questions. image

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Former Member
    Former Member over 11 years ago in reply to clem57

    ok, I got the device, kernel compilation is on the list of things I wonna learn, so I will give it a try tomorrow, although I dont't think it will work...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • clem57
    clem57 over 11 years ago in reply to Former Member

    oughy I unfortunately do not have the device. I only checked the level of changes and can say it was "meant for that level" of kernel. There is even proof of recent activity of changes. What I cannot say is it complete. Only takes someone to try it.

    Clem

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • 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 © 2026 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