I2CV2 - Revision history

Admin at 14:50, 4 February 2014

2014-02-04T14:50:01Z

Admin at 14:47, 4 February 2014

2014-02-04T14:47:36Z

Admin at 14:31, 4 February 2014

2014-02-04T14:31:19Z

Admin: Created page with "I2CV2"

2014-02-04T11:16:59Z

Created page with "I2CV2"

New page

I2CV2

@@ Line 25: / Line 25: @@
 &nbsp;
-'''See also''': [[Using_the_I2C_protocol|Using the I2C protocol]] , [[CONFIG_TWI|CONFIG TWI]]
+'''See also''': [[Using the I2C protocol|Using the I2C protocol]] , [[CONFIG TWI|CONFIG TWI]]
@@ Line 31: / Line 31: @@
 <br/>{{Languages}}
-[[Category:BASCOM Language Reference]]
+[[Category:ASM Libraries and Add-Ons]]

@@ Line 11: / Line 11: @@
 For this purpose the i2c master library has been rewritten so that clock and data have a known state/level at all times. This allows to create glitch free clock/data.
-To use this library use the $LIB directive : &nbsp; $LIB "I2CV2.LIB"
+To use this library use the $LIB directive&nbsp;: &nbsp; $LIB "I2CV2.LIB"
-This will make the compiler use this library. One thing to be aware of : &nbsp;a repeated start can only be created by using the[[File:file:///D:/TRANSFER/AVRHELPHTML/new29012014/i2start_i2cstop__i2crbyte__i2cwbyte.htm|I2CREPSTART]]&nbsp;statement.
+This will make the compiler use this library. One thing to be aware of&nbsp;: &nbsp;a repeated start can only be created by using the [[I2CREPSTART]] statement.
 This is a difference with the default i2c.lib
@@ Line 25: / Line 25: @@
 &nbsp;
-See also:&nbsp;[[Using_the_I2C_protocol|Using the I2C protocol]],&nbsp;[[CONFIG_TWI|CONFIG TWI]]&nbsp;,&nbsp;[[I2CV2]]
+'''See also''': [[Using_the_I2C_protocol|Using the I2C protocol]] , [[CONFIG_TWI|CONFIG TWI]]

← Older revision		Revision as of 14:31, 4 February 2014
Line 1:		Line 1:
−	I2CV2	+	<span class="f_Header">I2C Software</span>
		+
		+	By default BASCOM will use software routines when you use I2C statements. This because when the first AVR chips were introduced, there was no TWI interface. Atmel named it TWI because Philips is the inventor of I2C. But TWI is the same as I2C.
		+
		+
		+
		+	When your processor has a TWI interface you can best use this TWI interface.
		+
		+	By default the software master i2c routines use the library named i2c.lib. This library does not maintain a clock/data state so when i2cstart or i2cstop is generated, the clock and data lines need to be set to the proper state before the start/stop condition can be generated. This can result in small glitches. Most slave chips will not notice them but some do.
		+
		+	For this purpose the i2c master library has been rewritten so that clock and data have a known state/level at all times. This allows to create glitch free clock/data.
		+
		+	To use this library use the $LIB directive :   $LIB "I2CV2.LIB"
		+
		+	This will make the compiler use this library. One thing to be aware of :  a repeated start can only be created by using the[[File:file:///D:/TRANSFER/AVRHELPHTML/new29012014/i2start_i2cstop__i2crbyte__i2cwbyte.htm\|I2CREPSTART]] statement.
		+
		+	This is a difference with the default i2c.lib
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+	See also: [[Using_the_I2C_protocol\|Using the I2C protocol]], [[CONFIG_TWI\|CONFIG TWI]] , [[I2CV2]]
		+
		+
		+
		+	<br/>{{Languages}}
		+
		+	[[Category:BASCOM Language Reference]]