Hello Paul
1.)
I could not find information if the Teensy 3.2 protects the flash memory from reading.
I know that there are other micro controllers that allow to read the flash memory with the stored program code out.
How does Teensy 3.2 manage this ?
Can anybody read my compiled sketch out of a Teensy 3.2 ?
2.)
And what about RAM content.
Supposed I have a sketch code that works with cryptographic keys.
Supposed that an attacker wants to make a memory dump of the Teensy RAM memory to serach for any interesting information, would it be possible that he uploads another sketch to the Teensy that dumps all the RAM ?
Or is the entire RAM erased, when a new sketch is uploaded ?
1.)
I could not find information if the Teensy 3.2 protects the flash memory from reading.
I know that there are other micro controllers that allow to read the flash memory with the stored program code out.
How does Teensy 3.2 manage this ?
Can anybody read my compiled sketch out of a Teensy 3.2 ?
2.)
And what about RAM content.
Supposed I have a sketch code that works with cryptographic keys.
Supposed that an attacker wants to make a memory dump of the Teensy RAM memory to serach for any interesting information, would it be possible that he uploads another sketch to the Teensy that dumps all the RAM ?
Or is the entire RAM erased, when a new sketch is uploaded ?