ss=a-plus-plus5subHsub class=a-plus-plus5subNS}(PPhsub class=a-plus-plus3sub)sub class=a-plus-plus2sub(X)] · CHsub class=a-plus-plus2subClsub class=a-plus-plus2sub (em class...pdfVIP

Chapter 14 I2C Bus The I2C bus, also known as the two-wire interface (TWI), was developed by Philips circa 1982 to allow communication with lower-speed peripherals.49 It was also economical because it required only two wires (excluding ground and power connections). Since then, other standards have been devised, building upon this framework, such as the SMBus. However, the original I2C bus remains popular as a simple, cost-effective way to connect peripherals. I2C Overview Figure 14-1 shows the I2C bus in the Raspberry Pi context. The Raspberry Pi provides the I2C bus using the BCM2835 as the bus master. Notice that the Pi also provides the external pull-up resistors R and R , shown inside the dotted lines. 1 2 Figure 14-1. The I2C bus 167 Chapter 14 ■ I2C Bus The two I2C bus lines are provided on the header strip P1: P1 Rev 1.0 Rev 2.0 + GPIO I2C Bus GPIO I2C Bus P1-03 0 SDA0 I2C-0 2 SDA1 I2C-1 P1-05 1 SCL0 3 SCL1 Note that the original Raspberry Pi provided I2C bus 0, but switched to using bus 1 with Rev 2.0 and later units. The design of the I2C bus is such that multiple peripherals are attached to the SDA and the SCL lines. Each slave (peripheral) has its own unique 7-bit address. For example, the MCP23017 GPIO extender peripheral might be configured with the address of 0x20. Each peripheral is called upon by the master by using this address. All nonaddressed peripherals are expected to remain quiet so that communication can proceed with the selected slav