Skip to main content
Production test fixture with multiple Aardvark I2C adapters programming EEPROMs

Programming Multiple I2C Chips Safely with Aardvark Adapters

GSAS Engineering · · 2 min read

A common production test scenario involves using multiple Aardvark I2C/SPI Host Adapters in a single system to program several I2C chips simultaneously, for example, writing calibration data to multiple EEPROMs on an assembly line fixture. While the Aardvark’s API makes this straightforward from a software perspective, the electrical configuration requires careful attention to grounding and power delivery to avoid intermittent failures and potential hardware damage.

The Problem: Floating Grounds and Insufficient Power

When two or more Aardvark adapters connect to the same target board (or to separate boards sharing a common bus), each adapter’s ground reference may float relative to the others if they are not explicitly tied together. This ground potential difference causes:

  • Unpredictable data levels: I2C SDA and SCL signals are referenced to ground, so a floating ground shifts the effective voltage threshold, causing the target device to misinterpret logic levels.
  • Flash Center failures: programming operations that appear to complete successfully may actually write corrupted data, or Flash Center may report communication timeouts.
  • Interface board damage: if an external level shifter board or interface board sits between the Aardvark and the target, ground potential differences can stress the level-shifting circuitry beyond its rated input range.

The Fix: Common Ground and External Power

Ground rule: All Aardvark adapters and all target devices must share a common ground reference. The Aardvark provides two ground pins on its 10-pin header specifically to ensure a solid ground path. Connect all adapter ground pins to a common ground bus on your test fixture. Power rule: When using an interface board or level shifter between the Aardvark and target devices, disable the Aardvark’s target power output on all adapters and supply 3.3V from an external bench power supply. The Aardvark’s target power pin can supply up to 25 mA at 5V, sufficient for a single EEPROM but not for powering interface boards with multiple level-shifting channels. Overloading this output risks damage to both the Aardvark and the interface board.

Step-by-Step Configuration

1. Wire all ground pins from every Aardvark adapter to a common ground bus on the fixture. Use short, low-impedance connections.
2. Disable target power on every Aardvark adapter (in Flash Center: uncheck “Enable Target Power” in the adapter settings; in API: do not enable target power in the configuration call).
3. Supply external 3.3V from a bench power supply to the interface board’s VCC rail.
4. Verify ground continuity with a multimeter before powering on, ensure less than 0.1 ohm between all adapter ground pins and the target board ground.
5. Test with a single adapter first before adding the second and subsequent adapters to isolate any per-channel issues.

Applies to SPI Too

The same grounding and power rules apply when using multiple Aardvark adapters for SPI communication. SPI signals (MOSI, MISO, SCLK, SS) are equally sensitive to ground reference differences, and the higher SPI clock rates (up to 8 MHz) make the system even more susceptible to noise caused by ground loops.

GSAS Support

GSAS Micro Systems provides applications engineering support for multi-adapter test fixture design, including guidance on grounding schemes, power distribution, and API integration for parallel programming workflows. Contact your local GSAS FAE for fixture design consultation.

Interested in Total Phase tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

I3C FAQ for firmware teams covering MIPI I3C bus fundamentals, tooling and adoption in India, from GSAS
Technical Guides Binho Semiconductor Design

I3C FAQ for Firmware Teams: What the Bus Is, What Changes, and What You Need on the Bench

MIPI Alliance describes I3C as the successor to I2C, with legacy compatibility so that I3C and I2C devices can coexist on the same bus, a two-wire interface that supports in-band interrupts to reduce pin count, plus multi-controller support and dynamic addressing. This FAQ answers the questions firmware teams actually ask before adopting it.

31 Jul 2026 · 8 min read
Binho Supernova running in I3C target mode to emulate a device against a customer controller, supported in India by GSAS
Technical Guides Binho Semiconductor Design

Running the Binho Supernova as an I3C Target: Emulating a Device Against Your Own Controller

Binho specifies the Supernova's I3C role as Controller or Target, which means the same adapter can stand in as the device under test rather than only driving one. That second direction is how a team validates its own I3C controller, its ENTDAA implementation and its interrupt handling, before the target silicon exists.

31 Jul 2026 · 7 min read
Functional verification engineer in India reviewing RTL waveforms, coverage charts and a regression dashboard, Siemens Questa One and the Questa Prime to Questa One rename explained by GSAS
Questa Siemens EDA Semiconductor Design

What Happened to Questa Prime and ModelSim?

Siemens has consolidated its Questa verification line under a single brand. The Questa product hub now returns a 301 redirect to the Questa One page, the ModelSim URL redirects to Questa One Sim, and Questa Prime no longer appears on any Siemens public product page. Here is what Questa One actually contains, what Siemens says the word One means, and what Indian verification teams should check before treating this as only a name change.

31 Jul 2026 · 11 min read