Vendor: Digital Blocks, Inc. Category: I2C / I3C

I2C Controller IP – Slave, Parameterized FIFO, AHB Master Interface (I2C2AHB)

The DB-I2C-S-AHB-BRIDGE is an I2C Slave Controller IP Core focused on low VLSI footprint ASIC / ASSP designs not requiring intern…

Overview

The DB-I2C-S-AHB-BRIDGE is an I2C Slave Controller IP Core focused on low VLSI footprint ASIC / ASSP designs not requiring internal configuration & control registers (and thus no local host CPU required), and an AHB Master interface for read/write to the user system. The DB-I2C-S-AHB-BRIDGE processes the I2C protocol & physical layers, and receives & transmits bytes with respect to the I2C payload via a bridge AHB Master Interface to user registers or memory.

The DB-I2C-S-AHB-BRIDGE runs off the AHB Master external clock input within the ASIC / ASSP, providing a synchronous design while offering I2C spike filtering of SDA and SCL.

The DB-I2C-S-AHB-BRIDGE is a member of Digital Blocks DB-I2C Controller IP Core family, which includes I2C Master/Slave, I2C Master-only, and I2C Slave-only configurations.

Figure 1 depicts the DB-I2C-S-AHB-BRIDGE Core system view. The IP is configured by internal pre-synthesis parameters and post-synthesis top-level input signals, receives input clock and reset, and performs I2C Slave-Receiver transfers (for writing data to the AHB via its AHB Master Interface) and Slave-Transmitter transfers (for reading data from the AHB via the AHB Master Interface).

Key features

  • I2C Slave Controller - Implements Slave-only protocol for smaller VLSI footprint, for applications requiring Slave–Receiver and Slave–Transmitter capability
  • AHB Master Interface – bridging the I2C Bus to the AHB Bus
    • AHB5, AHB 2.0, AHB-Lite releases
  • Autonomous I2C Slave Controller:
    • No local CPU host required
    • No configuring of control/status registers
  • Slave I2C Controller Modes:
    • Slave – Transmitter
    • Slave – Receiver
  • Supports five I2C bus speeds:
    • Standard Mode (100 Kb/s)
    • Fast Mode (400 Kb/s)
    • Fast Mode plus (1 Mbit/s)
    • Ultra fast mode (5 Mbit/s)
    • Hs-mode (3.4 Mbit/s)
  • 7- or 10-bit I2C Slave ID addressing, SCL Low Wait States
  • Digital filter for the received SDA and SCL lines
  • Compliance with I2C specifications:
    • Philips – The I2C-Bus Specification, Version 2.1, January 2000
    • NXP Rev 7.0 October 1, 2021
  • Fully-synchronous, synthesizable Verilog RTL core, with rising-edge clocking, no gated clocks, and no internal tri-states, for easy integration into FPGA or ASICdesign flows.

Block Diagram

What’s Included?

  • Verilog RTL Source or technology-specific netlist.
  • Comprehensive testbench suite with expected results.
  • Synthesis scripts.
  • Installation & Implementation Guide.
  • Technical Reference Manual.

Files

Note: some files may require an NDA depending on provider policy.

Specifications

Identity

Part Number
DB-I2C-S-AHB-BRIDGE
Vendor
Digital Blocks, Inc.
Type
Silicon IP

Provider

Digital Blocks, Inc.
HQ: USA
Digital Blocks architects, designs, verifies, and markets semiconductor Intellectually Property (IP) cores to worldwide technology systems companies. The company's expertise is in Embedded Processor & Peripherals, Display Controller, Display Link Layer, 2D Graphics, Image Compression, Audio / Video Processing, and High-Speed Networking / A/V Networking & Routing / High-Frequency Trading Networking.

Learn more about I2C / I3C IP core

From I2C to I3C: Evolution of Two-Wire Communication in Embedded Systems

The I2C (Inter-Integrated Circuit) Bus invented in 1980 by Philips Semiconductors (NXP Semiconductors today) was a massive step forward in simplifying communications in embedded systems. It is a simple two-wire interface for synchronous, multi-master/multi-slave, single ended serial communication. Fast forward 45 years to today and it is still widely used for attaching low speed peripheral Integrated Circuits (ICs), processors and microcontrollers. But silicon today has changed...

Maximizing the Usability of Your Chip Development: Design with Flexibility for the Future

Early in my career selling chips for Motorola Semiconductor, the ability to spin derivative microcontroller chips for a customer’s specific requirement was relatively straightforward. If the volume looked reasonable, we would tape-out a new chip with a few added features because mask costs and wafers were relatively inexpensive at the larger process nodes. The customer won by getting an MCU tailored to their specific need, and Motorola won by gaining a more committed customer plus another SKU that could be sold to other customers – boosting ROI. With the migration to higher cost FinFET nodes, those times are long gone as the economics no longer work.

MIPI CCI over I3C: Faster Camera Control for SoC Architects

Imagine a camera subsystem that responds in microseconds, consumes less power, and offers a more straightforward route to time-to-market. For SoC architects and IP integration teams, that vision is increasingly possible with MIPI Camera Control Interface (CCI) over I3C.

Frequently asked questions about I2C / I3C IP cores

What is I2C Controller IP – Slave, Parameterized FIFO, AHB Master Interface (I2C2AHB)?

I2C Controller IP – Slave, Parameterized FIFO, AHB Master Interface (I2C2AHB) is a I2C / I3C IP core from Digital Blocks, Inc. listed on Semi IP Hub.

How should engineers evaluate this I2C / I3C?

Engineers should review the overview, key features, supported foundries and nodes, maturity, deliverables, and provider information before shortlisting this I2C / I3C IP.

Can this semiconductor IP be compared with similar products?

Yes. Buyers can compare this product with similar semiconductor IP cores or IP families based on category, provider, process options, and structured technical specifications.

×
Semiconductor IP