Teensy 4.0 Secure Firmware

Status
Not open for further replies.

HallMark

Well-known member
Somewhere I read about the way we can do encryption for the firmware to secure it in chip.
What options do we have on Teensy 4.0 to secure firmware on chip from readback?
 
Teensy 4.0 does not support this. The fuse bits are set to the unlocked configuration.

We make in the (likely distant) future have a way to support encrypted code, but that is not currently in development. It is unlikely to happen anytime soon, if ever.
 
Teensy 4.0 does not support this. The fuse bits are set to the unlocked configuration.

We make in the (likely distant) future have a way to support encrypted code, but that is not currently in development. It is unlikely to happen anytime soon, if ever.

Is it possible to set fuse bits in case if we will not update Teensy Firmware anymore and fixed with one code?
 
Is it possible to set fuse bits in case if we will not update Teensy Firmware anymore and fixed with one code?

Is there anyway to program our final compiled code externally and lock Teensy forever? It's OK if my Teensy doesn't accept any more future firmware.
 
Status
Not open for further replies.
Back
Top