OTA programming

[SteveCS]

Hi

I know Teensy's don't support OTA programming, but do you think it would be possible to remotely implement?
We have multiple controllers running 3.2's and the customer now wants OTA capability. That means ripping them apart and fitting ESP32's or something.

Just wondered if 'in theory' it could be achieved (I realise it's not simple)

[MichaelMeissner]

You might look at https://github.com/joepasquariello/FlasherX. I've not used it, but it claims to work on Teensy LC, 3.x, and 4.x's. There are threads roaming around that mention this software and OTA programming.

[joepasquariello]

You might look at https://github.com/joepasquariello/FlasherX. I've not used it, but it claims to work on Teensy LC, 3.x, and 4.x's. There are threads roaming around that mention this software and OTA programming.

I can confirm that it works for all Teensy LC/3.x/4.x/MM. The sketch on github is a demo that lets you update firmware via UART for any Teensy or via SD for 3.5/3.6/4.1 with built-in SD card. For T3.2, the new firmware is buffered in upper flash, so your sketch must be less than 1/2 of the size of flash. You can read about it further in this thread.

https://forum.pjrc.com/threads/43165...l=1#post317080

[SteveCS]

Brilliant. I will have a look at that

Thanks for your time.
I will look into how I actually wire this all up.

[joepasquariello]

Brilliant. I will have a look at that

Thanks for your time.
I will look into how I actually wire this all up.

Read the github readme info. The way that I use it in "production" is by reading the hex file into a Windows HMI program and sending the firmware to Teensy as larger blocks of binary data. On the Teensy side, I receive the packets containing the data and buffer them to flash, confirm that the new firmware is complete and correct (CRC), then erase the old firmware and write the new firmware.