Differences

This shows you the differences between two versions of the page.

--- en:iot-open:embeddedcommunicationprotocols2:spi [2023/11/21 21:43] – pczekalski
+++ en:iot-open:embeddedcommunicationprotocols2:spi [2024/05/27 10:16] (current) – [QSPI] ktokarz
@@ Line 1: / Line 1: @@
 ====== SPI ======
+{{:en:iot-open:czapka_b.png?50| General audience classification icon }}{{:en:iot-open:czapka_e.png?50| General audience classification icon }}\\
 One of the most popular interfaces to connect different external devices is SPI (Serial Peripheral Interface). It is a synchronous serial interface and protocol that can transmit data with speeds up to 20 Mbps. SPI is used to communicate microcontrollers with one or more peripheral devices over short distances – usually internally in the device. High transmission speed enables SPI to be suitable even for sending animated video data to colourful displays. In SPI connection, there is always one master device, in most cases the microcontroller (μC) that controls the transmission, and one or more slave devices – peripherals. To communicate, SPI uses three lines common to all connected devices and one enabling line for every slave element (table {{ref>RefTabSPI1}}).
 <table RefTabSPI1>
 <caption>SPI Lines</caption>
-^ <fs xx-small>Line</fs> ^ <fs xx-small>Description</fs> ^ <fs xx-small>Direction</fs> ^
+^ Line ^ Description ^ Direction ^
-| <fs xx-small>MISO</fs> | <fs xx-small>Master In Slave Out</fs> | <fs xx-small>peripheral -> μC</fs> |
+| MISO | Master In Slave Out | peripheral -> μC |
-| <fs xx-small>MOSI</fs> | <fs xx-small>Master Out Slave In</fs> | <fs xx-small>μC -> peripheral</fs> |
+| MOSI | Master Out Slave In | μC -> peripheral |
-| <fs xx-small>SCK</fs> | <fs xx-small>Serial Clock</fs> | <fs xx-small>μC -> peripheral</fs> |
+| SCK | Serial Clock | μC -> peripheral |
-| <fs xx-small>SS</fs> | <fs xx-small>Slave Select</fs> | <fs xx-small>μC -> peripheral</fs> |
+| SS | Slave Select | μC -> peripheral |
 </table>
 The MISO line is intended to send bits from slave to master, the MOSI wire transmits data from master to slave, and the SCK line sends clock pulses that synchronise data transmission. The master device always generates the clock signal.
 Every SPI-compatible device has the SS (Slave Select) input that enables communication in this specific device. Master is responsible for generating this enable signal – separately for every slave in the system, as present in figure {{ref>RefSPIPic1}}.
 <figure RefSPIPic1>
-{{ :en:iot-open:embeddedcommunicationprotocols2:spi_diagram.png?nolink&500 | Sample SPI connections }}
+{{ :en:iot-open:embeddedcommunicationprotocols2:spi_diagram.png?500 | Sample SPI connections }}
 <caption>Sample SPI connection</caption>
 </figure>
@@ Line 26: / Line 27: @@
 <table RefSPITab2>
 <caption>SPI Modes</caption>
-^ <fs xx-small>Mode</fs> ^ <fs xx-small>Clock polarity</fs> ^ <fs xx-small>Clock phase</fs> ^ <fs xx-small>Idle state</fs> ^ <fs xx-small>Active state</fs> ^ <fs xx-small>Output edge</fs> ^ <fs xx-small>Data capture</fs> ^
+^ Mode ^ Clock polarity ^ Clock phase ^ Idle state ^ Active state ^ Output edge ^ Data capture ^
-| <fs xx-small>mode 0</fs> | <fs xx-small>0</fs> | <fs xx-small>0</fs> | <fs xx-small>0</fs> | <fs xx-small>1</fs> | <fs xx-small>falling</fs> | <fs xx-small>rising</fs> |
+| mode 0 | 0 | 0 | 0 | 1 | falling | rising |
-| <fs xx-small>mode 1</fs> | <fs xx-small>0</fs> | <fs xx-small>1</fs> | <fs xx-small>0</fs> | <fs xx-small>1</fs> | <fs xx-small>rising</fs> | <fs xx-small>falling</fs> |
+| mode 1 | 0 | 1 | 0 | 1 | rising | falling |
-| <fs xx-small>mode 2</fs> | <fs xx-small>1</fs> | <fs xx-small>0</fs> | <fs xx-small>1</fs> | <fs xx-small>0</fs> | <fs xx-small>rising</fs> | <fs xx-small>falling</fs> |
+| mode 2 | 1 | 0 | 1 | 0 | rising | falling |
-| <fs xx-small>mode 3</fs> | <fs xx-small>1</fs> | <fs xx-small>1</fs> | <fs xx-small>1</fs> | <fs xx-small>0</fs> | <fs xx-small>falling</fs> | <fs xx-small>rising</fs> |
+| mode 3 | 1 | 1 | 1 | 0 | falling | rising |
 </table>
@@ Line 36: / Line 37: @@
 <figure RefSPIPic2>
-{{ :en:iot-open:embeddedcommunicationprotocols2:spi_timing.png?nolink&500 | Sample SPI timing }}
+{{ :en:iot-open:embeddedcommunicationprotocols2:spi_timing.png?500 | Sample SPI timing }}
 <caption>Sample SPI timing</caption>
 </figure>
@@ Line 44: / Line 45: @@
 <figure RefSPIPic3>
-{{ :en:iot-open:embeddedcommunicationprotocols2:qspi_diagram.png?nolink&500 | Sample QSPI connections }}
+{{ :en:iot-open:embeddedcommunicationprotocols2:qspi_diagram.png?500 | Sample QSPI connections }}
 <caption>Sample QSPI connection</caption>
 </figure>

en/iot-open/embeddedcommunicationprotocols2/spi.1700603001.txt.gz · Last modified: 2023/11/21 21:43 by pczekalski