Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:netzer:spi-master [2014/02/09 14:32] 127.0.0.1 external edit |
en:netzer:spi-master [2015/12/23 17:10] svesch [Communication] |
||
|---|---|---|---|
| Line 54: | Line 54: | ||
| ===== Communication ===== | ===== Communication ===== | ||
| - | Since a [[:connection|connection]] is established, the SPI Master can be used. All received characters from TCP Client but the backslash '\' (Escape) are transparently sent from Netzer to the SPI master module. Escaped characters, which are not supported due the installed firmware version are also transparently conveyed. For a complete listing of the supported escape sequencies see below. The ring buffer has a size of 256 byte for buffering transmission bursts. | + | Since a [[connection|connection]] is established, the SPI Master can be used. |
| + | All received characters from TCP Client but the backslash '\' (Escape) are transparently sent from Netzer to the SPI master module. | ||
| + | Escaped characters, which are not supported due to the installed firmware version are also transparently conveyed. | ||
| + | For a complete listing of the supported escape sequencies see below. The ring buffer has a size of 256 byte for buffering transmission bursts. | ||
| - | The SPI Master module generates for each byte eight clock edges at SPI_CLK and shifts out the data at SPI_MO. At the same time the slave delivers data at SPI_MI (see figure above). The so received byte is sent automatically to the TCP Client. In this direction no escaping is used. | + | The SPI Master module generates for each byte eight clock edges at SPI_CLK and shifts out the data at SPI_MO. |
| + | At the same time the slave delivers data at SPI_MI (see figure above). | ||
| + | The so received byte is sent automatically on the TCP connection. | ||
| + | In this direction no escaping is used. | ||
