TS-7670 SPI: Difference between revisions

From embeddedTS Manuals
(Created page with "The SBC is utilizing the CPU SPI ports for the SD cards, therefore there is no available SPI peripheral in CPU. SPI transactions must be bitbanged because of this. Please se...")
 
(Cleaned up SPI section with more information)
 
Line 1: Line 1:
The SBC is utilizing the CPU SPI ports for the SD cards, therefore there is no available SPI peripheral in CPU.  SPI transactions must be bitbanged because of thisPlease see the [[#DIO|DIO]] section for more information on manipulating DIO pins.
This SBC utilizes all of the i.MX28 CPU SPI ports for the SD cards, therefore there is no externally available SPI peripheral from the CPU.  Because of this, bitbanging is strongly recommended for any attached peripherals that would utilize SPI.
 
Technologic Systems recommends using direct bitbanging of SPI pins from userspace to drive an SPI interfaceSee the [[#DIO|DIO section]] for further information on manipulating DIO pins.
 
Another option is to implement spi-gpio in linux.  This allows for a SPI physical interface on GPIO pins, but uses the kernel SPI software interface to read and write data on the SPI bus.  See linux kernel documentation, spi-gpio, and spidev for more information on this.

Latest revision as of 16:02, 6 June 2016

This SBC utilizes all of the i.MX28 CPU SPI ports for the SD cards, therefore there is no externally available SPI peripheral from the CPU. Because of this, bitbanging is strongly recommended for any attached peripherals that would utilize SPI.

Technologic Systems recommends using direct bitbanging of SPI pins from userspace to drive an SPI interface. See the DIO section for further information on manipulating DIO pins.

Another option is to implement spi-gpio in linux. This allows for a SPI physical interface on GPIO pins, but uses the kernel SPI software interface to read and write data on the SPI bus. See linux kernel documentation, spi-gpio, and spidev for more information on this.