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

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
Storage sizing ladder for automotive data logging: four rungs stepping from an aggregate link rate of 1 Gbit/s to 125 MB per second, then 450 GB per hour, then 3.6 TB per eight-hour shift, then 18 TB per five-day week, in decimal units, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Data Loggers: Capture Without Loss

Search for an automotive data logger and the results split into cheap OBD dongles at one end and enterprise ADAS recorders at the other, with nothing in between explaining the engineering that decides whether you lose frames. This is the loss budget end to end: mirror oversubscription upstream of the logger, encapsulation overhead on the capture path, sustained write rate against burst rate, rotation stalls, and storage arithmetic worked in full so you can redo it with your own numbers instead of trusting ours. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read