This library implements a software I2C controller interface. It was written without any platform-specific code, and should therefore work on any platform supported by the Arduino or Energia IDEs.

This library is not a drop-in replacement for Wire. You will therefore need to write your own code for sketches that need to use this library.

However, this library provides a much simpler interface than the Wire library, and modifying existing code to use this new library should be relatively straightforward in many cases.

I consider the Arduino Wire library needlessly complicated, particularly for beginners, for two key reasons:

1. The vast majority of I2C devices that I have worked with generally have a simple "read from register" or "write to register" interface.
   • This implies that simple readFromRegister() and writeToRegister() methods should be a fundamental part of the library API.
   • The user should not have to string together multiple commands just to perform a simple write to a device register.
   • The API should provide the hooks necessary to support more complicated communications, but not at the expense of ease-of-use for the most common use cases.
2. The Wire library abstracts the I2C hardware interface as the object being acted on.
   • From a design standpoint, I would suggest that the actual I2C device is the object that is being acted on.
   • The interface should therefore be modeled with the device as the object instantiated in code, not the hardware interface.

This software I2C library was designed so that the I2C device is the object that is instantiated and being acted on by the various methods. The API provides several simple readFrom() and writeTo() methods, while also including low-level signaling functionality to create more complicated communication flows when necessary.

In addition to simplifying the user interface compared to Wire, this library also addresses the following shortcomings of some of the other software I2C libraries:

• Hardcoded delays
  • Hardcoded delays should not be necessary at the "slow" signaling speeds inherent in a software-based I2C solution using digitalWrite() and pinMode() methods.
• Lack of or incorrect support of clock stretching
• Incorrectly using pinMode(OUTPUT) and digitalWrite(HIGH) for indicating a "HIGH" value on SCL or SDA
  • Since I2C is an open-collector design that requires pull-up resistors, a "high" value on the data and clock lines should be implemented by putting the pin in INPUT mode. INPUT mode does not drive the bus high or low, and allows the external pull-ups to assert the high level.

This library implements the I2C protocol without the above issues.

Many I2C devices have a simple "read a byte from a register" or "write a byte to a register" interface. This library has a very simple programming model for those cases. For example:

/* Example of a simple read and write program */

// First, include the library header file
#include "SWI2C.h"

// Define constants 
#define SCL_PIN 2
#define SDA_PIN 3
#define DEVICE_ADDRESS 0x30 // 7-bit I2C address of the device we are using

// Create an object instance of the I2C device
SWI2C myDevice = SWI2C(SDA_PIN, SCL_PIN, DEVICE_ADDRESS);

// Other global variables
uint8_t regAddress;
uint8_t byte_to_write;
uint8_t byte_to_read;
uint8_t buffer[10] = {0, 1, 2, 3, 4, 5, 6, 7, 8, 9};

void setup() {
  // Initialize the device
  myDevice.begin();

}

void loop() {
  regAddress = 0x10;
  byte_to_write = 0x55;

  // Write a byte to a device register: 
  myDevice.writeToRegister(regAddress, byte_to_write);
  // Read a byte from a device register: 
  myDevice.readFromRegister(regAddress, byte_to_read);

  // Write several bytes to a device register:
  myDevice.writeToRegister(regAddress, buffer, 10);
  // Read several bytes from a device register:
  myDevice.readFromRegister(regAddress, buffer, 10);
}

More complex use cases can take advantage of the other high level and low level methods outlined below.

Be sure to review the example sketches included with the library. Also see below for links to other libraries and sketches using SWI2C.

1. Include the library header file:

   #include "SWI2C.h"

2. Instantiate an object for each I2C device using SWI2C. The device address and I2C pins are defined in the object constructor, so you need a separate object for each device. Note that this is different from the way that the Wire library operates.

   sda_pin is the pin number for the SDA signal, scl_pin is the pin number for the SCL signal, and deviceID is the 7-bit device address of the I2C device represented by this object instance. deviceID does not include the read/write bit.

   SWI2C myDevice(uint8_t sda_pin, uint8_t scl_pin, uint8_t deviceID);

