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

Solid Sands campaign artwork for SuperTest Van Gogh 6.0, C++ source code set against Van Gogh's The Starry Night
Functional Safety Solid Sands

SuperTest Van Gogh 6.0: C23, C++23 and the C++20 Modules Gap

Solid Sands has released SuperTest Van Gogh 6.0 with more than 1,900 new tests, including 480 for C23 and 440 for C++23. The number worth your attention is a different one: GCC, Clang and MSVC each currently fail about 20% of its 173 C++20 modules tests.

6 Oct 2026 · 7 min read
Embedded verification and unit test workflow, illustrating the economics of finding defects early, supported by GSAS Micro Systems in India
Technical Guides

Verification Economics: What a Late Defect Actually Costs, and What the Evidence Really Says

Finding a defect in month 2 instead of month 14 is a budget decision before it is a quality decision. This sets out what the published evidence supports, what it does not, including the 100x multiplier that traces back to a course handout rather than a study, and how an Indian embedded team builds the case on its own numbers.

21 Sept 2026 · 14 min read
Master and slave roles on a 100BASE-T1 link: the master PHY times its transmitter from a local clock, the slave recovers the clock from the received signal, with the both-master and both-slave misconfigurations that leave the link down, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

100BASE-T1 Link Won't Come Up: A Vendor-Neutral Checklist

A 100BASE-T1 link that will not come up is almost never a mystery, but the answers on the web are written per silicon vendor and do not transfer. This is the ordered bring-up checklist that holds regardless of which PHY, switch or SoC you have: physical layer first, then the PHY over MDIO, then the master and slave pairing, then the causes of a link that comes up and drops. The standards and tooling claims trace to IEEE 802.3 task force records, the Linux ethtool and kernel documentation or published test material. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 14 min read