Actions
Bug #52
closedChromeOS verified boot is not executed on nyan_big, causing various issues
Start date:
05/08/2016
Due date:
% Done:
0%
Estimated time:
Affected versions:
Needs backport to:
Affected hardware:
Affected OS:
Description
VbInit is apparently never called in the current coreboot master, resulting in various issues such as the TPM not being properly initialized and resulting in depthcharge always rebooting to recovery:
Starting depthcharge on nyan_big...
The GBB signature is at 0x83004020 and is: 24 47 42 42
Calling VbSelectAndLoadKernel().
ec_init(0): CrosEC protocol v3 supported (544, 544)
Google ChromeOS EC driver ready, id 'big_v1.1.1807-2252740'
Clearing the recovery request.
PARAM_LIMIT_POWER not supported by EC.
TPM: TlclRead(0x1008, 13)
1.2 TPM (chip type slb9645tt device-id 0x1A)
TPM: command 0xcf returned 0x26
Rollback: 00000026 returned by ReadSpaceKernel(&rsk)
Unable to get kernel versions from TPM
VbSetRecoveryRequest(84)
VbSelectAndLoadKernel() returning 65545
VbSelectAndLoadKernel returned 65545, Doing a cold reboot.
Files
Updated by Paul Kocialkowski almost 8 years ago
It turns out the v1 vboot API is no longer supported by Coreboot as it was replaced with the v2 API. However, verstage and related options are not selected when enabling CHROMEOS with Nyan Big. Selecting the right options makes it start verstage and call the vboot API. However, an exception occurs when returning from verstage, as seen in the attached log.
Updated by Paul Kocialkowski almost 8 years ago
- Subject changed from VbInit is never called when using ChromeOS and verified boot, causing various issues to ChromeOS verified boot is not executed on nyan_big, causing various issues
- Category set to board support
- Status changed from New to In Progress
Updated by Paul Kocialkowski almost 8 years ago
- Status changed from In Progress to Resolved
- Assignee set to Paul Kocialkowski
Fixed with http://review.coreboot.org/#/c/15451/
Actions