Designing with proven implementations of the Inter IC bus
By Ted Salazar, Maxim Integrated Products
Aug 8 2007 (0:07 AM), Embedded.com
The Inter IC (I2C) bus was developed by Philips Semiconductor in the early 1980s to simplify electronic products by reducing the number of parallel data lines. Version 1.0 of the I2C-Bus specification, released by Philips in 1992, defined a simple, 2-wire, bidirectional bus for communications between ICs.
By 1998, the I2C bus had become the de-facto standard for low-speed IC-to-IC communications. At that time more than 50 licensed companies were using the standard, and the I2C interface was included in more than 1000 different ICs.
Because the I2C bus is currently the industry's most widely used serial bus, it behooves a system designer to have a handful of proven implementations on hand.
The method you choose - on-chip, bit-banged, or IP-core implementation - depends mostly on the system processor, but nothing is easier than using an approach that is proven and already works. This article includes a working reference for each of the three methods.
The I2C bus configurations presented in this article have been proven to ensure easy communications with slave devices on the bus. Each implementation includes examples in the form of schematics and code.
Aug 8 2007 (0:07 AM), Embedded.com
The Inter IC (I2C) bus was developed by Philips Semiconductor in the early 1980s to simplify electronic products by reducing the number of parallel data lines. Version 1.0 of the I2C-Bus specification, released by Philips in 1992, defined a simple, 2-wire, bidirectional bus for communications between ICs.
By 1998, the I2C bus had become the de-facto standard for low-speed IC-to-IC communications. At that time more than 50 licensed companies were using the standard, and the I2C interface was included in more than 1000 different ICs.
Because the I2C bus is currently the industry's most widely used serial bus, it behooves a system designer to have a handful of proven implementations on hand.
The method you choose - on-chip, bit-banged, or IP-core implementation - depends mostly on the system processor, but nothing is easier than using an approach that is proven and already works. This article includes a working reference for each of the three methods.
The I2C bus configurations presented in this article have been proven to ensure easy communications with slave devices on the bus. Each implementation includes examples in the form of schematics and code.
To read the full article, click here
Related Semiconductor IP
- I2C protocol Controller
- I2C - Verifies I2C communication, ensuring protocol compliance and error-free data transfer
- I2C Master and Slave
- I2C Verification IP
- I2C Synthesizable Transactor
Related Articles
- Revolutionizing Consumer Electronics with the power of AI Integration
- Streamlining SoC Integration With the Power of Automation
- CANsec: Security for the Third Generation of the CAN Bus
- Expanding the Horizon of System Monitoring with the Arm SMCF
Latest Articles
- A Secure dToF LiDAR SoC with Dual-Domain Fingerprinting and Event-Driven AFE Circuit Achieving Sensor-Level Attack Resilience
- ZTA-Q: an Open-source RISC-V Platform for Accurate Quantized CNN Inference
- Automated Pre-Silicon Verification of High-Speed DDR5 and LPDDR5/6 Memory Controllers: Closed-Loop Timing, Mode Register, and PHY Synchronization in UVM
- U-Sonic: An Open-Source 8-Channel Ultrasound Transmit IP in a 130 nm RISC-V SoC
- S-ALSA: Co-Design of Adiabatic Logic-based Sensing and Balanced Bit-Cells for Secure and Energy-Efficient MRAM