Example SPI test - Revision history

Nperkins at 19:22, 30 November 2022

2022-11-30T19:22:30Z

Nperkins at 17:28, 14 October 2022

2022-10-14T17:28:27Z

Nperkins at 17:27, 14 October 2022

2022-10-14T17:27:46Z

Btisler: Added OE5 instructions

2020-09-25T16:24:24Z

Added OE5 instructions

Mdean: Marked as complete.

2014-09-14T02:38:07Z

Marked as complete.

Mdean: /* The dots should be on the lines, not near them, in the diagram. The C dot should be between the ground symbol and the bottom of the pot (on the line); likewise, the A dot should be on the line between the Vcc rail symbol and the top of the pot. Th...

2014-09-14T02:36:50Z

/* The dots should be on the lines, not near them, in the diagram. The C dot should be between the ground symbol and the bottom of the pot (on the line); likewise, the A dot should be on the line between the Vcc rail symbol and the top of the pot. Th...

Bserrano at 21:49, 10 September 2014

2014-09-10T21:49:56Z

Mdean: Updated TODO tag.

2014-09-09T22:22:47Z

Updated TODO tag.

Mdean: /* The dots should be on the lines, not near them, in the diagram. The C dot should be between the ground symbol and the bottom of the pot (on the line); likewise, the A dot should be on the line between the Vcc rail symbol and the top of the pot. Th...

2014-09-09T22:16:09Z

Mdean: /* Your parameters are inconsistent. Here, you name them device and length, but down below, you refer to them as device and channel: Fixed */

2014-09-09T22:09:00Z

‎Your parameters are inconsistent. Here, you name them device and length, but down below, you refer to them as device and channel: Fixed

