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

Embedded engineering workstation in India, illustrating the debug, analysis and design steps where AI now runs inside the process, supported by GSAS
Industry Insights

AI Inside the Engineering Process: What Is Worth Automating, and What Still Needs an Engineer

Arm, SEGGER, Perforce and Siemens EDA have each put AI inside a step of the engineering process rather than on top of it: debug, remediation, design entry, inference on the part. GSAS sets out the position behind our coverage of each: which steps are now worth automating, and which keep a human because the cost of being wrong is a recall.

21 Sept 2026 · 11 min read
Embedded engineering bench in India, illustrating the hardware a developer can act on today, supported by GSAS
Technical Guides Arm

Arm's Agentic AI Push: What Indian Embedded Teams Can Actually Use Today

Arm has set out its platform strategy for the agentic era, putting inference everywhere it has compute. Indian embedded teams can start on that direction this quarter with the Cortex-M toolchain they already own: Helium, CMSIS-NN, Ethos-U and Vela, on boards you can order today.

13 Sept 2026 · 7 min read
Side by side comparison of a 10BASE-T1S multidrop mixing segment, one balanced pair with four nodes on short stubs and a termination at each end, against a point to point star of four separate links into switch ports, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

10BASE-T1S and PLCA: Multidrop Ethernet Explained

10BASE-T1S is the one member of the T1 single-pair Ethernet family that keeps a shared medium, and PLCA is the reconciliation sublayer that stops the nodes on it from colliding. This article covers what IEEE 802.3cg standardises, how the beacon and transmit opportunities schedule a cycle, the node count and segment length figures the OPEN Alliance interoperability test suite works to, and the failure modes that put a segment quietly back into contention while every link still looks up. Written by the GSAS Micro Systems engineering team in India for teams bringing up multidrop segments on the bench.

29 Aug 2026 · 12 min read