3. Initialize the hardware before using the I2C device:

   myDevice.begin();

4. Use the high level or low level library methods described below.

The library provides several basic methods that can be used to simply interface with a wide variety of I2C devices.

• Write 8-bit value data to register address regAddress:

  int writeToRegister(uint8_t regAddress, uint8_t data);

• Write count bytes from buffer to register address regAddress:

  int writeToRegister(uint8_t regAddress, uint8_t* buffer, uint8_t count);

• Write 8-bit value data to the device. Used for devices which do not have registers (e.g. PCA9548, PCF8574):

  int writeToDevice(uint8_t data);

• Write count bytes from buffer to the device. Used for devices which do not have registers (e.g. PCA9548, PCF8574):

  int writeToDevice(uint8_t* buffer, uint8_t count);

• Read 8-bit value data from register address regAddress:

  int readFromRegister(uint8_t regAddress, uint8_t &data);

• Read count bytes into buffer from register address regAddress. buffer must be defined to have at least count elements. Bytes received are placed in buffer LSB first (i.e., the first byte received is put in buffer[0], second byte is buffer[1], etc.):

  int readFromRegister(uint8_t regAddress, uint8_t* buffer, uint8_t count);

• Read 8-bit value data from the device. Used for devices which do not have registers (e.g. PCA9548, PCF8574):

  int readFromDevice(uint8_t &data);

• Read count bytes into buffer from the device. buffer must be defined to have at least count elements. Bytes received are placed in buffer LSB first (i.e., the first byte received is put in buffer[0], second byte is buffer[1], etc.). Used for devices which do not have registers (e.g. PCA9548, PCF8574):

  int readFromDevice(uint8_t* buffer, uint8_t count);

The following additional high level library methods can also be used to read and write data to an I2C device. See below for details on the return codes for these and the above methods.

• Write a 16-bit data value to device register regAddress. The first byte written is the least signifcant byte of data:

  int myDevice.write2bToRegister(uint8_t regAddress, uint16_t data);

• Same as write2bToRegister(), except that the first byte written is the most signifcant byte of data:

  int myDevice.write2bToRegisterMSBFirst(uint8_t regAddress, uint16_t data);

• Read 16-bit value from register address regAddress into the location pointed to by data. This function assumes that the first byte received is the least significant byte:

  int myDevice.read2bFromRegister(uint8_t regAddress, uint16_t* data);

• Same as read2bFromRegister(), except the first byte received is the most significant byte:

  int myDevice.read2bFromRegisterMSBFirst(uint8_t regAddress, uint16_t* data);

All of the high level methods above return the integer 1 if the message was sent successfully, and return 0 if a NACK was detected during the I2C communication.

If a NACK was detected (return code 0):

• The transmission is immediately stopped, with no more data sent or received.
• An I2C STOP condition is signalled on the bus.
• The I2C bus is released.
• The contents of the data variable for the various read() methods should be assumed to be invalid, as a partial or incorrect data transfer has occurred.

Each of the high level methods listed above also takes an optional final parameter bool sendStopBit which defaults to true (and therefore does not need to be specified when calling any of these methods). When sendStopBit is true, the I2C message will end with a STOP bit and release control of the I2C bus.

To trigger a repeated start condition (sometimes referred to as a restart condition), set sendStopBit to false. In this case a STOP bit will not be sent at the end of the message, and the I2C bus will be kept active by the controller.

Although general I2C communication can be done with the above readFrom and writeTo methods, there may be times where more direct control of the protocol is required. The following public methods are also available in the SWI2C class.

• The following methods set the SCL or SDA lines HIGH or LOW:

  void sclHi();
  void sclLo();
  void sdaHi();
  void sdaLo();

• Signal a START bit on the I2C bus:

  void startBit();

