I can’t find that spec in any of the documentation.
Quote from muff’s - “Meta us running an dual-core 800MHz Cortex-A7 plus Cortex-M4 co-processor with 512MB DDR3 Ram”
Yeah, I saw the RAM amount. I was referring to internal (persistent) storage. Where the demo and temp files live. It is also listed as a target for your own files.
The FLASH chip is 16MB, but that holds firmware (13.5MB max), the bootloaders (0.5MB), some calibration values (some small amount <1kB), and the patch storage drive (just under 2MB).
That isn’t a lot of flash memory. Anyway to make temp files use a SD card or USB to reduce writes and to extend the life of the flash memory?
What temp files do you mean?
Untitled Patch files. Aren’t those written to flash?
i think the best idea is to immediately save any new patches to the sdc or usb and wear those drives out instead. since sdc or usb are easily replaceable. and maybe only keep the most important, completely finished ymls stored on the internal for read only. regardless i would think it would take many years of everyday use to wear out an sdc writing these typically 20kb yml files. just my opinions there.
Oh, no, they live in RAM. If you save them to the “Internal” drive (as opposed to USB or SDCard) then they will be written to FLASH. But only if you do that.
OK, now I have a better understanding. Thanks for that info!
No problem, yeah the Internal drive (aka FLASH) is used sparingly. It came up in another thread that you have to hit Back to exit the Plugins page before it will save the settings file. The reason is that the settings file lives in FLASH, and we minimize the writes to it, so we just do it once when you exit the page rather than every time you check/uncheck “autoload” for each plugin
Yeah, I saw that. It was what got me thinking about internal flash sides and writes.