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

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.

Former Member over 11 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 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 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
hystrix over 10 years ago in reply to fvan

In reply to post #7 (http://www.element14.com/community/message/136223#136223), is the OLED display connected using I2C or SPI?

Many thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
fvan over 10 years ago in reply to hystrix

via I2C
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
hystrix over 10 years ago in reply to fvan

I'm having problems with my OLED display connected using I2C. I posted details here: http://www.element14.com/community/message/158693#158693
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Former Member over 10 years ago in reply to hystrix

This is preliminary -- I've only just fired up an RPi 2-B with Cirrus audio card to use for a software-defined radio and I'm beginning to learn about it.

I found that i2c (to control an Si5351 frequency generator) is indeed carried through to the Cirrus connector, but apparently not to the pins given in the user manual at http://www.element14.com/community/servlet/JiveServlet/previewBody/72078-102-1-303819/Cirrus%20Logic%20Audio%20Card%20Us…
Unless, of course, I completely misunderstand the manual!

The manual lists header pins as 1, 2, 3 . . . but doesn't give their physical arrangement. I'm assuming that it is:

2 4 6 8 10 . . .
1 3 5 7 9

with pin 1 closest to the speaker header and the edge of the board as shown here:
https://github.com/guussie/PiDS/wiki/09.-How-to-make-various-DACs-work

That seems to work -- I can confirm pin 1 is +5v, pin 2 is +3.3v and pin7 is Gnd.

The manual gives pin 9 as SCLK (I presume they mean SCL) and pin 10 as SDA.

That doesn't work for me -- but I find pin 9 as SCL and pin 11 as SDA does work, provided pin 11 is not connected to my i2c device at boot-up. If it is, then the audio card fails to be recognised and instantiated.

So I have to boot up the RPi, then connect SDA -- which won't work for what's supposed to be a remote setup, wili it!

Does anyone else have similar experience, or any light to cast on mine?

Thanks -- Ross
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel