Adding Battery-Backed SRAM to the X68000 Expansion Bus

The Sharp X68000 is an unusually rewarding platform for hardware expansion because its architecture remains accessible at the signal level. A carefully designed SRAM board can add persistent working memory for diagnostics, utility software, configuration data, or custom applications without changing the character of the original computer.

Battery-backed SRAM is different from ordinary expansion RAM. The memory contents survive shutdown, but only if the SRAM receives a clean backup supply while its data and control pins remain electrically isolated from the inactive computer bus. That makes the project a combination of memory mapping, bus interfacing, power management, and physical construction.

A successful module should be treated as a small computer peripheral rather than as a collection of memory chips. The address range must be selected deliberately, bus timing must be respected, and the backup circuit must prevent the battery from feeding the X68000 or other devices when the machine is turned off.

Why Add Persistent SRAM

The most direct use is storing small amounts of information that should remain available after power-off. A diagnostic program could preserve error codes, a development tool could retain settings, and a game or application could use the area for save data. SRAM is also convenient during prototyping because it can be written repeatedly without the erase cycles associated with flash memory.

Battery-backed memory has a particularly useful role in hardware development. A test program can record the last successful stage before a crash, preserve counters across resets, or store calibration values for an expansion device. When investigating intermittent faults, persistent logs can reveal whether the failure occurred during startup, video initialization, disk access, or a later bus transaction.

The capacity does not need to be large. A 32 KB or 128 KB device may be sufficient for configuration and logging, while a larger chip can support a compact ramdisk or experimental software environment. The important distinction is that the selected address space must be documented and stable. A reliable small memory region is more useful than a larger area that overlaps another peripheral.

Know the Expansion Bus

The X68000 expansion connector exposes the signals required for a 68000-family peripheral: address lines, a bidirectional data bus, read and write controls, upper- and lower-byte strobes, address strobe, data-transfer acknowledgement, reset, clock, and power. Exact signal names and available address lines can vary by connector, documentation source, or machine revision, so the original service information and verified community schematics should be treated as authoritative.

The 68000 does not use a single universal “memory enable” pin in the way some microcontrollers do. A peripheral normally combines address decoding with bus control signals to decide when it should respond. A practical SRAM board therefore needs a decoder or programmable logic device that recognizes a chosen address window and generates a chip-enable signal. It must also ensure that the SRAM output drivers remain disabled except during a valid read cycle.

Byte strobes deserve special attention. The 68000 can access an even byte, an odd byte, or a full word using separate upper- and lower-data strobes. If the SRAM is organized as an 8-bit device, the board must route the appropriate byte lane and define what happens during word operations. Two 8-bit SRAMs can be arranged as a 16-bit pair, with one device connected to the upper byte and the other to the lower byte. A 16-bit SRAM simplifies word access but may require a less common part and more careful control logic.

Before designing the PCB, identify which address bits are actually present on the connector and which signals are safe to use. Confirm whether the bus expects a peripheral to assert a shared acknowledge line or whether the module should generate a local termination. Never assume that an unused address range is free merely because no documentation mentions a device there.

Choose The Memory Architecture

Several architectures are suitable for an X68000 SRAM expansion, and the best choice depends on whether the project prioritizes simplicity, capacity, or compatibility. A static RAM chip with a separate decoder is easy to understand and troubleshoot. A CPLD-based design can provide flexible address mapping and status registers, but it introduces programming tools, configuration storage, and another potential failure point.

Architecture Practical Capacity Main Strength Main Concern
Single 8-bit SRAM 32–128 KB Simple, inexpensive construction Byte-lane handling is required
Two 8-bit SRAMs 64–256 KB Natural 16-bit word access More board space and backup current
16-bit SRAM 128–512 KB Clean word-oriented interface Suitable parts may be harder to source
SRAM with CPLD decoder Depends on device Flexible mapping and control Firmware and configuration complexity
FRAM replacement Small to medium No battery maintenance Availability, voltage, and interface limits

A conventional static RAM may be labeled with a designation such as 62256, 62512, or a compatible modern equivalent. The number describes the organization and capacity, but not necessarily the voltage, speed, standby current, or pin compatibility. Check the complete datasheet. Some newer parts use 3.3 V signaling and cannot be connected directly to a 5 V expansion bus without level translation.

