Go Down

Topic: Which pins to use for SPI communication of an "Arduino nano v3"? (Read 21747 times) previous topic - next topic


Nov 13, 2012, 08:11 pm Last Edit: Nov 13, 2012, 08:26 pm by xalpage Reason: 1
Dear everybody,

I have an   arduino nano V3                     and trying to connect to an
               SPI LCD TFT Module with MicroSD

After seeing all the post in arduino forum to find which pins to connect(miso,mosi,cslk,ss), I did not find anything but

Could you tell me which pins to use in my nano for SPI communication(as a master)?
(Example    mosi=pin? miso=pin? sclk=pin? ss=pin?)

Also which pins to use of the SPI TFT LDC Module to pair it with nano?
(Example    nano's mosi pin  pairs with LCD's  miso pin?   or   nano's miso pin pairs with LCD's mosi pin?   etc.)

And at last can I use the both the LCD and the SD card with just with one and only arduino nano?

(What I am really trying to learn is how to use an arduino nano to load photos from the SD card  to the TFT screen. And preferably without burning anything)

Thank you all in advanced.


Something wrong with going to the source?
SPI: 10 (SS), 11 (MOSI), 12 (MISO), 13 (SCK). These pins support SPI communication, which, although provided by the underlying hardware, is not currently included in the Arduino language.

But the SPI library does include the support.
The art of getting good answers lies in asking good questions.


SS, also known as CS or "chip select" can be any available digital pin, and you can communicate with several SPI components by having each connected to a different pin for CS and having software pull one down to activate that component and pull the others up to disactivate the others.  All SPI devices share the same pins for the other 3.  Do read through the documentation for the Nano and for your display board, and work through the sample programs.  There are other shields around that have 2 SPI links, e.g. a CAN shield that also has a micro card slot, and there's lots of documentation and examples for that.


Thank you for the response.
PaulS next time I should read the documentation more carefully.
LROBBINS you have been very helpful.

Go Up