• Write the 7-bit device address along with either a read (1) or write (0) bit (r_w), for a total of 8 bits:

  void writeAddress(uint8_t r_w);

• Return the value of the ACK bit received (either 1 or 0) from the device. This function is also used to send a NACK from the controller when reading the last byte from the peripheral device:

  uint8_t checkAckBit();

• Write an ACK bit -- used by the controller between bytes of a multi-byte read operation. The final byte is indicated by a NACK from the controller (see checkAckBit() above):

  void writeAck();

• Write the 8-bit regAddress value to the SDA bus:

  void writeRegister(uint8_t regAddress);

• Signal a STOP bit on the I2C bus:

  void stopBit();

• Return an 8-bit value read from the I2C bus:

  uint8_t read1Byte();

• Return a 16-bit value read from the I2C bus. The first byte received is assumed to be the least significant byte:

  uint16_t read2Byte();

• Write an 8-bit data value to the I2C bus:

  void writeByte(uint8_t data);

• Return the current deviceID (7-bit I2C address):

  uint8_t getDeviceID();

• Change the deviceID (7-bit I2C address).
  NOTE: The deviceID is set in the SWI2C constructor and under normal circumstances should not need to change. This method is provided for specialized use cases (e.g., where the sketch may change the I2C address of the device by controlling the address configuration pins of the I2C device, or to create an I2C address scanner).

  void setDeviceID(uint8_t deviceid);

• Set the clock stretching timeout to t milliseconds. The default timeout is 500 ms when the SWI2C object is created. If the timeout value is set to zero, then the library will wait indefinitely for the clock to be released by the device:

  void setStretchTimeout(unsigned long t);

• Read the current clock stretching timeout value:

  unsigned long getStretchTimeout();

• Check if a previous clock operation resulted in a timeout. Returns non-zero if the timeout was reached waiting for the SCL line to go high. The error will remain set internally until this function is called. Reading the value (by calling this function) clears the error:

  unsigned long checkStretchTimeout();

The library does not use any platform-specific code. All I/O functions use standard Arduino pinMode(), digitalRead(), and digitalWrite() functions. Reading and writing to the I2C device is accomplished by stringing together the basic signaling primitives specified by the protocol.

There are no hardcoded delays in the code. However, the high-level readFrom() and writeTo() methods are blocking -- they do not return until the message is completed, a NACK is received, or the clock-stretching timeout has been exceeded.

The clock-stretching timeout is implemented with a busy-wait loop in the sclHi() method which waits until the SCL line actually goes high before exiting the function. There is a default timeout of 500 ms before the wait times out and the function returns. This delay can be changed on a per-device basis (setStretchTimeout()). It can also be set to zero if no timeout is desired (which could potentially cause the library to "lock up" if the I2C device does not properly release the SCL line).

Since this is a software-based, platform-agnostic implementation, the clock speed is not programmable and is significantly reduced compared to a hardware-based I2C implementation. Expect an I2C clock speed of about 25 KHz when using an 8 MHz microcontroller.

Two example sketches use several of the high level readFrom() and writeTo() class methods.

One of the example sketches implements an I2C address scanner which uses several low level class methods.

Besides the sketches included in the examples folder, several more examples of code using SWI2C are available in my other published libraries and sketches:

• Weather Sensors Software I2C Library
• EEPROM Software I2C Library
• BQ27441 Software I2C Library
• Temperature Sensor With Display Sketch
• Sensor Repeater Sketch

• NXP I2C Bus Specification and User Manual (NXP login required)
• NXP I2C Bus Specification and User Manual available from Pololu
• NXP I2C Application Note/Manual (published 2003, possibly outdated)
• Texas Instruments I2C Application Report
• Clock Stretching
• Arduino Hardware I2C Wire library
• PCF8574A 8-bit I/O expander datasheet
  • Example of a device which does not have registers. I2C data is read/written immediately after sending the device address.

The software and other files in this repository are released under what is commonly called the MIT License. See the file LICENSE in this repository.