Phil Sznyck
Member
Hello guys, first of all: I'm a musician that learned programming in c via YouTube with the goal of programming a good midi controller for myself. So please keep in mind that I will not understand hex numbers or specific language. I'm also not a native English speaker, I live in Germany.
I've been programming my pedal for over a year now and it's getting quite complex, and that's great. To be easily able to command audio software on my computer I switched from arduino to teensy and it works fine.
My pedal has a 16x2 lcd display and I would love to be able to define what kind of message the buttons and the poti will send, if the buttons are momentary, latching or exclusive latching, or even a package of commands, etc, without connecting it to a computer, using the buttons and the poti only and the lcd screen as reference. And there is where the eeprom becomes interesting, cause normally this button information (variables) are written in the main code and that's why the Chip won't forget them if I power cycle it. So if I want to change this variables without the computer and then have this information stored after a power cycle I'll need to store them in the eeprom, right? In a sum this would mean a minimum of 780 numbers, that's not that much to consider sd cards.
So NOW comes the real question: eeprom normally means a certain number of write cycles, then it's broke. Does this also apply to emulated EEPROM? As I understood the word "emulated" this is not really eeprom, it's flash but works as eeprom. So I thought maybe it doesn't have the write number limitation. I'm aware that it would take a long time to achieve the 10000 times, but 780 variables are also a lot...
I just realised that I wrote quite a lot for a simple question, but often when I ask programming related stuff in forums and social media groups people say they need more information to answer my questions...
However, have a nice day and thanks for reading until this point of the post! ;-)
I've been programming my pedal for over a year now and it's getting quite complex, and that's great. To be easily able to command audio software on my computer I switched from arduino to teensy and it works fine.
My pedal has a 16x2 lcd display and I would love to be able to define what kind of message the buttons and the poti will send, if the buttons are momentary, latching or exclusive latching, or even a package of commands, etc, without connecting it to a computer, using the buttons and the poti only and the lcd screen as reference. And there is where the eeprom becomes interesting, cause normally this button information (variables) are written in the main code and that's why the Chip won't forget them if I power cycle it. So if I want to change this variables without the computer and then have this information stored after a power cycle I'll need to store them in the eeprom, right? In a sum this would mean a minimum of 780 numbers, that's not that much to consider sd cards.
So NOW comes the real question: eeprom normally means a certain number of write cycles, then it's broke. Does this also apply to emulated EEPROM? As I understood the word "emulated" this is not really eeprom, it's flash but works as eeprom. So I thought maybe it doesn't have the write number limitation. I'm aware that it would take a long time to achieve the 10000 times, but 780 variables are also a lot...
I just realised that I wrote quite a lot for a simple question, but often when I ask programming related stuff in forums and social media groups people say they need more information to answer my questions...
However, have a nice day and thanks for reading until this point of the post! ;-)