We talked about how to record data. A MicroSD card is too large for a ring, obviously. However, a uSD card is good because it contains a controller that takes care of things like mapping bad memory sectors and doing load leveling. It’s not clear to me whether or not these functions need to be performed with a discrete flash memory IC.

Here is an SPI-connectable 1G-bit flash chip from Micron that is only 6mm x 8mm:
This device has 4 stacked 256 M-bit die. The memory is therefore arranged as 256Mbx4, or 128 M-Bytes. 

I am hoping that this device could be used both for data storage and program storage. For example, if the Dialog  DA14580 were used, the program could be loaded from the memory device to the 42kB system RAM.

If there were swapping involved that would most likely kill the power budget. After development is completed the OTP memory of the DA14580 could be used. Maybe an OTP memory saves some power.

Writing data to a flash memory takes a lot of power. Maybe it’s not practical to consider it.

Adesto 32Mbit memory, 6mm x 6mm BGA:  http://www.adestotech.com/sites/default/files/datasheets/doc3686.pdf

1 thought on “Memory

  1. 128MB should be enough to get started. I did some worst case estimation for data generated / day.

    Mapping bad sectors, and load leveling seem like important things. It would be a show stopper to worry about that kind of thing. Just keeping track of the bad blocks is a pain.

    Can you compare and contrast the DA14580 memories please?
    Would the OTP be used for a OTA bootloader?
    Does it execute out of the ROM?
    What's the difference between the System SRAM and the Retention SRAM

    If there is the least chance of having to do swapping, then we should choose a chip with more memory – like the EFM32LG330F256

Leave a Reply