@@ Line 27: / Line 27: @@
 Alternatively, the <code>CMakefile.txt</code> can be used with the <code>cmake</code> command from the commandline to build and upload the example.  For information on this method, please see [[Getting_Started_with_the_EMAC_OE_SDK#Target_Machine_Compiling | Getting Started with the EMAC OE SDK]].
 == Usage and Behavior ==
 ===Hardware Requirements===

@@ Line 97: / Line 97: @@
 In order to run these examples on the board, either follow the schematic from figure 4 or use part MIKROE-304.
 {|style="margin: 0 auto;"
-| [[File:Potentiometer3.jpg|left|thumb|300px|alt=A potentiometer circuit.|Figure 1: Potentiometer Circuit]]
+|[[File:Spi Test Schematic.png|thumb|Figure 4: Schematic used to set up spi test for iPac9x25]]
 <br clear=all>
 |}

@@ Line 93: / Line 93: @@
 Due to ADC noise, you may see the values fluctuate slightly from one run to the next.  This is normal behavior.  This fluctuation can be more severe with some potentiometers than it is with others; some potentiometers are more prone to picking up noise.  The noise will also be more severe with longer wires, due to transmission line effects.  Eliminating noise is typically the greatest challenge in high resolution A/D conversion (especially at 18 bit and above), so you should expect to see some noise when performing an informal test such as this.
-The <code>spi_test</code> program is executed from the console. It takes three parameters.
+==Updates for iPac9x25==
+In order to run these examples on the board, either follow the schematic from figure 4 or use part MIKROE-304.
- root@emac-oe~:$ ./spi_test device length mosi
+{|style="margin: 0 auto;"
+| [[File:Potentiometer3.jpg|left|thumb|300px|alt=A potentiometer circuit.|Figure 1: Potentiometer Circuit]]
-:* <code>device</code>: Name of the <code>spi</code> device node.
+[[File:Spi Test Schematic.png|thumb|Schematic used to set up spi test for iPac9x25]]
-:* <code>length</code>: Length of <code>spi</code> transactions in bytes.
+<br clear=all>
-:* <code>mosi</code>: Hex value to be transmitted in hexadecimal.
+|}
 == Summary ==
 The <code>indexed_atod_test</code> C example project demonstrates how to use a 12 bit A/D converter chip (mcp3208) with SPI Serial Interface. <code>SPI</code> is simply a way to send data from device to device in a serial fashion (bit by bit). <code>SPI</code> provides good support for communication with peripheral devices that are accessed intermittently.

@@ Line 15: / Line 15: @@
 The <code>spi_test</code> project builds one executable: <code>spi_test</code>.
-== Opening, Building, and Uploading the Project Files ==
+== 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.
+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:
+Alternatively, the <code>Makefile</code> can be used with the <code>make</code> command from the commandline to build and upload the example.  For information on this method, please see [[Using EMAC OE SDK Example Projects]].
-<syntaxhighlight lang=console>
+====EMAC SDK 5.X====
-Alternatively, the <code>Makefile</code> can be used with the <code>make</code> 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]].
+For information on opening the project from within QtCreator, please see [[Getting_Started_With_Qt_Creator#Adding_Source_Files | QtCreator: Adding Source Files]].  Then, follow [[Getting Started With Qt Creator]] for information on how to build, upload and execute the example.
 == Usage and Behavior ==

← Older revision		Revision as of 02:38, 14 September 2014
Line 1:		Line 1:
−	{{todo\|Buggy (2.21.14-17:40->BS+);(2.24.14-13:00->MD-)(2.28.14-17:48->BS+)(03.10.14-13:30->MD-)(08.27.14-16:55->BS+)(09.09.14-17:20->MD-)(09.10.14-17:00->BS+) \|Brian Serrano\|project=oe 4,md,~~Buggy~~,bs}}	+	{{todo\|Buggy (2.21.14-17:40->BS+);(2.24.14-13:00->MD-)(2.28.14-17:48->BS+)(03.10.14-13:30->MD-)(08.27.14-16:55->BS+)(09.09.14-17:20->MD-)(09.10.14-17:00->BS+)(09.13.14-21:40->MD+) \|Brian Serrano\|project=oe 4,md,Complete,bs}}

	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.

@@ Line 46: / Line 46: @@
 |}
-=== The dots should be on the lines, not near them, in the diagram.  The C dot should be between the ground symbol and the bottom of the pot (on the line); likewise, the A dot should be on the line between the Vcc rail symbol and the top of the pot.  The B symbol should be on the line just to the right of the wiper of the pot. The dots on the mechanical drawing of the pot look strange.  Normally, the mechanical drawing will have a drawing of the physical shape of the terminals rather than a schematic representation of them.  It would be better to give the mechanical drawing legs, and label the legs A, B, and C.  This is an example of how you would normally expect to see a schematic like this drawn: [https://dlnmh9ip6v2uc.cloudfront.net/assets/6/3/e/5/e/511ac8f5ce395f5846000000.png Schematic]  (taken from [https://learn.sparkfun.com/tutorials/voltage-dividers this page]).  You currently have the dots on top of the symbols, which doesn't look right (especially for the Vcc rail symbol).===
+This example command was run on an EMAC SoM-150ES carrier board with a SoM-9G20M. This test uses a potentiometer for input to the A/D. You will be communicating with the mcp3208 chip, which is an 8-channel 12-bit A/D converter with SPI Serial Interface. Figure 1 provides a potentiometer test circuit for help on connection to the SoM-150ES carrier board.  A circuit like this is recommended for familiarizing oneself with the A/D code before connecting the actual device to be measured by the A/D.
 Before running the command in the terminal, you will need to connect the potentiometer to the carrier board as diagrammed. Figure 2 shows where to connect the potentiometer on Header 8 of the SoM-150ES. You will be focusing on CARR_ANL_1 for this example.
@@ Line 78: / Line 76: @@
 [[File:Hdr8_chan6.jpg|center|thumb|250px|alt=HDR8 Analog I/O|Figure 3: HDR8 ANALOG I/O]]<br clear=all>
-Before doing example 3, you'll want to put the wiper (B) wire on pin 9 of the SoM-150ES carrier board. Figure 3 shows that pin 9 is CARR_ANL_6. Turn the potentiometer counter-clockwise about half way. You'll see how the values on channel 6 will change when running the command below. Test results will be displayed in the terminal.
+Before doing example 3, you'll want to put the wiper (B) wire on pin 9 of the SoM-150ES carrier board. Figure 3 shows that pin 9 is CARR_ANL_6. Turn the potentiometer counter-clockwise about half way. You will see how the values on channel 6 will change when running the command below. Test results will be displayed in the terminal.
 <syntaxhighlight lang=console>

@@ Line 1: / Line 1: @@
-{{todo|Buggy (2.21.14-17:40->BS+);(2.24.14-13:00->MD-)(2.28.14-17:48->BS+)(03.10.14-13:30->MD-)(08.27.14-16:55->BS+)(09.09.14-17:20->MD-) |Brian Serrano|project=oe 4,md,Buggy,bs}}
+{{todo|Buggy (2.21.14-17:40->BS+);(2.24.14-13:00->MD-)(2.28.14-17:48->BS+)(03.10.14-13:30->MD-)(08.27.14-16:55->BS+)(09.09.14-17:20->MD-)(09.10.14-17:00->BS+) |Brian Serrano|project=oe 4,md,Buggy,bs}}
 This is a guide to the <code>spi_test</code> example project included in the EMAC OE SDK.
@@ Line 42: / Line 42: @@
 {|style="margin: 0 auto;"
-| [[File:Potentiometer2.jpg|left|thumb|300px|alt=A potentiometer circuit.|Figure 1: Potentiometer Circuit]]
+| [[File:Potentiometer3.jpg|left|thumb|300px|alt=A potentiometer circuit.|Figure 1: Potentiometer Circuit]]
 | [[File:Hdr8_chan1.jpg|right|thumb|250px|alt=HDR8 Analog I/O|Figure 2: HDR8 ANALOG I/O]]<br clear=all>
 |}

← Older revision		Revision as of 22:22, 9 September 2014
Line 1:		Line 1:
−	{{todo\|Buggy (2.21.14-17:40->BS+);(2.24.14-13:00->MD-)(2.28.14-17:48->BS+)(03.10.14-13:30->MD-)(08.27.14-16:55->BS+) \|Brian Serrano\|project=oe 4,md,Buggy,bs}}	+	{{todo\|Buggy (2.21.14-17:40->BS+);(2.24.14-13:00->MD-)(2.28.14-17:48->BS+)(03.10.14-13:30->MD-)(08.27.14-16:55->BS+)(09.09.14-17:20->MD-) \|Brian Serrano\|project=oe 4,md,Buggy,bs}}

	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.

@@ Line 46: / Line 46: @@
 |}
-=== The dots should be on the lines, not near them, in the diagram.  The C dot should be between the ground symbol and the bottom of the pot (on the line); likewise, the A dot should be on the line between the Vcc rail symbol and the top of the pot.  The B symbol should be on the line just to the right of the wiper of the pot. The dots on the mechanical drawing of the pot look strange.  Normally, the mechanical drawing will have a drawing of the physical shape of the terminals rather than a schematic representation of them.  It would be better to give the mechanical drawing legs, and label the legs A, B, and C. : Fixed  ===
+=== The dots should be on the lines, not near them, in the diagram.  The C dot should be between the ground symbol and the bottom of the pot (on the line); likewise, the A dot should be on the line between the Vcc rail symbol and the top of the pot.  The B symbol should be on the line just to the right of the wiper of the pot. The dots on the mechanical drawing of the pot look strange.  Normally, the mechanical drawing will have a drawing of the physical shape of the terminals rather than a schematic representation of them.  It would be better to give the mechanical drawing legs, and label the legs A, B, and C.  This is an example of how you would normally expect to see a schematic like this drawn: [https://dlnmh9ip6v2uc.cloudfront.net/assets/6/3/e/5/e/511ac8f5ce395f5846000000.png Schematic]  (taken from [https://learn.sparkfun.com/tutorials/voltage-dividers this page]).  You currently have the dots on top of the symbols, which doesn't look right (especially for the Vcc rail symbol).===
 This example command was run on an EMAC SoM-150ES carrier board with a SoM-9G20M. This test uses a potentiometer for input to the A/D. You'll be communicating to the mcp3208 chip, which is an 8-channel 12-bit A/D converter with SPI Serial Interface. Figure 1 provides a potentiometer test circuit for help on connection to the SoM-150ES carrier board.  A circuit like this is recommended for familiarizing oneself with the A/D code before connecting the actual device to be measured by the A/D.
@@ Line 139: / Line 139: @@
 </syntaxhighlight>
 In this third example, the results change again because of the different length and hex value. -->
 == Summary ==
 The <code>indexed_atod_test</code> C example project demonstrates how to use a 12 bit A/D converter chip (mcp3208) with SPI Serial Interface. <code>SPI</code> is simply a way to send data from device to device in a serial fashion (bit by bit). <code>SPI</code> provides good support for communication with peripheral devices that are accessed intermittently.

← Older revision		Revision as of 22:09, 9 September 2014
Line 36:		Line 36:
	The <code>indexed_atod_test</code> program is executed from the console. It takes two parameters.		The <code>indexed_atod_test</code> program is executed from the console. It takes two parameters.

−	~~=== Your parameters are inconsistent. Here, you name them ''device'' and ''length'', but down below, you refer to them as ''device'' and ''channel'': Fixed ===~~
	root@emac-oe~:$ ./indexed_atod_test device channel		root@emac-oe~:$ ./indexed_atod_test device channel