This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:iot-open:embeddedcommunicationprotocols2:spi [2023/11/23 13:55] – pczekalski | en:iot-open:embeddedcommunicationprotocols2:spi [2024/05/27 10:16] (current) – [QSPI] ktokarz | ||
|---|---|---|---|
| Line 13: | 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> | 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> | ||
| <figure RefSPIPic1> | <figure RefSPIPic1> | ||
| - | {{ : | + | {{ : |
| < | < | ||
| </ | </ | ||
| Line 24: | Line 24: | ||
| * communication interfaces (e.g. Ethernet, WiFi), | * communication interfaces (e.g. Ethernet, WiFi), | ||
| * and many others. | * and many others. | ||
| - | |||
| - | |||
| Due to different hardware implementations, | Due to different hardware implementations, | ||
| <table RefSPITab2> | <table RefSPITab2> | ||
| Line 39: | Line 37: | ||
| <figure RefSPIPic2> | <figure RefSPIPic2> | ||
| - | {{ : | + | {{ : |
| < | < | ||
| </ | </ | ||
| Line 47: | Line 45: | ||
| <figure RefSPIPic3> | <figure RefSPIPic3> | ||
| - | {{ : | + | {{ : |
| < | < | ||
| </ | </ | ||