37 Replies Latest reply on Sep 26, 2015 4:37 AM by drb

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

    gkzsolt

      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.

        • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
          gkzsolt

          Of course I am interested also in which pins it uses from the GPIO header. I don't seem to get this from the documentation.

          • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
            Frederick Vandenbosch

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

             

            Screen Shot 2014-12-29 at 14.57.55.png

              • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                gkzsolt

                Thank you both. From the schematics I see they use the I2C and SPI pins, for example, but there is no sign of them passing out, to connect other devices. (although they are designed to connect several devices, not only one, isn't it?) With the Raspberry model B, we had, beside the I2C (2 pins) and SPI (4 pins) other 11 pins for general IO, with the model B+ this increased to at least 20 - so 26 pins, counting the 6 mentioned ones. Now on the Cirrus card expansion header I see 6 pins for general IO, plus some pins I don't understand. There is no mention of SPI, there is SDA and SCLK (Control Interface - what does it mean?) which resemble the I2C (just the clock was named SCL, and "Control Interface clock input" is a bit confusing, because I2C clocks can be output as well, as I know), and a few pins I don't understand. The Audio Interface 3 seems to refer to the SPDIF, isn't it? There are also 2 pins for a "Digital speaker", what can be very cool, I assume (for audiophiles). So if I put in Cirrus, it looks like the whole Raspberry is converted to a super audio card, with a lot of audio inputs and outputs. If I want to do some other stuff, I should content myself with a total of 6 GPIO pins (and this with the model B+). Cool, isn't it?

                • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                  tonyhansen

                  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?

                    • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                      gkzsolt

                      Good call. I've seen only now the whole schematics, sorry.

                      • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                        wan1

                        Yes, some of these errors I pointed out too in my comments to the CL manual.

                         

                        Pin 14 is GPIO 5 for sure. It is wired physically to the Pin 29 in 40-pin header.

                         

                        Pin 11 (Not Pin 10!) is wired to the Pin 03 of 40-pin header - GPIO 2 (SDA1, I2C). So, Pin 10 could be PDMDAT.

                         

                        As far as Pin 09 is SCL, and (I checked) it is connected to the Pin 05 of 40-pin header - it's GPIO 3. So the Pin 16 of Expansion header should be something else.

                        Both of pins 15 and 16 are not connected to any of pins of 40-pin header.


                        So we have 6 GPIOs that are tied directly from the RPI into the Cirrus L Expansion header (Pins 09, 11, 14, 17, 18, 19, 20).

                        This is what can be easily verified by a simple multimeter.

                         

                         

                          • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                            tonyhansen

                            If what you say is correct, that means I count 9 GPIO pins that are passed through from the RPi, the 7 GPIOs (not 6) you list (Pins 09, 11, 14, 17, 18, 19, 20) that are passed through the Expansion header, and 2 more that are passed through the J8 header.

                             

                            I put together this table for my own notes and figured I'd share it:

                             

                                


                            Cirrus Logic

                            Audio Board

                            Pin

                            RPi GPIO

                            Description

                            RPI Alternate

                            Description

                            RPi pin

                            1

                            EX 9

                            GPIO 3

                            SCL I2C

                            5

                            2

                            EX 11

                            GPIO 2

                            SDA1 I2C

                            3

                            3

                            EX 14

                            GPIO 5

                             

                            29

                            4

                            EX 17

                            GPIO 6

                             

                            31

                            5

                            EX 18

                            GPIO 12

                             

                            32

                            6

                            EX 19

                            GPIO 16

                             

                            36

                            7

                            EX 20

                            GPIO 26

                             

                            37

                            8

                            J8-1

                            GPIO 14

                            UART TX

                            8

                            9

                            J8-2

                            GPIO 15

                            UART RX

                            10

                             

                             

                            Of course, this doesn't match the number 8 that is mentioned in the Cirrus Logic Audio Card Comparison Table. No reconciling that yet.

                              • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                gkzsolt

                                Sorry to ask, what do you mean by GPIO pins that are passed through from the RPi? How can I access those? (I don't have a Cirrus card yet).

                                  • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                    tonyhansen

                                    The Cirrus Logic Audio Card (and the Wolfson Audio Card before) have a few headers sticking up. In particular, the Cirrus Logic Audio Card has a header known as the J2 Expand (or Expansion) Header and another header known as J8 (marked UART on the CL), some of whose pins are direct connections to (i.e., pass-throughs of) the GPIO pins on the Raspberry Pi itself. The other pins are instead connected to various features of the Audio Board itself.

                                     

                                    For more information, see

                                    • the table in previous posts for which CL header pins are hooked to which RPi pins,
                                    • the user manual (which currently has some typos in it), or
                                    • the schematic.
                                      • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                        gkzsolt

                                        Thank you again. I am sorry, I've misread your previous comment (and not looked at the schematic and table attentively.) Now I've done this.

                                        The user manual definitively needs major corrections. What is not clear now is what are pins 15 and 16 on the expansion header, if they are not GPIO4 and GPIO3.

                                        9 GPIO pins passed through from the RPi doesn't sound very bad, but what worries me very much is that the SPI bus pins (GPIO9, 10 and 11, not counting CE0 and CE1) are not between them. So how can I use any SPI device then?

                                         

                                        Another note. According to the Cirrus Logic Audio Card Comparison Table, the previous Wolfson Audio Card had only 3 available Pi GPIO pins, including UART. Is that true? It follows that using the new one would be a better choice. But on the old card and RPi I could access the general protocol pins, in particular the SPI bus because the whole RPi P1 header was available. Am I right?

                                         

                                        The pdf user manual I downloaded is not text searchable, at least I cannot search it with Linux evince. Is this my fault?

                                          • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                            tonyhansen

                                            Correct, pins 15&16 are marked GPIO4&3. But if you look at the schematic, you will see that those are GPIO connections from the AUDIO chip, and NOT the RPi. And I haven't seen any reports of anyone finding an interface for controlling those audio chip pins.

                                             

                                            You cannot directly use an SPI device when the audio board is mounted. But you can use UART and I2C.  If you >really< need SPI, you'll need to use a bridging device between I2C or UART and SPI.

                                             

                                            The older Wolfson Audio card has the same architecture as the newer board: it plugs into the RPi J8 header AND has contact pins to the P5 interface, then uses most of the available RPi GPIO pins for its own purposes, including the P5 GPIO pins. Your choices are limited.

                                             

                                            Hope this helps.

                                              • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                gkzsolt

                                                Thanks for looking up the 15 & 16 pins.

                                                 

                                                "You cannot directly use an SPI device when the audio board is mounted."

                                                 

                                                Why? To my knowledge, the SPI control pins are general: the clock, MOSI and MISO are shared between all SPI devices (like on the I2C). There is one pin dedicated to each slave, a CHIP SELECT (and maybe some other pins too, depending on the device). I have an nRF24 device connected to my Raspberry now, what seems that I should abandon if I enter the Wolfson/Cirrus world. Do you see any reason for not using the SPI bus for several devices?

                                                 

                                                "But you can use UART and I2C.  If you >really< need SPI, you'll need to use a bridging device between I2C or UART and SPI."

                                                 

                                                I am not sure what kind of bridging device you mean, but if it would be a protocol translator chip, for ex. from SPI to I2C I would definitely avoid this. The I2C interface implementation on the Raspberry PI is quite (I would say "very") limited. It does not allow repeated starts (by the software driver), which already hinders the use of some devices. It also supports only single-master setups (by hardware), so you should carefully design your network. But you may understand if I would stay clear from translating other (and quicker) protocols to I2C.

                                                 

                                                Regarding the UART, it's fine but allows a connection with only one device and you should decide to disable or not the kernel console on it. If you leave it enabled, you have a "single master" only operation (commands only from the connected device). If you disable it, you can implement a duplex communication (where each device can initiate write), but you loose the kernel messages.

                                                 

                                                I am thinking of connecting the RPi to a controller (an Arduino), but even this has issues, knowing the mentioned limitations.

                                                  • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                    tonyhansen

                                                    For SPI, you're making a few assumptions:

                                                     

                                                    • that you can get at the pins for CLK, MOSI and MISO. They are not passed through to the audio card expansion header.
                                                    • that they haven't been reassigned to other uses by the audio card. We don't know the answer to this.

                                                     

                                                    Some people have played around with resoldering some of the audio card connectors to gain access to hidden pins like CLK, MOSI, and MISO. Feel free to try that and let us know how it goes.

                                                     

                                                    With the Wolfson card, because of the P5 spring-loaded connector, there was little leeway to access the pins >from below< the audio card. But with the Cirrus Logic card, I don't see any reason that something like Element 14's RTC shim board wouldn't work.

                                                     

                                                    So you MIGHT be able to do something similar to the shim board to access the CLK/MISO/MOSI pins. They MAY or may NOT work for you as SPI access. Go go for it and let us know what happens.

                                                     

                                                    The thing to remember with the Wolfson and Cirrus Logic audio cards is that they were designed to take advantage of the RPi's capabilities to provide high-quality audio features. To do that, those cards use a LOT of the RPi's resources. Anything else we get to do with the RPi after that is a bonus. :-)

                                                      • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                        gkzsolt

                                                        Hi Tony,

                                                         

                                                        No, I am not making the assumption that the SPI bus pins are exposed. I know they are not, and that is what makes me wonder: why have the designers decided to hide them? In general, there should be no reason for that, except in some (unusual) cases.

                                                        In the schematics I see these 4 pins (MIS, MOSI, SCLK, SS) routed to the corresponding CIF2XX on the WM5102 chip (the RPI pins enter into IC U8, what seems to be a level shifter). From this I conclude that they are used for their purpose, in an SPI protocol and not been "reassigned to other uses", if you meant that. This also means that they can be used for other devices too (except SS). All SPI devices in a module share the same bus pins, ignoring them if their SS slave select pin is not active. So the question remains.

                                                        (I could go and try this with some experiments, but I don't have a Cirrus card yet. I am trying to figure out if it is worth buying one.)

                                                        May I ask if you could search through the "Cirrus Logic Audio Card User Manual.pdf"?

                                                        I agree very much with you in that a Cirrus card takes a lot of RPi's resources. But what worries me more, is the quality of documentation (very poor) and the lack of support. Is somebody at Cirrus reading and taking notice of these discussions? Or is there a place we can show some of these to a competent personnel (thinking of your table, etc.) ?

                                                          • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                            wan1

                                                            In Windows the pdf CLAC user manual also not text searchable (it searches only in small parts of text like tables and command examples).

                                                            Yes, and looks like there is nothing relevant to your question in the manual, any way.

                                                            • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                              tonyhansen

                                                              Zsolt Gere Kiss wrote:

                                                               

                                                              Hi Tony,

                                                               

                                                              No, I am not making the assumption that the SPI bus pins are exposed. I know they are not, and that is what makes me wonder: why have the designers decided to hide them? In general, there should be no reason for that, except in some (unusual) cases.

                                                              In the schematics I see these 4 pins (MIS, MOSI, SCLK, SS) routed to the corresponding CIF2XX on the WM5102 chip (the RPI pins enter into IC U8, what seems to be a level shifter). From this I conclude that they are used for their purpose, in an SPI protocol and not been "reassigned to other uses", if you meant that. This also means that they can be used for other devices too (except SS). All SPI devices in a module share the same bus pins, ignoring them if their SS slave select pin is not active. So the question remains.

                                                              (I could go and try this with some experiments, but I don't have a Cirrus card yet. I am trying to figure out if it is worth buying one.)

                                                              May I ask if you could search through the "Cirrus Logic Audio Card User Manual.pdf"?

                                                              I agree very much with you in that a Cirrus card takes a lot of RPi's resources. But what worries me more, is the quality of documentation (very poor) and the lack of support. Is somebody at Cirrus reading and taking notice of these discussions? Or is there a place we can show some of these to a competent personnel (thinking of your table, etc.) ?

                                                              I cannot speak for the Wolfson designers - I don't know why they made some of their trade offs. I think they've heard loud and clear, though, that GPIO access is important to RPi designers.

                                                               

                                                              However, their bottom line design rule appears to have been to provide access to a high-quality audio board. Everything else seemed to be secondary for them.

                                                               

                                                              If that's your highest priority, as it was mine, then the answer is clear. If something else is more important, then your mileage will vary.

                                                               

                                                              Searchability of PDF files is entirely dependent on the tools used when they are built. These do not appear to be searchable. But they are perfectly valid PDF files.

                                                               

                                                              A number of people have asked similar questions to what you're asking. There's no consensus on any answers yet.

                                                                • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                                  scotth

                                                                  I have put together a complete table to capture the 26/40 way pins for the B and A+/B+ and the use of these pins on both the Wolfson and Cirrus cards. Hopefully this helps bring the information together and highlights the functions and availability of pins on the card. If there are any comments or feedback on the information please provide here, I think this will be useful based on the questions in the forum so I will pass the information on to E14 with the aim of adding to the user manual.

                                                                   

                                                                  26/40 Way Pin allocation and function

                                                                  P1 PinNameModel BModel A+ /B+
                                                                  GPIO (BCM)WAC FunctionGPIO (BCM)CLAC Function
                                                                  13V3 Power
                                                                  25V0 Power
                                                                  3SDA1GPIO2WM8804 I2C - SDAGPIO2WM8804 I2C - SDA
                                                                  EXP/11
                                                                  45V0 Power
                                                                  5SCL1GPIO3WM8804 I2C - SCLKGPIO3WM8804 I2C - SCLK
                                                                  EXP/9
                                                                  6Ground
                                                                  7GPIO_GCLKGPIO4WM5102 MCLK2 (unused)
                                                                  WM8804 MCLK (unused)
                                                                  GPIO4WM5102 MCLK2 (unused)
                                                                  WM8804 MCLK (unused)
                                                                  8TXD0 (UART)GPIO14J8/1GPIO14
                                                                  J8/1
                                                                  9Ground
                                                                  10RXD0 (UART)GPIO15J8/2GPIO15J8/2
                                                                  11GPIO_GEN0GPIO17WM5102 RSTGPIO17WM5102 RST
                                                                  12GPIO_GEN1 (PCM_CLK)GPIO18WM8804 - I2C Address ConfigGPIO18WM5102 AIF PCM - BCLK
                                                                  13GPIO_GEN2GPIO27WM5102 IRQGPIO27WM5102 IRQ
                                                                  14Ground
                                                                  15GPIO_GEN3GPIO22WM5102 LDO EnableGPIO22WM5102 LDO Enable
                                                                  16GPIO_GEN4GPIO23WM8804 - Control I/F ConfigGPIO23WM8804 - Control I/F Config
                                                                  173V3 Power
                                                                  18GPIO_GEN5GPIO24WM5102 GPIO5 (unused)GPIO24WM5102 GPIO5 (unused)
                                                                  19SPI_MOSIGPIO10WM5102 SPI - MOSIGPIO10WM5102 SPI - MOSI
                                                                  20Ground
                                                                  21SPI_MISOGPIO9WM5102 SPI - MISOGPIO9WM5102 SPI - MISO
                                                                  22GPIO_GEN6GPIO25WM5102 GPIO3 (unused)
                                                                  EXP/16
                                                                  GPIO25WM5102 GPIO3 (unused)
                                                                  EXP/16
                                                                  23SPI_SCLKGPIO11WM5102 SPI - SCLK1GPIO11WM5102 SPI - SCLK1
                                                                  24SPI_CE0_NGPIO8WM8804 RSTGPIO8WM8804 RST
                                                                  25Ground
                                                                  26SPI_CE1_NGPIO7WM5102 SPI - CEGPIO7WM5102 SPI - CE
                                                                  27ID_SD GPIO0EEPROM
                                                                  28ID_SC GPIO1EEPROM
                                                                  29GPIO5 GPIO5EXP/14
                                                                  30Ground
                                                                  31GPIO6 GPIO6EXP/17
                                                                  32GPIO12 GPIO12EXP/18
                                                                  33GPIO13 GPIO13WM8804 - I2C Address Config
                                                                  34Ground
                                                                  35GPIO19 (PCM_FS) GPIO19WM5102 AIF PCM - FS
                                                                  36GPIO16 GPIO16EXP/19
                                                                  37GPIO26 GPIO26EXP/20
                                                                  38GPIO20 (PCM_DIN) GPIO20WM5102 AIF PCM - DIN
                                                                  393V3 Power
                                                                  40GPIO21 (PCM_DOUT) GPIO21WM5102 AIF PCM - DOUT
                                                                  Note: Unused functions need to be treated carefully. Although they are not enabled in the current driver
                                                                  they provide scope for increased functionality going forward.

                                                                   

                                                                  P5 Connector (Model B Only)
                                                                  PinNameModel B
                                                                  15V0 Power
                                                                  23V3 Power
                                                                  3PCM_CLKGPIO28
                                                                  4PCM_FSGPIO29
                                                                  5PCM_DINGPIO30
                                                                  6PCM_DOUTGPIO31
                                                                  7Ground
                                                                  8Ground

                                                                   

                                                                  Based on Tony's table of the 8 available GPIOs, I have updated this to include additional information. To clarify the 8 referenced available GPIO are numbers 6 to 13 in the table. I2C and SPI are functions utilised on the card so these can not be changed for other functions.

                                                                  Cirrus Logic
                                                                  Audio Board
                                                                  Pin
                                                                  RPi GPIO
                                                                  Description
                                                                  RPI Alternate
                                                                  Description
                                                                  RPi pin
                                                                  1EX 9GPIO 3SCL I2C5
                                                                  2EX 11GPIO 2SDA1 I2C3
                                                                  3J9-19GPIO 10SPI_MOSI19
                                                                  4J9-21GPIO 9SPI_MISO21
                                                                  5J9-23GPIO 11SPI_SCLK23
                                                                  6EX 14GPIO 5 29
                                                                  7EX 16GPIO 25 22
                                                                  8EX 17GPIO 6 31
                                                                  9EX 18GPIO 12 32
                                                                  10EX 19GPIO 16 36
                                                                  11EX 20GPIO 26 37
                                                                  12J8-1GPIO 14UART TX8
                                                                  13J8-2GPIO 15UART RX10
                                                                    • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                                      wan1

                                                                      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?

                                                                      • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                                        gkzsolt

                                                                        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,

                                                                        • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                                          gkzsolt

                                                                          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

                                                                          • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                                            tonyhansen

                                                                            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.

                                                                            • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                                              jemfiner

                                                                              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

                                                    • Re: Is the Raspberry B+ GPIO passed through with the Cirrus Audio card?
                                                      pitsch

                                                      thanks for documenting the 8 available GPIOs!

                                                       

                                                      will this little TFT display play with the cirrus logic audio card ?

                                                      it uses the SPI pins (SCK, MOSI, MISO, CE0, CE1) as well as GPIO #25

                                                      https://www.adafruit.com/products/2315

                                                      since there is no standard port they need to be rewired

                                                      with six female to female jumper wires and a slim GPIO header


                                                      are there any other recommendable working displays to report?