Stuck in OTA update mode
08-18-2021, 10:49 PM
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:
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
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
