|
|
|
|
|
by samueldr
1370 days ago
|
|
I wonder if it will have proper CCD (Case Closed Debugging)[0] support. With CCD, you are pretty much free to mess around with the "BIOS" of the machine, without fear of being put in a bad situation. It also provides a serial terminal to the "AP" (application processor), e.g. available to the OS. In other words, the Cr50 provides a controlled and user-controlled (but not user-owned) sideband channel to debug the system, even on consumer hardware. Why user-controlled? Because it requires asserting presence to "Open", which with the design of ChromeOS basically requires being the owner of the device. Why not user-owned? For official ChromeOS devices, AFAIK that firmware cannot be replaced by a user with their own builds. [0]: https://chromium.googlesource.com/chromiumos/platform/ec/+/c... |
|