Hello !
Trace:

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:iot-open:embeddedcommunicationprotocols2:spi [2023/11/21 23:37] – pczekalskien:iot-open:embeddedcommunicationprotocols2:spi [2024/05/27 10:16] (current) – [QSPI] ktokarz
Line 1: Line 1:
 ====== SPI ====== ====== 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}}). 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> <table RefTabSPI1>
Line 12: Line 13:
 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}}. 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> <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> <caption>Sample SPI connection</caption>
 </figure>   </figure>  
Line 36: Line 37:
  
 <figure RefSPIPic2> <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> <caption>Sample SPI timing</caption>
 </figure>   </figure>  
Line 44: Line 45:
  
 <figure RefSPIPic3> <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> <caption>Sample QSPI connection</caption>
 </figure>   </figure>  
  
en/iot-open/embeddedcommunicationprotocols2/spi.1700609854.txt.gz · Last modified: 2023/11/21 23:37 by pczekalski
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0