Mostly Non-Volatile Memory With Supercapacitors

Back in the days of old, computers used EPROMs to store their most vital data – usually character maps and a BASIC interpreter. The nature of these EPROMs meant you could write to them easily enough, but erasing them meant putting them under an ultraviolet light. Times have changed and now we have EEPROMs, which can be erased electronically, and Flash, the latest and greatest technology that would by any other name be called an EEPROM. [Nicholas] wanted an alternative to these 27xx-series EPROMs, and found his answer in supercapacitors.

[Nick]’s creation is a mostly non-volatile memory built around an old 62256 32k SRAM. SRAM is completely unlike EPROMs or Flash, in that it requires power to keep all its bits in memory. Capacitor technology has improved dramatically since the 1980s, and by using a supercap and one of these RAM chips, [Nick] has created a substitute for a 27-series EPROM that keeps all its memory alive for days at a time.

The circuit requires a small bit of electronics tucked between the EPROM socket and the SRAM chip; just enough to turn the 12 Volts coming from the EPROM programming pin to the 5 Volts expected from the SRAM’s Write Enable pin. This is accomplished by a few LEDs in series, and a 0.1F 5.5V supercap which keeps the SRAM alive when the power is off.

As for why anyone would want to do this when modern technologies like Flash can be found, we can think of two reasons. For strange EPROM sizes, old SRAMs abound, but a suitable Flash chip in the right package (and the right voltage) might be very hard to find. Also, EEPROMs have a write lifetime; SRAMs can be written to an infinite number of times. It’s not the best solution in every case, but it is certainly interesting, and could be useful for more than a few vintage computing enthusiasts.

This project makes us think of another where an LED may have been supplying keep-alive power to some volatile memory.

26 thoughts on “Mostly Non-Volatile Memory With Supercapacitors

      1. A company I previously worked at used those Dallas modules in an automotive datalogger. This was before flash was cheap or large enough to safely deal with rolling buffers, so NVSRAM was a good option. It also had to be readable following an accident, and an offchip battery wouldn’t have been reliable enough.

    1. Like the old Timekeeper RTC chips (M48T08) with a lithium battery and quartz in a piggyback package.
      Used in old Sun workstations and various old gear.

      They can be repaired, cutting into the epoxy to solder another battery, when the former eventually dies, after 10 years.

  1. So paired with a uC you could concievable charge the Supercap from a Lipo pack feeding through a 5V boost and/or a solar setup? I’m thinking 512k SRAM might hold a lof of data for outdoor sensors cheaper than adding in an SD logger, an I would already being powering them off something (batter/solar).

    I’ve never used supercaps before: can you easily check/estimate the charge state as in add a little code when the uC is running to make sure the supercap is charged before putting it back to sleep?

      1. You’ll have to ask a lawyer about that. The invention was intended to do almost exactly what an NVDIMM does, but the patent is written as a fail-over mechanism. It could go either way in court.

  2. We did that at work some 20 years ago. We had no debbugers so trial and error writing tens of EPROMs per hour was the way of programming, this saved a few seconds here and there,,,

  3. But why use a supercap and not just a CR2032 or similiar lithium battery? That would hold the memory contents for years. Retro computer users don’t always turn them on daily, so a longer memory retention time would be preferable.

    Unfortunately, there are some old systems where this stack wouldn’t work since it’s too high, there you’re still limited to using the actual EPROMs (which can still be bought easily).

    1. I wouldn’t trust this design for a BIOS ROM. The original point was to have a way to deal with MCU projects where you change the code many times in a day, so you don’t need to mess with UV erase boxes or have a stack of blanks on hand.
      I did try a CR2032, but I couldn’t figure out a good way to attach the bulkier cell/holder and I wasn’t able to come up with a small enough circuit to switch from the battery to VCC. I’m sure there’s a way to do it and it would absolutely make more sense for most applications.

  4. Wouldn’t the cost of all the parts here be more than just getting an oversized conventional 27 or 29 series and piggybacking it off an adapter board for just the relevant address lines and wiring it like RAM?

  5. Alliance sells a number of cheap SRAM chips that are pin-compatible with the old 62xxx series, and have a standby mode that will probably let you retain the data in a 32KB chip a lot longer than an original 62256. The AS6C62256 uses only 1 micro-Ampere (typical) when you deassert CE#, and retains data until the supply voltage drops under 2.0V. See

    They also sell SRAM chips that have more memory capacity than Ye Olde 62256: the largest DIP chip that they have (AS6C4008-55PCN) is a whopping 512 Kilobytes(!), and if SMD is okay you can go up to 2 Megabytes (AS6C1608) or 2 Megawords (32Mbits x 16bits, AS6C3216).

    (No, I don’t work for them ;-)

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.