A/B partitioning (supported in the latest SDK), and other options to disable USB boot (in the OTP) to prevent anything being downloaded at all.If that's addressed at me I can assure you I do understand chapters. I have written many datasheets and much documentation and user manuals myself. I have no idea what the Terry Pratchett reference relates to.I guess the concept of chapters has passed you by. Terry Pratchett would be proud.
What I mean about not liking the way Raspberry Pi do things is in putting it all in one document - overview, detailed explanations, hardware references, example code, register lists and bit definitions all inter-mingled.
I prefer separate documents for overview and explanations, app notes and code examples, technical details. Separate datasheets on specific topics.
That's how others do it and I just prefer it.It's not breaking it I was concerned about - It was some rogue foisting it upon others and effectively 'bricking' their Pico 2 I was wondering about, what protections exist to prevent that happening ?As for security, the chip has been in the hands of white hat security companies for a couple of months who have been trying to break the security, so far to no avail.Exactly that. If I can trick you into loading a rogue '.uf2', which then secures your Pico 2, requires you to sign everything just to upload again ... how will you ever do that when you don't know the hidden incantation, have no way to get at it ?I would expect that you cannot download an unsigned image to the EEPROM on a protected system to break it.
I have effectively rendered your Pico 2 unusable.
This is all covered in the documentation.
Statistics: Posted by jamesh — Fri Aug 09, 2024 3:02 pm