@Dennis, I misread the code. I was wrong. The wait is only called in the .finish() that concludes a write of bytes. Nice of this implementation is that the chip can be asked and when ready move on. Some implementations justs make sure to be time-wise on the safe side with a kill time.
Did you know that FRAM/MRAM technology does not a wait or erase? ...and it is fast: 40MHz clock rate. I 'glued' such a chip on my classical Espruino 1.3 board. The chip is pin AND command compatible with the standard EEPROM chips... even though the commands are not needed. Large capacities are though not in hacker standard package and therefore not as prevalent as EEPROMS. FRAM/MRAM is more like a non-volatile RAM that does not backup power.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Dennis, I misread the code. I was wrong. The wait is only called in the .finish() that concludes a write of bytes. Nice of this implementation is that the chip can be asked and when ready move on. Some implementations justs make sure to be time-wise on the safe side with a kill time.
Did you know that FRAM/MRAM technology does not a wait or erase? ...and it is fast: 40MHz clock rate. I 'glued' such a chip on my classical Espruino 1.3 board. The chip is pin AND command compatible with the standard EEPROM chips... even though the commands are not needed. Large capacities are though not in hacker standard package and therefore not as prevalent as EEPROMS. FRAM/MRAM is more like a non-volatile RAM that does not backup power.