I’m currently finishing up my updates for Pollen8+FM, and I’ve made the decision to remove the fatfs file system for saving patches to SD, and to replace it with the QSPI - as the fatfs system was taking up more flash than I had room for.
My concern with this, is that I’m sure people are already using the QSPI flash for saving other “stuff” (I believe owlsy uses this, not sure about oopsy or any other projects).
While I’m currently trying to make the impact as minimal as possible (by looking for a large contiguous 0xFF blank space to store the rudimentary file system), I just wanted to judge the kind of impact messing with the QSPI flash would have on people’s “other” projects - e.g. I wouldn’t want to be the cause of a scenario where you’ve been in the middle of working with something, and upload the new synth to try it out only to wipe out any other save data etc. Implementing an “are you sure?” function on the field / patch is admittedly a bit easier to implement vs the pod, and this synth supports all 3 modules.
Do note - I haven’t tried owlsy or oopsy or any other projects that use the qspi flash at this time, so I am not familiar with how the flash data is being used, so this might be moot anyway if it can all be re-downloaded with ease from a PC etc…
Please let me know your thoughts if you have any / have a chance!