The backup circuit should separate three operating conditions: normal powered operation, machine shutdown, and battery replacement. During normal operation, the SRAM should receive the system supply and communicate with the bus. When the X68000 is off, the memory should receive only the backup voltage, while its chip-enable and output-enable inputs hold it in standby. During battery replacement, a temporary capacitor or socketed battery procedure can preserve contents, but this is optional and should not compromise safety.

A common arrangement uses a low-forward-drop diode or power-path controller to select the higher valid supply, with the battery feeding the SRAM’s backup pin or supply rail through current-limiting and isolation components. Do not rely on a diode alone to protect the battery. The SRAM’s standby current, leakage through input protection structures, and the behavior of the decoder must all be measured. A battery that appears to last for years on paper may discharge quickly if another device remains partially powered.

Design The Backup Power Path

The battery is usually the most failure-prone part of a long-lived SRAM module. A coin cell is convenient, but a non-rechargeable cell must never be connected to a circuit that can charge it. If the board uses a rechargeable coin cell, it needs an appropriate charging path and a component choice designed for that chemistry. Mixing the two approaches can create leakage, swelling, or a damaged cell.

A removable holder is preferable to soldering a primary lithium cell directly to the board. Add a clearly marked polarity indicator and, where practical, a series fuse or resettable protective device. A reverse-installed battery should not be able to inject current into the system supply. The battery compartment should also be positioned so that leakage cannot run across the connector or logic devices.

Backup retention can be estimated from the battery capacity and measured standby current, but the estimate must include leakage from the SRAM, supervisor, decoder, and protection components. If a 200 mAh cell supplies 2 microamps under ideal conditions, the theoretical duration is very long; real service life is reduced by self-discharge, temperature, aging, and current peaks. Measure the complete off-state current with a reliable meter after the board has settled.

The memory must be held in standby before the main supply falls through the SRAM’s valid operating range. A voltage supervisor can generate a reset or inhibit signal that disables the SRAM and decoder during brownout. This is especially valuable because a slowly collapsing supply can produce unintended writes. The supervisor threshold should suit the actual SRAM and logic voltage, rather than being selected only because it is a familiar part.

Build For Signal Integrity

Keep the address and data traces short, direct, and grouped by function. Place the SRAM close to the bus interface and put bypass capacitors beside every logic device. A 100 nF ceramic capacitor at each IC is a sensible baseline, with a larger bulk capacitor near the expansion connector and another near the battery-backed section if the layout requires it.

Bus transceivers can protect the memory and reduce loading on the X68000 connector. They are particularly useful when the module has several devices or a long edge-connector trace path. However, every additional buffer contributes propagation delay. The complete path from address decoding through chip enable and data output must meet the timing requirements of the 68000 bus cycle.

The acknowledge strategy should be conservative. If the SRAM is fast enough, the module may generate a prompt data-transfer acknowledge after decoding a valid cycle. If the logic path is slower, a wait-state mechanism may be required. A board that works with a short diagnostic routine but fails during repeated word transfers may have a marginal acknowledge timing problem rather than a defective memory chip.

Mechanical construction matters as much as logic design. Use a keyed connector or clear orientation marks, provide mounting points, and avoid a board outline that can touch adjacent metalwork. A small enclosure or insulating sheet can prevent accidental shorts. Label the address range, battery type, revision, and replacement date directly on the module so that future maintenance does not depend on a separate note.

Prepare And Verify The Host Computer

The expansion module should be tested on a machine with a known-good power supply and stable reset behavior. A board that draws excessive current or responds incorrectly can make a healthy X68000 appear defective. Power supply repairs and analog-board work are separate from SRAM installation, but general system health still matters; stable digital operation begins with clean rails and a dependable reset circuit. The documented process for stable RGB output illustrates why careful board-level maintenance is valuable before adding new hardware.

Start testing with the battery removed or disconnected. Verify ground continuity, supply voltage, and the absence of shorts between adjacent connector pins. Then check the decoder with an oscilloscope or logic analyzer while a diagnostic program performs reads and writes inside the intended address window. Probe chip enable, output enable, write enable, the byte strobes, and data lines rather than relying only on software results.

The first software test should use a walking-bit pattern, alternating values, and address-dependent data. These patterns expose stuck data lines, swapped address lines, incorrect byte-lane wiring, and decoder aliasing. Follow them with word, even-byte, and odd-byte accesses. If the board uses two SRAMs, verify that each half responds only to its intended strobe.

