Cypress FRAM
It's very interesting. Wouldn't it be only 500kB though? The density has to improve a lot before we could consider it for data storage.
————

I was thinking of a couple of things:

  • There is a long-term data storage challenge, but saving stuff to a uSD card is thristy work.  To make sure nothing get's lost you have to write often.  Writing partial-pages is bad because the whole page has to be erased (v. expensive as I understand it) and re-written.  So you get to save power at the risk of losing data occasionally.   The alternative is to have a non-volatile FRAM cache.
  • The other challenge is on-board signal processing, and pattern recognition.  The technique is to build a tree-structured pipeline of filters that makes a single pass over the data.  The windows can get large and the intermediate results are cached to avoid unnecessary read/writing.  Obviously there isn't enough RAM to do much of that, but 500kB could make a difference. 
Too early to think about much yet, but worth keeping an eye on options.  Does the new Nordicchip have the ability to extend it's address space with FRAM?  Can code be run from FRAM.  Code runs faster out of normal RAM.

//Mik

On Thu, Jul 9, 2015 at 9:26 AM, David Carkeek <dcarkeek@gmail.com> wrote:

It's very interesting. Wouldn't it be only 500kB though? The density has to improve a lot before we could consider it for data storage.

On Thu, Jul 9, 2015 at 9:06 AM, Mik Lamming <mik@lamming.com> wrote:

Leave a Reply