This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| spi_interface [2011/11/15 09:50] – ab | spi_interface [2012/02/06 11:18] – ab | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| Unfortunately there are many different protocol implementations used in the industry which makes it difficult to provide a generic SPI driver VI.\\ | Unfortunately there are many different protocol implementations used in the industry which makes it difficult to provide a generic SPI driver VI.\\ | ||
| For this reason **ZBrain-SDK does not support generic SPI access** through LabVIEW VIs.\\ | For this reason **ZBrain-SDK does not support generic SPI access** through LabVIEW VIs.\\ | ||
| - | Schmid Engineerig offers a **SPI driver design in service** for custom SPI devices, please ask for an detailed offer.\\ | + | Schmid Engineerig offers a **SPI driver design in service** for custom |
| \\ | \\ | ||
| - | Refer to [[DEV-Z48-C1]] for examples of SPI devices attached to a core module. | + | Refer to [[DEV-Z48-C1]] for examples of SPI devices attached to a core module.\\ |
| + | \\ | ||
| + | The TWI bus (I2C) might be an option offering generic VI support, allowing the user to access almost every devices manually.\\ | ||
| + | [[supported_twi_devices]] | ||