After normal operation is confirmed, shut the computer down and measure the battery-backed rail. Wait several minutes, power the machine on again, and verify that the test signature remains intact. Repeat the test after a reset, after a complete power removal, and after reconnecting the expansion board. A memory module that survives a warm reset but loses data during power-off has a backup-path or standby-control fault.

Compare Common Design Choices

The following choices help narrow the design before schematic capture. They are not substitutes for reading the selected components’ datasheets, because similarly named memory parts can differ substantially in pinout and electrical behavior.

Design Decision Conservative Choice Why It Helps
Memory organization Two 8-bit SRAMs for a 16-bit bus Makes byte strobes explicit
Address selection Jumper or DIP-configurable decoder Allows conflict testing and future software
Bus isolation Dedicated transceivers Limits loading and simplifies troubleshooting
Backup source Replaceable non-rechargeable cell with isolation Reduces maintenance ambiguity
Power monitoring Supervisor with SRAM inhibit Prevents brownout writes
Initial capacity 32–128 KB Easier validation and lower standby current
Testing method Diagnostic ROM or bootable test program Confirms real bus cycles, not just continuity

Configurable address selection is useful during development, but it should not become an excuse for undocumented settings. Print the switch positions and mapped range on the PCB or in the software documentation. If the design eventually settles on one address, fixed decoding may reduce accidental conflicts and simplify production.

A socketed SRAM can be convenient during early experiments, while a soldered device is mechanically stronger for a permanent board. Modern FRAM is attractive when battery maintenance is undesirable, but it may have different write timing, endurance behavior, voltage requirements, and bus organization. It should be evaluated as a separate peripheral design rather than assumed to be a drop-in SRAM substitute.

Recommendations For A Reliable Module

A practical build benefits from a disciplined sequence rather than from adding every possible feature at once. Keep the first revision small, expose test points, and document every assumption about the X68000 bus.

  • Begin with a modest SRAM capacity and a fixed, well-documented address window.
  • Use a removable battery holder and include explicit isolation against charging or reverse current.
  • Add a supervisor or equivalent inhibit circuit to prevent writes during supply collapse.
  • Test byte, word, reset, and complete power-cycle behavior before installing the module permanently.
  • Record the measured off-state current, battery type, chip revisions, and decoder settings.

The module should also have a software identity. A small diagnostic utility can report the detected address window, fill the memory with patterns, verify retention, and display the board revision. If the memory is intended for applications, reserve a header with a magic value, version number, size field, and checksum. This prevents old data from being mistaken for valid configuration after a firmware change.

Finally, publish the schematic, pin assignments, timing assumptions, and test results with the hardware. The X68000 community benefits when a board can be repaired or reproduced years later, even if its original builder is unavailable. Clear documentation turns a one-off expansion into a useful preservation resource.

A battery-backed SRAM module is a manageable project when its responsibilities are separated: the decoder selects the address range, the bus interface handles timing and byte lanes, the SRAM stores data, and the power circuit preserves contents safely. Build the first revision around measured signals rather than assumptions, validate it through complete power cycles, and document the finished design so it can remain useful alongside the X68000 for many years.

Nereid-X Expansion Board

A personally-produced LAN+USB+Memory expansion board for Sharp X68000 series computers. Multiple production runs were offered, including a final batch and a later revival reproduction run.

Power Supply Repair

X68 power supply repair and modification services were offered by the site owner, with documentation shared through diary entries spanning 2001–2006.

Server & Networking

Notes on FreeBSD administration, ISP changes, server migration, and networking topics. The site itself ran on FreeBSD with the hns diary system and Namazu search integration.

A two-ink risograph print in muted slate-blue and charcoal on off-white paper, showing a stylized desktop computer monitor beside a circuit board with soft geometric trace lines, conveying a calm retro-computing workshop atmosphere. A two-ink risograph print in deep purple and dark grey on cream stock, depicting a compact expansion card with connector ports and subtle Japanese technical annotations, evoking a hobbyist electronics bench. A two-ink risograph print in teal and charcoal on warm white paper, showing a server rack silhouette with soft network-line motifs and a small weather icon, suggesting a personal server room corner.

Get in touch

X68K.NET connects Sharp X68000 enthusiasts through community links and shared projects. Reach out with questions about the Nereid project or X68 resources.