I2C

Note

The I2C interface is currently only available from the ‘i2c’ branch of the github libmaple repository.

I2C is a crude and easy-to-hack serial protocol that requires only two wires/channels for communication between many devices. Every message passed on the bus is between a master (who initiates the message) and a slave device. Slaves are addressed using 7-bit addresses (up to 127 unique devices); 10-bit addressing is possible, but currently unimplemented. Every message consists of an arbitrary combination of 8-bit reads and writes as requested by the master. Higher level functionality, such as reading a particular register value, is achieved by writing to set the memory location then reading to pull out the data.

Note that the master/slave designation is on a message-by-message basis. The Maple can act as both a master (messages initiated by user code) and slave device (responding to requests via configurable interrupt handlers) at the same time.

Hardware/Circuit Design

The Maple has two I2C ports. Port 1 (i2c1) has SDA on header D9 and SCL on D5; Port 2 (i2c2) has SDA on D30 and SCL on D29.

The Maple reliably communicates with up to a 400kHz clock speed; this doesn’t translate into a 400kbps data rate except in extreme cases because of addressing and protocol overhead. We have tested clock speeds up to a megahertz and have had mixed results; in theory it could be possible to achieve even higher rates, but signal quality degrades rapidly and the bus becomes unreliable.

Proper wiring and pull-up resistor selection are essential when incorporating I2C into a circuit, especially with data rates above 100kHz. In the lab, we usually use approximately 5kΩ resistors with Vcc (3.3V) as the high voltage, and try to connect the pullup voltage as close to the SDA and SCL pins as possible. We recommend looking at the ST reference website for I2C (see the recommended reading below), starting with a slow clock rate (10kHz), and, if possible, using an oscilloscope to debug any issues.

Function Reference

The function API for I2C is not finished! See the source code for now.

SMBus

The STM32 microcontroller has hardware support for SMBus; we simply have not written software for it. The SMBAL line for i2c1 is on header D4 and for i2c2 is on D31.