Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| en:netzer:spi-master [2015/12/23 17:10] – [Communication] svesch | en:netzer:spi-master [2025/06/11 20:42] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 123: | Line 123: | ||
| | T | 0x54 | Wait 1\ ms till processing of the next character. | 1.5 | | | T | 0x54 | Wait 1\ ms till processing of the next character. | 1.5 | | ||
| | All others | Character is transparently transmitted. | | | All others | Character is transparently transmitted. | | ||
| + | |||
| + | |||
| + | ===== SPI master in single slave operation ===== | ||
| + | |||
| + | For using this SPI master in a single slave environment this example is provided here. | ||
| + | We assume that the slave is connected with the SPI_CS wire like shown below. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | The SPI_CS shall be low active - a low level selects the slave. | ||
| + | The pull up resistor at CS is needed to prevent false selection. | ||
| + | This may occur on power up if CS is not driven by Netzer. | ||
| + | The pull up resistor at SPI_MI is needed to prevent floating in case the slave is not selected and therefore the pin is not driven. | ||
| + | |||
| + | The data string < | ||
| + | |||
| + | The command for controlling the SPI_CS line is an escape sequence consisting of two bytes: | ||
| + | < | ||
| + | < | ||
| + | |||
| + | The final code together: | ||
| + | < | ||