<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MRAM and FRAM on Precomputing.com</title>
    <link>https://precomputing.com/tags/mram-and-fram/</link>
    <description>Recent content in MRAM and FRAM on Precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.com/tags/mram-and-fram/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AltSql Instant: A Battery-Free Sensor on MRAM Saved 1,428 Readings in a Simulated Minute, Against 220 for AltSql Core on Flash</title>
      <link>https://precomputing.com/altsql-instant-a-battery-free-sensor-on-mram-saved-1428-readings-in-a-simulated-minute-against-220-for-altsql-core-on-flash/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/altsql-instant-a-battery-free-sensor-on-mram-saved-1428-readings-in-a-simulated-minute-against-220-for-altsql-core-on-flash/</guid>
      <description>&lt;p&gt;Some sensors have no battery. A small solar cell charges a capacitor, and when it is full the sensor wakes and works until the charge runs out. Then the power goes, wherever the sensor happens to be. It might be between readings or in the middle of writing one. Every bit of energy spent on storage is a reading not taken.&lt;/p&gt;&#xA;&lt;p&gt;Flash memory makes this hard. It writes in pages and has to erase before it can write again, so a storage engine for flash keeps a log and cleans it up later. MRAM and FRAM work differently. They write single bytes, need no erase and keep what was written the moment the write ends.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
