General I2C protocol - Revision history

Rew at 12:06, 6 November 2023

2023-11-06T12:06:48Z

Cartridge1987 at 16:00, 27 November 2015

2015-11-27T16:00:47Z

Rew: Created page with " BitWizard expansion boards communicate using an I2C protocol. I2C is a standard protocol, sometimes called "TW" or "TWI" by other manufacturers. Each I2C slave has its own..."

2012-04-06T14:22:11Z

Created page with " BitWizard expansion boards communicate using an I2C protocol. I2C is a standard protocol, sometimes called "TW" or "TWI" by other manufacturers. Each I2C slave has its own..."

New page

BitWizard expansion boards communicate using an I2C protocol.

I2C is a standard protocol, sometimes called "TW" or "TWI" by other manufacturers.
Each I2C slave has its own I2C address. This allows us to daisy chain a large number of boards. The BitWizard I2C boards can be told to use a different I2C address so that you can resolve conflicts if you would otherwise have several devices at one address.

= timing =

The slaves use an ATTINY44 processor. These have a hardware universal serial interface (USI) module that can be configured as "I2C slave". Many things however have to be processed in software. This means that some time is required between each byte. The hardware of the ATTINY44 will pull the SCL line low while the processing is not finished. If you use a software I2C master, doublecheck that your I2C master supports this feature.

The I2C protocol is specified at 100kHz and 400kHz bit rate. If you lower the pullup resistors a bit and have a short bus, the hardware will probably be able to handle bit rates up to 2MHz. This is not recommended. Use the standard 400kHz.

= protocol =

To send a sequence of bytes to the slave I2C device, the master starts by creating a START condition: the SDA line goes low while SCL is held high. All slaves are now primed to receive an "address" byte. Next the master sends the address byte.

After this the protocol in theory depends on which slave you are talking to. In practice so far it is convenient to make the slaves talk a similar protocol: the next byte specifies a "register" or "port" address. After this you can send data to that port or register.

If the data can be considered a "data stream" like with the I2C_LCD board, you can call it a "port". If there is just a single value, it is more common to call it a register.

@@ Line 3: / Line 3: @@
 I2C is a standard protocol, sometimes called "TW" or "TWI" by other manufacturers.
-Each I2C slave has its own I2C address. This allows us to daisy chain a large number of boards. The BitWizard I2C boards can be told to use a different I2C address so that you can resolve conflicts if you would otherwise have several devices at one address.
+Each I2C slave has its own I2C address. This allows us to daisy chain a large number of boards. The BitWizard I2C boards can be told to use a different I2C address so that you can resolve conflicts if you would otherwise have several devices at one address. Most other commercial products have an I2C address assigned by the manufacturer or a small range that you can configure using strapping pins.
+For the pinout of the bitwizard connector: [https://bitwizard.nl/wiki/I2C_connector_pinout look here]

@@ Line 6: / Line 6: @@
-= timing =
+= Timing =
 The slaves use an ATTINY44 processor. These have a hardware universal serial interface (USI) module that can be configured as "I2C slave". Many things however have to be processed in software. This means that some time is required between each byte. The hardware of the ATTINY44 will pull the SCL line low while the processing is not finished. If you use a software I2C master, doublecheck that your I2C master supports this feature.
@@ Line 12: / Line 12: @@
 The I2C protocol is specified at 100kHz and 400kHz bit rate. If you lower the pullup resistors a bit and have a short bus, the hardware will probably be able to handle bit rates up to 2MHz. This is not recommended. Use the standard 400kHz.
-= protocol =
+= Protocol =
 To send a sequence of bytes to the slave I2C device, the master starts by creating a START condition: the SDA line goes low while SCL is held high. All slaves are now primed to receive an "address" byte. Next the master sends the address byte.