Skip to main content
I2C EEPROM programming setup with Aardvark adapter and development board

I2C EEPROM Batch Programming with the Aardvark Adapter

GSAS Engineering · · 2 min read

Programming I2C EEPROMs is one of the most common tasks for the Aardvark I2C/SPI Host Adapter. While Control Center Serial Software provides an interactive GUI for single read/write operations, its XML Batch Mode enables scripted, repeatable programming sequences that are essential for production workflows. This guide walks through programming an AT24C02 I2C EEPROM using batch mode.

Hardware Setup

The AT24C02 is a 256-byte (2 Kbit) I2C EEPROM with 8-byte page write capability. It is the EEPROM included on the I2C/SPI Activity Board.

Connections

Aardvark PinSignalAT24C02 Pin
Pin 4SCLSCL (clock)
Pin 6SDASDA (data)
Pin 9GNDGND, A0, A1, A2, WP
Pin 10VCCVCC (3.3V)

The AT24C02’s address pins (A0, A1, A2) are tied to ground, setting the device’s I2C address to 0x50 (binary 1010000). The Write Protect (WP) pin is also grounded to enable write operations.

Control Center Configuration

Open Control Center Serial Software and configure the Aardvark:

1. Enable I2C: check the I2C checkbox in the adapter configuration.
2. Enable pullups: the Activity Board has on-board pullup resistors, but enabling the Aardvark’s internal pullups provides additional bus drive capability.
3. Enable target power: supplies 3.3V from the Aardvark to the Activity Board.
4. Set bitrate: 100 kHz is a safe starting point for EEPROM operations.

Writing with XML Batch Mode

Control Center’s Batch Mode executes a sequence of I2C/SPI commands defined in an XML file. For EEPROM programming, the XML script contains a series of I2C write commands, one per byte or page.

Batch Configuration

The XML batch script begins with an adapter configuration block:

```

```

Page Write Operation

Each write command sends a memory address byte followed by the data byte to the EEPROM’s I2C address:

```
00 AA
```

This writes the value 0xAA to EEPROM address 0x00. The first byte (0x00) is the word address inside the EEPROM; the second byte (0xAA) is the data.

To program the entire 256-byte EEPROM, the batch script contains 256 write commands, one per address. A 5 ms delay between writes ensures the EEPROM’s internal write cycle completes:

```
00 00

01 01

…
FF FF
```

This writes address 0x00 = 0x00, address 0x01 = 0x01, through address 0xFF = 0xFF, filling the EEPROM with its own address values for easy verification.

Sequential Read Operation

Reading back the EEPROM uses a two-step I2C sequence:

1. Set the address pointer: write the starting address to the EEPROM without sending a STOP condition.
2. Read the data: perform a read operation that retrieves bytes sequentially from the current address pointer.

In batch XML:

```
00

```

The `nostop=“1”` parameter on the write command generates an I2C Repeated Start instead of a Stop + Start sequence, which is required by most I2C EEPROMs for the “Set Address then Read” operation. The subsequent 256-byte read retrieves the entire EEPROM contents starting from address 0x00.

Verifying the Data

Compare the read-back data against the expected pattern. If you programmed address = data (0x00 at 0x00, 0x01 at 0x01, etc.), the read-back should produce an ascending sequence from 0x00 to 0xFF.

Moving to Production

For production programming workflows, the same operations can be automated through the Aardvark API in Python, C, or LabVIEW, reading firmware images from files and programming them into EEPROMs with pass/fail logging and serial number traceability. Flash Center Software also provides a GUI-based alternative that handles the entire read/program/verify cycle without writing any code.

GSAS Micro Systems provides the Aardvark alongside the I2C/SPI Activity Board for I2C EEPROM programming workshops and production test integration support across India.

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
The bench to harness adapter path drawn left to right: the ECU connector, a test lead, a media converter or pluggable T1 module, RJ45, and the host, showing where each connector family sits between the device under test and the laptop, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Connectors: H-MTD, MATEnet, MQS

An ECU arrives on the bench with a connector nobody has a mate for, and the day is gone. Search the family names and you get connector product pages that describe their own part and stop there. This article puts the families side by side in one table using only what their public pages state, then makes the point those pages leave out: the IEEE link segment definition, not the connector, is what sets reach and loss limits, and shielding is a channel decision rather than a preference. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read