by antto » Wed Dec 26, 2012 6:10 pm
EEPROM has a certain amount of "writes" before it starts to fail
so if you write to the eeprom very often for a long period of time, at some point you should expect to get wrong bits
i'm not saying that's the case, but it's good to be aware of it (specifically developers)
certainly the fact that the stock firmware saves the tempo immediately when it changes is a bad idea
also, don't abuse your eeprom with c0nb0x/c0ntr0l (that happens when you edit patterns from the app, or import patterns/whole memory)
the external eeprom can be replaced if it goes bad
but you can't replace the internal eeprom, you have to buy the whole microcontroller
still, i don't expect such things to happen soon, the x0xb0x is not so old, is it?
We are here too: irc.freenode.net >>> #x0xb0x
..:: c0nb0x v1.00 ::.. viewtopic.php?f=7&t=29282 (new control app - win/osx)
VCO Tuning: viewtopic.php?f=12&t=24759 (do it the EASY way)