AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

legacy-circuit-mockups

Generate breadboard circuit mockups and visual diagrams using HTML5 Canvas drawing techniques. Use when asked to create circuit layouts, visualize electronic component placements, draw breadboard diagrams, mockup 6502 builds, generate retro computer schematics, or design vintage electronics projects. Supports 555 timers, W65C02S microprocessors, 28C256 EEPROMs, W65C22 VIA chips, 7400-series logic gates, LEDs, resistors, capacitors, switches, buttons, crystals, and wires.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--legacy-circuit-mockups at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 21

references/emulator-28256-eeprom.md

AT28C256 EEPROM Emulation Specification

Overview

This document specifies how to emulate the AT28C256 (32 KB Parallel EEPROM) in a 6502-based system emulator. The goal is behavioral accuracy suitable for SBCs, monitors, and real ROM images, not just generic file-backed storage.

The AT28C256 is commonly used as ROM in 6502 systems, but it is electrically writable and has timing behaviors that differ from SRAM.


Chip Summary

| Parameter | Value | | -------------- | ---------------------- | | Capacity | 32 KB (256 Kbit) | | Organization | 32,768 x 8 | | Address Lines | A0-A14 | | Data Lines | D0-D7 | | Supply Voltage | 5V | | Typical Use | ROM / Firmware storage |


Pin Definitions

| Pin | Name | Function | | ------ | ------------- | ---------------------- | | A0-A14 | Address | Byte address | | D0-D7 | Data | Data bus | | /CE | Chip Enable | Activates chip | | /OE | Output Enable | Enables output drivers | | /WE | Write Enable | Triggers write cycle | | VCC | +5V | Power | | GND | Ground | Reference |


Read Cycle Behavior

A read occurs when:

/CE = 0
/OE = 0
/WE = 1

Read Rules

  • Address must be stable before /OE is asserted
  • Data appears on D0-D7 after access time (ignored in most emulators)
  • Output is high-impedance when /OE = 1 or /CE = 1

Emulator Behavior

if CE == 0 and OE == 0 and WE == 1:
    data_bus = memory[address]
else:
    data_bus = Z

Write Cycle Behavior

A write occurs when:

/CE = 0
/WE = 0

(/OE is typically HIGH during writes)

Important EEPROM Characteristics

  • Writes are not instantaneous
  • Each write triggers an internal programming cycle
  • During programming, reads may return undefined data

Write Timing Model (Simplified)

Real Hardware

| Parameter | Typical | | --------------- | -------- | | Byte Write Time | ~200 µs | | Page Size | 64 bytes | | Page Write Time | ~10 ms |

Emulator Simplification Options

Option A - Instant Writes (Common)

  • Write immediately updates memory
  • No busy state
  • Recommended for early emulators

Option B - Cycle-Based Busy State (Advanced)

  • Track a "write in progress" timer
  • Reads during write return last value or 0xFF
  • Writes ignored until cycle completes

Page Write Emulation (Optional)

  • Page size: 64 bytes
  • Writes within same page before timeout commit together
  • Crossing page boundary wraps within page (hardware quirk)

Simplified rule:

page_base = address & 0xFFC0
page_offset = address & 0x003F

Write Protection Behavior

Some systems treat EEPROM as ROM-only after programming.

Emulator may support:

  • Read-only mode (writes ignored)
  • Programmable mode (writes allowed)
  • Runtime toggle (simulates programming jumper)

Power-Up State

  • EEPROM retains contents
  • No undefined data on power-up

Emulator should:

  • Load contents from image file
  • Preserve data across resets

Bus Contention Rules

| Condition | Behavior | | ------------------- | ----------------- | | /CE = 1 | Data bus = Z | | /OE = 1 | Data bus = Z | | /WE = 0 and /OE = 0 | Undefined (avoid) |

Emulator may:

  • Prioritize write
  • Or flag invalid state

Memory Mapping in 6502 Systems

Common layout:

$0000-$7FFF  RAM
$8000-$FFFF  AT28C256 EEPROM

Reset Vector Usage

| Vector | Address | | ------ | ----------- | | RESET | $FFFC-$FFFD | | NMI | $FFFA-$FFFB | | IRQ | $FFFE-$FFFF |


Emulator API Model

typedef struct {
    uint8_t memory[32768];
    bool write_enabled;
    bool busy;
    uint32_t busy_cycles;
} AT28C256;

Read

uint8_t eeprom_read(addr);

Write

void eeprom_write(addr, value);

Recommended Emulator Defaults

| Feature | Setting | | ------------- | ----------- | | Write Delay | Disabled | | Page Mode | Disabled | | Write Protect | Enabled | | Persistence | File-backed |


Testing Checklist

  • Reset vector fetch
  • ROM reads under normal execution
  • Writes ignored in read-only mode
  • Correct address masking (15 bits)
  • No bus drive when disabled

References


Notes

This specification intentionally mirrors real hardware quirks while allowing emulator authors to choose between simplicity and accuracy. It is suitable for:

  • Educational emulators
  • SBC simulation
  • ROM development workflows
  • Integration with 6502 + 6522 + SRAM emulation