@Paul:
Hello Paul,
on my short trip to the ESP32 world i learned to enjoy the "preferences" library.
It is very handy because it allows to store key/value pairs. This could be a PIN assignment, volume or filter settings, for example. These are retained even when reflashing.
It is similar to a config file, but binary.
So that different programs can use them, there is a parent namspace. For example, the same key can be stored for "Sketch1" and "Sketch2" (and have different values)
"preferences" is the name of the Arduino interface, in the IDF it is called Non-volatile storage library. (link to docu)
My question now: Teensy 4.x has some flash free at the top end.
Can this be used partially? I assume you need less than the 64k.
Is the area partially writable?
Will it be erased when flashing (I hope not) ?
For example, if you could use 48K of it, that would be a practical thing.
If that doesn't work - is there any other way to reserve some memory that is not erased?
Something like EEPROM emulation?
Hello Paul,
on my short trip to the ESP32 world i learned to enjoy the "preferences" library.
It is very handy because it allows to store key/value pairs. This could be a PIN assignment, volume or filter settings, for example. These are retained even when reflashing.
It is similar to a config file, but binary.
So that different programs can use them, there is a parent namspace. For example, the same key can be stored for "Sketch1" and "Sketch2" (and have different values)
"preferences" is the name of the Arduino interface, in the IDF it is called Non-volatile storage library. (link to docu)
My question now: Teensy 4.x has some flash free at the top end.
Can this be used partially? I assume you need less than the 64k.
Is the area partially writable?
Will it be erased when flashing (I hope not) ?
For example, if you could use 48K of it, that would be a practical thing.
If that doesn't work - is there any other way to reserve some memory that is not erased?
Something like EEPROM emulation?