Difference between revisions of "Example SPI test"

From wiki.emacinc.com
Jump to: navigation, search
Line 3: Line 3:
 
This is a guide to the <code>spi_test</code> example project included in the EMAC OE SDK.
 
This is a guide to the <code>spi_test</code> example project included in the EMAC OE SDK.
  
−
<code>SPI</code> (Serial Peripheral Interface) is a synchronous full duplex serial data communication standard used to interface many types of memory and I/O devices. <code>SPI</code> requires four lines per slave device connection, three of which are shared across the <code>SPI</code> bus. MISO, MOSI and SCLK are the three shared bus lines and chip selects (CSn) are used to determine which device is the target for communication.
+
<code>SPI</code> works in a master/slave setup. The master is the one that sends the clock pulses. At each pulse, data will be sent and received.
  
−
'''NOTE: This isn't exactly true.  SPI only requires 3 lines, not 4. The 4th line is only required if you have more than one device on the SPI bus; otherwise, you can hard-wire the CS of the only device on the SPI bus so that it is always selected. Additionally, it's not 4 per device from the host processor, because people typically use tricks to reduce the number of lines from the host processor required for the CSn lines.  For example, a 1:2 multiplexer can be used to select device A when the input line is low or device B when the input line is high.  Similarly, a 2:4 multiplexer can be used to select among 4 devices.  With more than 4 devices, an I²C device can often be used which will supply (typically) 8-16 GPIO lines which can be used to feed the chip select lines of the SPI devices while only requiring 2 lines from the host processor. This means that it's usually possible to get away with using no more than 5 lines in total from the host processor.  Since the number of lines required from the host processor is generally what people are most concerned about, because these are the most difficult to come by, the above paragraph should be reworded to clarify this. The SPI Programming page has been marked for revision due to this issue as well.'''
+
<code>SPI</code> is a protocol on four signal lines, it only requires three. The 4th line is only required if you have more than one device on the SPI bus; otherwise, you can hard-wire the chip select of the only device on the <code>SPI</code> bus so that it is always selected.  
 +
 
 +
<code>SPI</code> has a slave select pin. Every device will share the "MISO" (Master Input Slave Output), "MOSI" (Master Output Slave Input), and "Clock" pins, but each device will have its own slave select pin (also know as chip select). This means we can have a virtually unlimited number of devices on the same <code>SPI</code> bus. The slave select pin can be active high or active low depending on the device.
  
 
This procedure provides an overview of how to compile and run the <code>spi_test</code> C example project. This is an example test interface for sending a transaction to an EMAC <code>SPI</code> device interface. It is only relevant if the EMAC <code>SPI</code> device interface is enabled for an external <code>SPI</code> device that is connected to the bus. It assumes familiarity with the C programming language and is intended to be used by experienced programmers who are looking to learn the EMAC SDK.
 
This procedure provides an overview of how to compile and run the <code>spi_test</code> C example project. This is an example test interface for sending a transaction to an EMAC <code>SPI</code> device interface. It is only relevant if the EMAC <code>SPI</code> device interface is enabled for an external <code>SPI</code> device that is connected to the bus. It assumes familiarity with the C programming language and is intended to be used by experienced programmers who are looking to learn the EMAC SDK.

Revision as of 16:39, 25 February 2014

TODO: {{#todo:Buggy (2.21.14-17:40->BS+);(2.24.14-13:00->MD-)|Brian Serrano|oe 4,md,Buggy,bs}}

This is a guide to the spi_test example project included in the EMAC OE SDK.

SPI works in a master/slave setup. The master is the one that sends the clock pulses. At each pulse, data will be sent and received.

SPI is a protocol on four signal lines, it only requires three. The 4th line is only required if you have more than one device on the SPI bus; otherwise, you can hard-wire the chip select of the only device on the SPI bus so that it is always selected.

SPI has a slave select pin. Every device will share the "MISO" (Master Input Slave Output), "MOSI" (Master Output Slave Input), and "Clock" pins, but each device will have its own slave select pin (also know as chip select). This means we can have a virtually unlimited number of devices on the same SPI bus. The slave select pin can be active high or active low depending on the device.

This procedure provides an overview of how to compile and run the spi_test C example project. This is an example test interface for sending a transaction to an EMAC SPI device interface. It is only relevant if the EMAC SPI device interface is enabled for an external SPI device that is connected to the bus. It assumes familiarity with the C programming language and is intended to be used by experienced programmers who are looking to learn the EMAC SDK.

For more information about the SPI protocol, see the following page: http://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus

The spi_test project builds one executable: spi_test.

Opening, Building, and Uploading the Project Files

For information on opening the project from within Eclipse, please see, Importing the EMAC OE SDK Projects with Eclipse. Then, follow Using the EMAC OE SDK Projects with Eclipse for information on how to build, upload, and execute the example.

The example is located in the path below: 

developer@ldc:~$ path/to/EMAC/SDK/projects/spi

Alternatively, the Makefile can be used with the make command from the command-line to build and upload the example. For more information on this method, please see, Using EMAC OE SDK Example Projects.

Usage and Behavior

Hardware Requirements

The spi_test C example project will run on any EMAC carrier board which has an SPI interface (see also the EMAC SPI Programming page).

Using spi_test

The spi_test program is executed from the console. It takes three parameters. 

root@emac-oe~:$ ./spi_test device length mosi
  • device: Name of the spi device node.
  • length: Length of spi transactions in bytes.
  • mosi: Hex value to be transmitted in hexadecimal.

This example command was run on an EMAC SoM-150ES carrier board. Test results will be displayed in the terminal. 

root@emac-oe~:$ ./spi_test /dev/mcp3208 1 12

MOSI  MISO
 12  : 00

After running the ./spi_test /devmcp3208 1 12 command, the program displays MOSI in hexadecimal and then outputs MISO.

NOTE: A better description of the output is needed, along with more examples of using it. There should be at least 3-5 examples. As an example, you can see the way I demonstrated usage of the MySQL commandline on our Liferay site.

Summary

The spi_test C example project demonstrates how to use the SPI device. SPI is simply a way to send data from device to device in a serial fashion (bit by bit). SPI provide good support for communication with slow peripheral devices that are accessed intermittently. This protocol is used for things like SD memory cards, MP3 decoders, memory devices, and other high speed applications.

SPI can operate at extremely high speeds (million of bytes per second), which may be too fast for some devices. It can also achieve significantly higher data rates than I²C device. SPI is better suited than I²C for applications that are naturally thought of as data streams (as opposed to reading and writing addressed locations in a slave device).

Retrieved from "https://wiki.emacinc.com/index.php?title=Example_SPI_test&oldid=3318"