You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+3-1
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@ For more information and examples see [Tiny I2C Routines for all AVR Microcontro
7
7
8
8
The main difference between these routines and the standard Arduino Wire library is that these don't use buffers, so have much smaller memory requirements and don't impose a limit on transmissions.
9
9
10
+
Version 2.0.1 increases the number of bytes you can specify in a single transfer.
11
+
10
12
## Compatibility
11
13
These I2C routines are designed to provide master I2C functionality for all Microchip/Atmel AVR processors. Over the years different generations of AVR chips have featured three different, incompatible peripherals to handle I2C:
12
14
@@ -71,7 +73,7 @@ Starts a transaction with the slave device at the specified address, and specifi
71
73
The **type** parameter can have the following values:
72
74
73
75
* 0: Write to the device.
74
-
* 1 to 32767: Read from the device. The number specifies how many bytes you are going to read.
76
+
* 1 to 2147483647: Read from the device. The number specifies how many bytes you are going to read.
75
77
* -1: Read an unspecified number of bytes from the device.
76
78
77
79
If **type** is specified as -1 you must identify the last byte read by calling **TinyI2C.readlast()** rather than **TinyI2C.read()**.
0 commit comments