Additional RPi Pico W OTA Example: OTALedFlash

[djaus2]

In GitHub djaus2/Soft-ata/Misc

An example Sketch for OTA (Over-The-Air) updating of a RPi Pico W.
Similar to examples in /libraries/ArduinoOTA/examples especially the first 2. This one just uses the Inbuilt LED with coded flashes to indicate where the sketch is at. Number of pulses and length of each is different at different points in boot/OTA events.

[earlephilhower]

Maybe we could output Morse code instead! 😆

Anyway, this does freeze the OTA process while flashing. Look at the Ticker library for a way of doing that timed flashing w/o needing to busywait the device. I'm a little worried that some OTA processes may think the device is DOA if it hangs w/o response for too long...

[djaus2]

Yeah I thought of Morse Code! I did find if the OTA start event handler flashing took too long there was an upload error, so I made it short. David Jones (MVP)

…

________________________________ From: Earle F. Philhower, III ***@***.***> Sent: Saturday, July 13, 2024 5:20:20 AM To: earlephilhower/arduino-pico ***@***.***> Cc: David Jones (MVP) ***@***.***>; Author ***@***.***> Subject: Re: [earlephilhower/arduino-pico] Additional RPi Pico W OTA Example: OTALedFlash (Discussion #2260) Maybe we could output Morse code instead! 😆 Anyway, this does freeze the OTA process while flashing. Look at the Ticker library for a way of doing that timed flashing w/o needing to busywait the device. I'm a little worried that some OTA processes may think the device is DOA if it hangs w/o response for too long... — Reply to this email directly, view it on GitHub<#2260 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC7U2EK23ZYRFA4K5MRXWZTZMAT7JAVCNFSM6AAAAABKYNQ4NGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBTGUYTIMQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[djaus2]

And I'll have a look at the Ticker library. What happens if a process is running in the second CPU when an OTA update occurs? David Jones (MVP)

…

________________________________ From: David Jones (MVP) ***@***.***> Sent: Saturday, July 13, 2024 6:18:53 PM To: earlephilhower/arduino-pico ***@***.***> Subject: Re: [earlephilhower/arduino-pico] Additional RPi Pico W OTA Example: OTALedFlash (Discussion #2260) Yeah I thought of Morse Code! I did find if the OTA start event handler flashing took too long there was an upload error, so I made it short. David Jones (MVP)

________________________________ From: Earle F. Philhower, III ***@***.***> Sent: Saturday, July 13, 2024 5:20:20 AM To: earlephilhower/arduino-pico ***@***.***> Cc: David Jones (MVP) ***@***.***>; Author ***@***.***> Subject: Re: [earlephilhower/arduino-pico] Additional RPi Pico W OTA Example: OTALedFlash (Discussion #2260) Maybe we could output Morse code instead! 😆 Anyway, this does freeze the OTA process while flashing. Look at the Ticker library for a way of doing that timed flashing w/o needing to busywait the device. I'm a little worried that some OTA processes may think the device is DOA if it hangs w/o response for too long... — Reply to this email directly, view it on GitHub<#2260 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC7U2EK23ZYRFA4K5MRXWZTZMAT7JAVCNFSM6AAAAABKYNQ4NGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBTGUYTIMQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[earlephilhower]

Absolutely nothing, the 2nd core isn't aware. OTA just writes a file to the internal LittleFS filesystem. When all data's in the file, it then reboots. This ensures all-or-nothing updates.

[djaus2]

Ok thanks, that is quite clear. David Jones (MVP)

…

________________________________ From: Earle F. Philhower, III ***@***.***> Sent: Sunday, July 14, 2024 4:26:22 AM To: earlephilhower/arduino-pico ***@***.***> Cc: David Jones (MVP) ***@***.***>; Author ***@***.***> Subject: Re: [earlephilhower/arduino-pico] Additional RPi Pico W OTA Example: OTALedFlash (Discussion #2260) Absolutely nothing, the 2nd core isn't aware. OTA just writes a file to the internal LittleFS filesystem. When all data's in the file, it then reboots. This ensures all-or-nothing updates. — Reply to this email directly, view it on GitHub<#2260 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC7U2EIVAAW5ODN5WQSENCDZMFWM5AVCNFSM6AAAAABKYNQ4NGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBUGAZDMMI>. You are receiving this because you authored the thread.Message ID: ***@***.***>