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
Raspberry Pi Forum Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
  • 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 37 replies
  • Subscribers 687 subscribers
  • Views 4443 views
  • Users 0 members are here
  • raspberry_pi
  • raspeberry_pi_accessories
Related

Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?

gkzsolt
gkzsolt over 11 years ago

The previous Wolfson card has a 26 pin header with male pins to connect to the Raspberry GPIO header after pushed on top of it. Does the new audio card do the same for the 40 pin header? Sorry, but I cannot discern from the card images I have.

  • Sign in to reply
  • Cancel
Parents
  • fvan
    fvan over 11 years ago

    There is a table in the user manual with the remaining I/O on the expansion header.

     

    image

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • tonyhansen
    tonyhansen over 11 years ago in reply to fvan

    In this table (e), pins 16-20 are ALL described as "General Purpose Pin GPIO 3", which looks to me like a copy/paste error from the pin 15 description.

     

    It would be nicer if table (e) were to read:

     

    PinNameType

    Power

    Domain

    Description
    17GPIO6_EXDigital In/Out0 - 3.3VRPI General Purpose Pin GPIO6 (RPI pin 31)
    18GPIO12_EXDigital In/Out0 - 3.3VRPI General Purpose Pin GPIO12 (RPI pin 32)
    19GPIO16_EXDigital In/Out0 - 3.3VRPI General Purpose Pin GPIO16 (RPI pin 36)
    20GPIO26_EXDigital In/Out0 - 3.3VRPI General Purpose Pin GPIO26 (RPI pin 37)

     

     

    However, there are discrepancies between this table (e) and the description within the schematic that need to be figured out.

     

    Pins 10 and 11 are flipped between the schematic and table (e). (In the schematic, pin 10 is listed as PDMOUT_DAT [3] while table (e) says pin 10 is SDA. And vice versa for pin 11.) Which is correct?

     

    In the schematic, pin 14 is listed as connected to "GPIO5_EX [7]", which SHOULD correspond to PI GPIO 5 (PI pin 29). However table (e) lists pin 14 as being GND. Which is correct?

     

    In the Cirrus Logic Audio Card Comparison Table, it says that there are 8 PI connections (including the UART). The UART is connected to the Cirrus J8 Header. (RPI pins 8&10)

     

    Can anyone confirm definitively which are the other two GPIO pins that are tied directly from the PI into the Cirrus expansion header?

     

    • Expansion header pin 15 and 16 are marked GPIO4 and GPIO3, but those appear to be connected to GPIO4&3 on the WM5102_CSP137 chip instead of the RPi GPIO pins.
    • Pin 14 might be one of them if the schematic is correct but table e is not.

     

    Any definitive clues?

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

    Thank you, Scott, it looks great and very helpful!

     

    "Although they are not enabled in the current driver they provide scope for increased functionality going forward."

    Does it mean I can use those "unused" GPIOs as is, or I need to hack kernel driver somehow to make them free for using?

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

    >  Does it mean I can use those "unused" GPIOs as is, or I need to hack kernel driver somehow to make them free for using?

     

    I guess it means that you could use them now as is, if you'd want this very much, but you are not advised to do so, because they can be used some time in the future (drivers), for "increased functionality going forward" image

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

    Scott, many thanks for this and for passing the information on to E14. Could you pls. correct "SCL I2C" in the table to "SCL1 I2C"? (there are 2 I2C interfaces on the RPi, and that is from intf. 1)

     

    Also, if you could ask E14 to generate the doc pdf-s as for them to be searchable, it would be great. I don't think this to be too complicated, but the current manual is very, very hard to use. You cannot search any text, but neither can you copy and paste most of them, should it be a link, for example (text in tables *is* searchable, but normal text is not). I had to manually enter the (long) link from Annexe 7 d. of the "Schematic diagram" (have to enter this as well;), and on top of that, as I remember it was wrong, linking to the schematic of the Wolfson audio card! So please, can somebody at Cirrus check the links validity as well? Thanks,

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

    If so, I'm happy to hear that! It solved half of my alleged problems. image

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

    Scott,

     

    Your table suggests that the SPI control pins are still exposed through a header called J9. While this is good news, I am sorry to not find this header on the Cirrus schematics. Maybe I've missed it, but if not, would you be so kind to ask them for an update?

     

    Thanks,

      Zsolt

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

    Thank you for posting this table, Scott.

     

    It took me a while to realize how to interpret your references to the SPI functions on the J9 header. (J9 is the name for the 40-pin connector from the Cirrus board to the RPi J8 40-pin header.)


    The actual pins are NOT easily connected to, as they require you to use either: a shim connector between the two boards, or resoldering the pins.

     

    Nonetheless, the data IS important in that it confirms that the SPI pins ARE indeed being used for SPI and haven't been used for some other GPIO purpose.

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

    I have some comments about using "semi free" or "unused" GPIOs of Cirrus Logic AC. I mean GPIOs 04, 24, 25, and 27.

    In my project I use RPi with CLAC and SleepyPi to make battery powered field recorder for animal sounds. To make possible these three boards be connected I had have to make an adaptor from Exp. header of CLAC to Sleepy. To managing power of Rpi Sleepy needs GPIOs 24 and 25. 25 is present in CLAC Exp. header, so at the beginning I wanted to use it as is. But it didn't work, and when I checked voltage on this pin, my multimeter showed 0.7V, but not 3.3V. I measured this pin voltage in all combinations of boards (I have Rpi B+, couple of RPi A+, two CLACs and two Sleepy Pi) - results were the same. On Rpi without audio card and normal Raspbian loaded, those GPIOs of course had 3.3V when I switched them to High. Finally I have used "true free" pins from Exp. header, and everything is working properly.

     

     

    Thus, these pins (at least 25th), it seems, can not be used as normal GPIOs, despite the fact that they are unused in this version of the CLAC driver.

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

    Thanks for the feedback. We believe we have discovered and resolved the cause of the problem in the 3.18 driver which has been just been released. The GPIO pin of the WM5102 was incorrectly configured as an output, in the 3.18 driver this is now configured as an input. This issue was stopping the use of GPIO25 from the Pi as reported by Ivan W.

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

    Correct me if I'm wrong, but from reading this thread it seems like one needs to use (some of) the 20 Expansion Header pins for GPIO access.

    If this is the case is there a recommended 2 x 10 pin ribbon cable ?

     

    Thanks

    • 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,

     

    Instead of attaching the cirrus card to the 40 pins, lock, stock and barrel, could one connect only the necessary pins on the card and GPIO with jumper leads, thus leaving all the other pins available ?

    And maybe even leave out pins one doesn't need - for example if one only needed the mini jack line in and out ?

     

    Thanks,

     

    Jem

    • 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

    Hello,

     

    Instead of attaching the cirrus card to the 40 pins, lock, stock and barrel, could one connect only the necessary pins on the card and GPIO with jumper leads, thus leaving all the other pins available ?

    And maybe even leave out pins one doesn't need - for example if one only needed the mini jack line in and out ?

     

    Thanks,

     

    Jem

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
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