Embedded System I2C Tutorial - Revision history

Sree at 20:06, 25 January 2019

2019-01-25T20:06:48Z

2017-03-02T02:30:14Z

‎Assignment Outline

2017-03-01T03:50:59Z

‎Assignment

2017-03-01T03:28:06Z

‎Assignment Outline

2017-03-01T03:27:50Z

‎I2C

2017-03-01T03:23:35Z

‎Assignment

2017-03-01T03:23:05Z

‎Assignment

2017-03-01T03:22:17Z

‎Assignment

2016-10-14T04:40:19Z

2015-03-08T05:26:33Z

‎I2C Slave State Machine Planning

@@ Line 1: / Line 1: @@
 == Theory of Operation ==
 I2C is prounced "eye-squared see".  It is also known as "TWI" because of the intial patent issues of this BUS.  This is a popular, low throughput (100-1000Khz), half-duplix BUS that only uses two wires regardless of how many devices are on this BUS.  Many sensors use this BUS because of its ease of adding to a system.
@@ Line 204: / Line 211: @@
 *  Follow your diagram and figure out how to make the I2C slave state machine walk through to read and write registers
 <BR/>

@@ Line 140: / Line 140: @@
 === I2C Code Assignment ===
 ==== Assignment Outline ====
-<b>This is a group assignment; submit one copy of code per team and put down the names of your group members as part of the source code you turn in.  Only turn in the new code you added, not the entire file.</b>
+<b>This is a group of two assignment; submit one copy of code per team and put down the names of your group members as part of the source code you turn in.  Only turn in the new code you added, not the entire file.</b>
 * The I2C#2 driver is already implemented and used for on-board sensors.
 * Study the existing I2C code: i2c_base.cpp.  Please ask any questions if you have any, but the driver was implemented using the state machine diagrams given at the below wikipedia page.

@@ Line 131: / Line 131: @@
 == Assignment ==
-=== I2C State Machine ===
+=== I2C State Machine Assignment ===
 Design your I2C state machine.  Look at the "Master Write" and "Master Read", and do the following:
@@ Line 138: / Line 138: @@
 *You can design your own state machine, or augment the existing one, whichever method can yield the maximum clarify for your I2C slave state.
-=== I2C ===
+=== I2C Code Assignment ===
 ==== Assignment Outline ====
 <b>This is a group assignment; submit one copy of code per team and put down the names of your group members as part of the source code you turn in.  Only turn in the new code you added, not the entire file.</b>

@@ Line 140: / Line 140: @@
 === I2C ===
 ==== Assignment Outline ====
-<b>This is a group assignment; submit one copy of code per team and put down the names of your group members as part of the source code you turn in.  Only turn in the new code you added, not the entire file.<b>
+<b>This is a group assignment; submit one copy of code per team and put down the names of your group members as part of the source code you turn in.  Only turn in the new code you added, not the entire file.</b>
 * The I2C#2 driver is already implemented and used for on-board sensors.
 * Study the existing I2C code: i2c_base.cpp.  Please ask any questions if you have any, but the driver was implemented using the state machine diagrams given at the below wikipedia page.

@@ Line 139: / Line 139: @@
 === I2C ===
 Extend the I2C base class to also support slave operation.  Test your I2C driver by using one board as a master, and another board as a slave.
 #  Study <B><CODE>i2c_base.cpp</CODE></B>, particularly the following methods:

@@ Line 132: / Line 132: @@
 === I2C State Machine ===
-#Design your I2C state machine.  Look at the "Master Write" and "Master Read", and do the following:
+Design your I2C state machine.  Look at the "Master Write" and "Master Read", and do the following:
 *Right underneath the Master State, determine which state the slave will enter when the master is in each of the states

← Older revision		Revision as of 04:40, 14 October 2016
Line 179:		Line 179:
	=== Warning ===		=== Warning ===
	Since the I2C state machine function is called from inside an interrupt, you may not be able to to use <B><CODE>printf()</CODE></B>, especially if you are running FreeRTOS. As an alternative, use the debug printf methods from the <B><CODE>printf_lib.h</CODE></B> file.		Since the I2C state machine function is called from inside an interrupt, you may not be able to to use <B><CODE>printf()</CODE></B>, especially if you are running FreeRTOS. As an alternative, use the debug printf methods from the <B><CODE>printf_lib.h</CODE></B> file.
		+
		+	=== Hints ===
		+	* Start by hooking up master microcontroller running the default, unmodified sample FreeRTOS project
		+	* Familiarize yourself with the master microcontroller I2C commands: "help i2c"
		+	* Initialize the slave microcontroller's slave address such that you will get an interrupt when your address is sent by the master microcontroller
		+	* Add printfs to the I2C state machine code to identify what states you enter when the other master microcontroller is trying to do an I2C transaction
		+	* Follow your diagram and figure out how to make the I2C slave state machine walk through to read and write registers
		+	<BR/>

@@ Line 112: / Line 112: @@
 Before you jump right into the assignment, do the following:
 *  Read and understand how an I2C master performs slave register read and write operation
 *  Next to each of the master state, determine which slave state is entered when the master enters its state
 *  Determine how your slave memory or registers will be read or written