Quantcast
Viewing all articles
Browse latest Browse all 4325

General discussion • Locking threads of technical descussions/HW critisim when Devs do no like critique.

Re: Open Letter to the Raspberry Pi Foundation Development Team
1.) I violated no forum rules.
2.) I simply posted what I believed to be a critical design flaw with the hardware on the RPI zero 2.
3.) I noticed that the devs keep posting and I would like a chance to respond.
4.) forum user "6by9" listed as a dev brings up a critical point:

Zero 2 W uses bootcode.bin from filesystem Not SPI EEPROM like Pi 4/5. This is actually helpful technical clarification BUT this raises MORE questions:

1. Boot Security:
- How is bootcode.bin verified?
- What prevents corruption?
- Where are boot preferences stored?
- How are USB/Network boot settings preserved?

2. Recovery Concerns:
- If bootcode.bin corrupts?
- If SD fails?
- If boot filesystem damaged?
- Still no recovery path!

3. Design Decision:
- Why remove EEPROM safety of Pi 4?
- Why less secure boot path?
- Why no hardware recovery?
- Why step backwards in design?

NEW QUESTION:
"Why did Zero 2 W move away from Pi 4's secure EEPROM boot to a less robust bootcode.bin system with no recovery path?"

Statistics: Posted by blackforestdev — Tue Nov 19, 2024 1:42 pm



Viewing all articles
Browse latest Browse all 4325

Trending Articles