PINE64

I was interested to read in the September update about a PineTime manufacturing issue ("involved the memory protection, which was still enabled") that there are plans to fix.

I understood the memory protection is part of the APPROTECT register in the UICR flash page and can therefore be set or cleared by an OTA update. Certainly I was planning to update the wasp-reloader to ensure that it is capable of updating the UICR to ensure it will automatically clear the protection bits during an OTA update.

Does that sound right?

(09-18-2020, 02:44 AM)danielt Wrote: [ -> ]I was interested to read in the September update about a PineTime manufacturing issue ("involved the memory protection, which was still enabled") that there are plans to fix.

I understood the memory protection is part of the APPROTECT register in the UICR flash page and can therefore be set or cleared by an OTA update. Certainly I was planning to update the wasp-reloader to ensure that it is capable of updating the UICR to ensure it will automatically clear the protection bits during an OTA update.

Does that sound right?

The upcoming batch PineTime already has the protection set as disable.

according to this site:

https://www.cnx-software.com/2020/07/22/...rtwatches/

they say they can update our PineTime watches with the protection  OTA.

I haven't tried it, though

(09-20-2020, 06:05 PM)Alho Wrote: [ -> ]according to this site:

https://www.cnx-software.com/2020/07/22/...rtwatches/

they say they can update our PineTime watches with the protection  OTA.

I haven't tried it, though

I have been able to OTA update some other nRF52832 watches but since I've done that on watches that have the backs glued on I've not been able to tell if OTA updates can be used to unset (or indeed set) the protection bits.

I was curious... and I guess if I add UICR to the reflashing tools I'll be able to find that out for myself!