Example i2c test - Revision history

Nperkins at 19:21, 30 November 2022

2022-11-30T19:21:00Z

Nperkins: /* Using i2c_test */

2022-10-14T17:08:47Z

‎Using i2c_test

Nperkins at 16:59, 14 October 2022

2022-10-14T16:59:44Z

Btisler: Added OE5 instructions

2020-09-25T16:21:39Z

Added OE5 instructions

Mgloff: Fixed I2C page link.

2015-11-20T17:06:07Z

Fixed I2C page link.

Mdean: Marked Buggy due to too many issues.

2015-11-10T22:07:40Z

Marked Buggy due to too many issues.

Mdean: Fixed formatting issues.

2015-11-10T18:51:19Z

Fixed formatting issues.

Show changes

Mdean: /* Test Options */ Corrected punctuation and made sentence more clear.

2014-04-30T16:30:20Z

‎Test Options: Corrected punctuation and made sentence more clear.

Bserrano at 14:45, 30 April 2014

2014-04-30T14:45:55Z

Bserrano at 14:16, 25 April 2014

2014-04-25T14:16:46Z

@@ Line 21: / Line 21: @@
 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 28: / Line 28: @@
 ===Using i2c_test===
-The <code>i2c_test</code> program is executed from the console. If using the Ipac-9x25 it takes an optional argument which is the string representing the device path. By default, "/dev/i2c-1" is set, but if another device path needs to be used, append that to the command.
+The <code>i2c_test</code> program is executed from the console. If using the iPac9x25 it takes an optional argument which is the string representing the device path. By default, "/dev/i2c-1" is set, but if another device path needs to be used, append that to the command.
 {{cli |./i2c_test <optional device_path>}}

@@ Line 28: / Line 28: @@
 ===Using i2c_test===
-The <code>i2c_test</code> program is executed from the console. It takes no parameters.
+The <code>i2c_test</code> program is executed from the console. If using the Ipac-9x25 it takes an optional argument which is the string representing the device path. By default, "/dev/i2c-1" is set, but if another device path needs to be used, append that to the command.
-{{cli |./i2c_test}}
+{{cli |./i2c_test <optional device_path>}}
 A menu will appear in the terminal:

@@ Line 10: / Line 10: @@
 The <code>i2c_test</code> project builds one executable: <code>i2c_test</code>.
-== 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.
+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]].
-In OE 5, the project may be opened from within Qt Creator instead of Eclipse.
+====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 ==
 === Hardware Requirements ===

@@ Line 21: / Line 21: @@
 === Hardware Requirements ===
-The <code>i2c_test</code> C example project will run on any EMAC carrier board which has an <code>I²C</code> interface (see also the [http://wikidev.emacinc.com/wiki/EMAC_I%C2%B2C_Programming EMAC I²C Programming] page).
+The <code>i2c_test</code> C example project will run on any EMAC carrier board which has an <code>I²C</code> interface (see also the [[EMAC_I²C_Programming | EMAC I²C Programming]] page).
 ===Using i2c_test===

@@ Line 1: / Line 1: @@
-{{todo|InProgress (11.14.13-13:25->JG+);(11.14.13-15:45->MD-);(01.30.14-16:20->BS+);(01.30.14-18:30->MD-);(11.10.2015-12:50->MD+)|Brian Serrano|project=oe 4,oe 5,md,InProgress,bs}}
+{{todo|Buggy (11.14.13-13:25->JG+);(11.14.13-15:45->MD-);(01.30.14-16:20->BS+);(01.30.14-18:30->MD-);(11.10.2015-12:50->MD+)|Brian Serrano|project=oe 4,oe 5,md,Buggy,bs}}
 This is a guide to the <code>i2c_test</code> example project included in the EMAC OE SDK.
@@ Line 7: / Line 7: @@
 This procedure provides an overview of how to compile and run the <code>i2c_test</code> C example project. This is an example test interface for reading/writing to the Linux <code>I²C</code> device interface. It is only relevant if the <code>I²C</code> device interface is enabled and an external <code>I²C</code> device 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 protocol see the following page: http://en.wikipedia.org/wiki/I²C
+For more information about the protocol see the following page: http://www.nxp.com/documents/user_manual/UM10204.pdf
 The <code>i2c_test</code> project builds one executable: <code>i2c_test</code>.

@@ Line 192: / Line 192: @@
 The RTC Clock slave address in binary is 1010001 (58 in Hexadecimal).
-{{imbox |type = content | text = The slave address must be shifted to the right }}
+{{imbox |type = content | text = The slave address must be shifted to the right one bit. }}
 <syntaxhighlight lang=console>

@@ Line 165: / Line 165: @@
 === Hardware Requirements ===
 The <code>i2c_test</code> C Real-World example project will be running on an EMAC SOM-210ES carrier board. This example will be communicating with the RTC clock on the SOM-3517M.
 === Using Real-World Example i2c_test ===
@@ Line 171: / Line 173: @@
   root@emac-oe~:$ ./i2c_test
 == Summary ==
 The <code>i2c_test</code> C example project writes and reads bytes to a selected register on the <code>I²C</code> device.