+- PINE64 (https://forum.pine64.org)
+-- Forum: PineTime (https://forum.pine64.org/forumdisplay.php?fid=134)
+--- Forum: General Discussion on PineTime (https://forum.pine64.org/forumdisplay.php?fid=135)
+--- Thread: Stuck in OTA update mode (/showthread.php?tid=14615)
Stuck in OTA update mode - mark1250 - 08-09-2021
So I thought I would try out wasp-os on my pinetime. It was running the infinitime 1.0 bootloader and 1.2/1.3 OS.
I downloaded and unzipped the wasp-os-0.4.1 file from https://github.com/daniel-thompson/wasp-os/releases. I used nrfconnect to push the reloader-mcuboot.zip file from the build-pinetime folder to the pinetime. (I watched Daniel's YouTube video from November 2020 & followed the steps he outlined)
The watch rebooted and the pinecone changed from blue to white.
I reconnected nrfconnect with the pinetime and attempted to push the micropython.zip file to the pinetime, but it would get to 1% the watch would blink the pinecone is white with start and a white bluetooth symbol. I can reconnect (most of the time the phone & pinetime automatically connect), but I can't get past 1% and the cycle continues.
So I thought I would go back to infinitime by pushing the reloader-factory.zip, but the same thing happens - bluetooth disconnect, white pinecone, start-whitepinecone-whitebluetooth, whitepinecone-bluebluetooth.
How do I get my pinetime back?
Thanks.
Mark
RE: Stuck in OTA update mode - mark1250 - 08-11-2021
I installed nrfconnect on my work android phone to see if that would allow me to upload the micropython.zip file to the phone, but nrfconnect just kept crashing.
I searched more on the internet and found in the wasp-os installation guide a section on using tools directly on Linux.
Namely;
Code:
python3 dfu.py -z micropython.zip -a A0:B1:C2:D3:E3:F5 --legacySuccess!
Now, off to explore wasp-os
RE: Stuck in OTA update mode - danielt - 08-16-2021
(08-11-2021, 07:22 AM)mark1250 Wrote: Success!
Now, off to explore wasp-os
Great to hear that you got this sorted!
RE: Stuck in OTA update mode - horalocal - 08-18-2021
Quickly chiming in to note that this worked for me as well (thanks!) and add the detail (for searchability) that without the --legacy option I got:
Code:
Exception at line 166: UUID not found: 8ec90001-f315-4f60-9fb8-838830daea50One of those things that makes sense, but only after figuring it out; that UUID is the one corresponding to the "secure" service. Now that I'm thinking about it, seems like it should be possible to fall back to legacy when the device doesn't support secure (can probably submit a patch to this end if others agree).
I wonder if legacy mode is related to why nRF Connect is failing in this case? Apparently it should be compatible, but perhaps a flag/mode needs to be set somewhere (and I didn't see one in a quick pass through the UI). Quite new to all this, so a bit of a shot in the dark
RE: Stuck in OTA update mode - feketej - 06-01-2023
(08-18-2021, 10:49 PM)horalocal Wrote: Quickly chiming in to note that this worked for me as well (thanks!) and add the detail (for searchability) that without the --legacy option I got:
Code:Exception at line 166: UUID not found: 8ec90001-f315-4f60-9fb8-838830daea50
One of those things that makes sense, but only after figuring it out; that UUID is the one corresponding to the "secure" service. Now that I'm thinking about it, seems like it should be possible to fall back to legacy when the device doesn't support secure (can probably submit a patch to this end if others agree).
I wonder if legacy mode is related to why nRF Connect is failing in this case? Apparently it should be compatible, but perhaps a flag/mode needs to be set somewhere (and I didn't see one in a quick pass through the UI). Quite new to all this, so a bit of a shot in the dark
Hello horalocal,
I've had the same issue, that I managed to resolve thanks to mark1250. Daniels video is absolutely misleading I've tries rNF connect, I tried DaFlasher, I tried Siglo, I tried Gadgetbridge, NONE OF THEM WORKED.
So I used the command line, as everyone should who buys pinetime, and it worked on third attempt:
#first attempt:
python3 dfu.py -z ./micropython.zip -a EB:8B:CE:98:3F:BE
Sending file firmware.bin to EB:8B:CE:98:3F:BE
Binary imge size: 299440
Binary CRC32: 1549834072
Connecting to EB:8B:CE:98:3F:BE
Couldn't connect, will try DFU MAC
Connecting to EB:8B:CE:98:3F:BF
Exception at line 166: UUID not found: 8ec90001-f315-4f60-9fb8-838830daea50
#second attempt:
python3 dfu.py -z ./micropython.zip -a EB:8B:CE:98:3F:BE --legacy
Sending file firmware.bin to EB:8B:CE:98:3F:BE
Binary imge size: 299440
Binary CRC32: 1549834072
Connecting to EB:8B:CE:98:3F:BE
Couldn't connect, will try DFU MAC
Connecting to EB:8B:CE:98:3F:BF
Waiting for Image Size notification
Exception at line 166: Error in START_DFU procedure, reason: INVALID_STATE
#Third attempt:
python3 dfu.py -z ./micropython.zip -a EB:8B:CE:98:3F:BE --legacy
Sending file firmware.bin to EB:8B:CE:98:3F:BE
Binary imge size: 299440
Binary CRC32: 1549834072
Connecting to EB:8B:CE:98:3F:BE
Couldn't connect, will try DFU MAC
Connecting to EB:8B:CE:98:3F:BF
Waiting for Image Size notification
Waiting for INIT DFU notification
Begin DFU
[##################################################] 100.0% (292 of 292 kb)
Upload complete in 5 minutes and 2 seconds
Waiting for DFU complete notification
Waiting for Firmware Validation notification
Activate and reset
Okay, so tha --legacy parameter is mandatory, and you also need to restart the pinetime after each attempt, because BLE is a fkin unstable heap of trash just like all those android apps out there!!