<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/coreboot/vboot.git, branch firmware-kbl-10431.B</title>
<subtitle>review.coreboot.org: vboot.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/'/>
<entry>
<title>tpm: Add extern "C" declaration for C++ compatibility.</title>
<updated>2018-02-22T12:13:59+00:00</updated>
<author>
<name>Mattias Nissler</name>
<email>mnissler@chromium.org</email>
</author>
<published>2018-01-11T11:34:28+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=4a95b9b7aed292e2c0a02b2bf81b7244ab3b6549'/>
<id>4a95b9b7aed292e2c0a02b2bf81b7244ab3b6549</id>
<content type='text'>
The mount-encrypted utility, which includes tlcl.h is in the process
of being converted to C++. To simplify inclusion in C++ code, add the
standard extern "C" linkage specifiers.

BRANCH=none
BUG=chromium:808303
TEST=compiles

Change-Id: I8a99a0e5cfcce64b27cad10735b08ba40434b222
Reviewed-on: https://chromium-review.googlesource.com/915345
Commit-Ready: Mattias Nissler &lt;mnissler@chromium.org&gt;
Tested-by: Mattias Nissler &lt;mnissler@chromium.org&gt;
Reviewed-by: Vadim Bendebury &lt;vbendeb@chromium.org&gt;
Reviewed-by: Andrey Pronin &lt;apronin@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The mount-encrypted utility, which includes tlcl.h is in the process
of being converted to C++. To simplify inclusion in C++ code, add the
standard extern "C" linkage specifiers.

BRANCH=none
BUG=chromium:808303
TEST=compiles

Change-Id: I8a99a0e5cfcce64b27cad10735b08ba40434b222
Reviewed-on: https://chromium-review.googlesource.com/915345
Commit-Ready: Mattias Nissler &lt;mnissler@chromium.org&gt;
Tested-by: Mattias Nissler &lt;mnissler@chromium.org&gt;
Reviewed-by: Vadim Bendebury &lt;vbendeb@chromium.org&gt;
Reviewed-by: Andrey Pronin &lt;apronin@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Always enter BROKEN screen in non-manual recovery, even in dev mode</title>
<updated>2018-02-21T04:31:52+00:00</updated>
<author>
<name>Julius Werner</name>
<email>jwerner@chromium.org</email>
</author>
<published>2018-02-16T21:19:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=5b26e40508e787baecb5d8920926de0ba37f09ce'/>
<id>5b26e40508e787baecb5d8920926de0ba37f09ce</id>
<content type='text'>
Previously, non-manual recovery behavior would depend on the developer
mode switch: in normal mode it would get stuck at the BROKEN screen, but
in developer mode it would proceed exactly like manual recovery. This
behavior was mostly just confusing to people and it seems that we have
no real use case for it anymore. Remove the developer mode special case
so that non-manual recovery will always go to the BROKEN screen from now
on.

BRANCH=scarlet?
BUG=None
TEST=make runtests, verified manually on Scarlet and Kevin

Change-Id: Iaf33f82d7cb709a5ee309c08d1ad3015859738b3
Signed-off-by: Julius Werner &lt;jwerner@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/924458
Reviewed-by: Randall Spangler &lt;rspangler@chromium.org&gt;
Reviewed-by: Daisuke Nojiri &lt;dnojiri@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously, non-manual recovery behavior would depend on the developer
mode switch: in normal mode it would get stuck at the BROKEN screen, but
in developer mode it would proceed exactly like manual recovery. This
behavior was mostly just confusing to people and it seems that we have
no real use case for it anymore. Remove the developer mode special case
so that non-manual recovery will always go to the BROKEN screen from now
on.

BRANCH=scarlet?
BUG=None
TEST=make runtests, verified manually on Scarlet and Kevin

Change-Id: Iaf33f82d7cb709a5ee309c08d1ad3015859738b3
Signed-off-by: Julius Werner &lt;jwerner@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/924458
Reviewed-by: Randall Spangler &lt;rspangler@chromium.org&gt;
Reviewed-by: Daisuke Nojiri &lt;dnojiri@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Clear OPROM_NEEDED on EC update before reboot</title>
<updated>2018-02-16T15:46:17+00:00</updated>
<author>
<name>Daisuke Nojiri</name>
<email>dnojiri@chromium.org</email>
</author>
<published>2018-01-24T22:30:10+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=cc441a0ea8b0e1a7a1802070dc6ca606d80c9148'/>
<id>cc441a0ea8b0e1a7a1802070dc6ca606d80c9148</id>
<content type='text'>
This patch makes ec_sync_all clear OPROM_NEEDED flag when
ec_sync_phase2 updates EC and requests reboot.

Without this change OPROM_NEEDED flag will stay forever because after
reboot need_wait_screen won't be set (thus line 90 won't be reached).

BUG=b:72387533
BRANCH=none
TEST=Verify firmware screens are displayed on type-c monitor:
developer warning screen, critical update screen, recovery screen.

Change-Id: I9cc072efbf937ac438b55f3812f677612f79eaf9
Signed-off-by: Daisuke Nojiri &lt;dnojiri@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/916635
Reviewed-by: Julius Werner &lt;jwerner@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch makes ec_sync_all clear OPROM_NEEDED flag when
ec_sync_phase2 updates EC and requests reboot.

Without this change OPROM_NEEDED flag will stay forever because after
reboot need_wait_screen won't be set (thus line 90 won't be reached).

BUG=b:72387533
BRANCH=none
TEST=Verify firmware screens are displayed on type-c monitor:
developer warning screen, critical update screen, recovery screen.

Change-Id: I9cc072efbf937ac438b55f3812f677612f79eaf9
Signed-off-by: Daisuke Nojiri &lt;dnojiri@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/916635
Reviewed-by: Julius Werner &lt;jwerner@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>detachables: Allow 'Tab' to display debug info on all screens</title>
<updated>2018-02-08T09:24:36+00:00</updated>
<author>
<name>Julius Werner</name>
<email>jwerner@chromium.org</email>
</author>
<published>2018-02-07T23:36:41+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=dff3a8544b09d54cce487b215a8713d4594c834b'/>
<id>dff3a8544b09d54cce487b215a8713d4594c834b</id>
<content type='text'>
Since we're continuing to support the boot shortcuts Ctrl+D, Ctrl+U and
Ctrl+L, it makes sense to also continue to support the debug info
shortcut Tab, just in case somebody may want to use it from an external
keyboard. This does not affect the existing method to display debug info
through the appropriate menu option in any way.

BRANCH=None
BUG=b:73080278
TEST=make runtests, booted Scarlet and pressed Tab on UART.

Change-Id: Ia08404e0ffd1f8cac3d85f3b2fc4ce17a21d743d
Signed-off-by: Julius Werner &lt;jwerner@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/907759
Reviewed-by: Furquan Shaikh &lt;furquan@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since we're continuing to support the boot shortcuts Ctrl+D, Ctrl+U and
Ctrl+L, it makes sense to also continue to support the debug info
shortcut Tab, just in case somebody may want to use it from an external
keyboard. This does not affect the existing method to display debug info
through the appropriate menu option in any way.

BRANCH=None
BUG=b:73080278
TEST=make runtests, booted Scarlet and pressed Tab on UART.

Change-Id: Ia08404e0ffd1f8cac3d85f3b2fc4ce17a21d743d
Signed-off-by: Julius Werner &lt;jwerner@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/907759
Reviewed-by: Furquan Shaikh &lt;furquan@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>image_signing: delete old crosh_workarounds logic</title>
<updated>2018-02-08T09:24:17+00:00</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@chromium.org</email>
</author>
<published>2018-02-07T17:05:45+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=01b50c46bcff65524adacdcce91732e682f906e2'/>
<id>01b50c46bcff65524adacdcce91732e682f906e2</id>
<content type='text'>
We deleted crosh workarounds logic years ago (e.g. CL:178932),
so drop references here too.

BUG=None
TEST=precq passes
BRANCH=None

Change-Id: I2b195a7ca863101be35a4bfde29d7950a96c1edd
Reviewed-on: https://chromium-review.googlesource.com/907069
Commit-Ready: ChromeOS CL Exonerator Bot &lt;chromiumos-cl-exonerator@appspot.gserviceaccount.com&gt;
Tested-by: Mike Frysinger &lt;vapier@chromium.org&gt;
Reviewed-by: David Riley &lt;davidriley@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We deleted crosh workarounds logic years ago (e.g. CL:178932),
so drop references here too.

BUG=None
TEST=precq passes
BRANCH=None

Change-Id: I2b195a7ca863101be35a4bfde29d7950a96c1edd
Reviewed-on: https://chromium-review.googlesource.com/907069
Commit-Ready: ChromeOS CL Exonerator Bot &lt;chromiumos-cl-exonerator@appspot.gserviceaccount.com&gt;
Tested-by: Mike Frysinger &lt;vapier@chromium.org&gt;
Reviewed-by: David Riley &lt;davidriley@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Request cold reboot when switching to dev mode</title>
<updated>2018-02-08T09:23:49+00:00</updated>
<author>
<name>Daisuke Nojiri</name>
<email>dnojiri@chromium.org</email>
</author>
<published>2018-02-07T23:09:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=c7293182ed0dd01004e2ed0e1e2a02eab0c52f93'/>
<id>c7293182ed0dd01004e2ed0e1e2a02eab0c52f93</id>
<content type='text'>
When switching from normal to dev mode, the EC is in RO. AP requests
warm reboot, whic causes EC to jump to RW. After sysjump, RW tries to
renegotiate PD but it's too late for type-c monitor to function
because VBIOS has already run.

This patch makes AP request EC reboot when switching to dev mode.

BUG=b:73083750
BRANCH=none
TEST=Dingdong connected to Teemo. Verify norm-to-dev screen is
displayed. make -j runtests.

Change-Id: I763cd6968406f7b904604b2588a9db6d567cbd4e
Signed-off-by: Daisuke Nojiri &lt;dnojiri@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/907734
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When switching from normal to dev mode, the EC is in RO. AP requests
warm reboot, whic causes EC to jump to RW. After sysjump, RW tries to
renegotiate PD but it's too late for type-c monitor to function
because VBIOS has already run.

This patch makes AP request EC reboot when switching to dev mode.

BUG=b:73083750
BRANCH=none
TEST=Dingdong connected to Teemo. Verify norm-to-dev screen is
displayed. make -j runtests.

Change-Id: I763cd6968406f7b904604b2588a9db6d567cbd4e
Signed-off-by: Daisuke Nojiri &lt;dnojiri@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/907734
</pre>
</div>
</content>
</entry>
<entry>
<title>vboot_api: Remove unused VB_SCREEN constants</title>
<updated>2018-02-07T23:04:20+00:00</updated>
<author>
<name>Julius Werner</name>
<email>jwerner@chromium.org</email>
</author>
<published>2018-02-01T01:23:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=b2846490c3d027a434d34bffd490bf07b0d38eec'/>
<id>b2846490c3d027a434d34bffd490bf07b0d38eec</id>
<content type='text'>
Some of the defined screens have never been used or we've stopped using
them a while ago. Remove the respective constants to make it clearer
that callers of the library are not expected to handle them.

CQ-DEPEND=CL:903362
BRANCH=None
BUG=None
TEST=make runtests

Change-Id: I82308fc76dc10b2c8b408af7a15a819120043632
Signed-off-by: Julius Werner &lt;jwerner@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/902899
Commit-Ready: ChromeOS CL Exonerator Bot &lt;chromiumos-cl-exonerator@appspot.gserviceaccount.com&gt;
Reviewed-by: Randall Spangler &lt;rspangler@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some of the defined screens have never been used or we've stopped using
them a while ago. Remove the respective constants to make it clearer
that callers of the library are not expected to handle them.

CQ-DEPEND=CL:903362
BRANCH=None
BUG=None
TEST=make runtests

Change-Id: I82308fc76dc10b2c8b408af7a15a819120043632
Signed-off-by: Julius Werner &lt;jwerner@chromium.org&gt;
Reviewed-on: https://chromium-review.googlesource.com/902899
Commit-Ready: ChromeOS CL Exonerator Bot &lt;chromiumos-cl-exonerator@appspot.gserviceaccount.com&gt;
Reviewed-by: Randall Spangler &lt;rspangler@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>image_signing: Support AOSP dev signing keys</title>
<updated>2018-02-07T05:32:45+00:00</updated>
<author>
<name>Nicolas Norvez</name>
<email>norvez@chromium.org</email>
</author>
<published>2018-02-05T19:50:52+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=2fbb522949cd5c7a4f203a90da1bcdbf6057b5ae'/>
<id>2fbb522949cd5c7a4f203a90da1bcdbf6057b5ae</id>
<content type='text'>
Following ag/3536780, aosp_cheets targets have their APKs signed with
keys https://android.googlesource.com/platform/build/+/master/target/product/security/
The image signing script now:
- detects if it's an aosp_cheets or cheets build
- checks the correct signing keys have been used in either case
- logs more information about the Android image

BUG=b:72947583
TEST=manually test sign_framework_apks against AOSP and cheets builds
TEST=aosp_cheets builds prior to ag/3536780 are now failing (expected)
TEST=aosp_cheets builds posterior to ag/3536780 are passing
TEST=cheets builds (before and after) are passing

TEST=check that commenting out ro.product.name in build.prop triggers an
error
TEST=check that an invalid value in ro.product.name triggers an error
BRANCH=None

Change-Id: I72abea5182fbfe76820e3f48831be04f39cb334e
Reviewed-on: https://chromium-review.googlesource.com/904726
Commit-Ready: Nicolas Norvez &lt;norvez@chromium.org&gt;
Tested-by: Nicolas Norvez &lt;norvez@chromium.org&gt;
Reviewed-by: Mike Frysinger &lt;vapier@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Following ag/3536780, aosp_cheets targets have their APKs signed with
keys https://android.googlesource.com/platform/build/+/master/target/product/security/
The image signing script now:
- detects if it's an aosp_cheets or cheets build
- checks the correct signing keys have been used in either case
- logs more information about the Android image

BUG=b:72947583
TEST=manually test sign_framework_apks against AOSP and cheets builds
TEST=aosp_cheets builds prior to ag/3536780 are now failing (expected)
TEST=aosp_cheets builds posterior to ag/3536780 are passing
TEST=cheets builds (before and after) are passing

TEST=check that commenting out ro.product.name in build.prop triggers an
error
TEST=check that an invalid value in ro.product.name triggers an error
BRANCH=None

Change-Id: I72abea5182fbfe76820e3f48831be04f39cb334e
Reviewed-on: https://chromium-review.googlesource.com/904726
Commit-Ready: Nicolas Norvez &lt;norvez@chromium.org&gt;
Tested-by: Nicolas Norvez &lt;norvez@chromium.org&gt;
Reviewed-by: Mike Frysinger &lt;vapier@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>cgpt: add support for managing GPT platform required partition bit</title>
<updated>2018-02-07T02:18:35+00:00</updated>
<author>
<name>Ben Chan</name>
<email>benchan@chromium.org</email>
</author>
<published>2018-01-31T19:39:14+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=a4a8c02ad5988bd4b6fd85f6e09e9e0e79d18feb'/>
<id>a4a8c02ad5988bd4b6fd85f6e09e9e0e79d18feb</id>
<content type='text'>
Bit 0 in the GPT partition attributes is defined to indicate whether a
partition is required by the platform. This CL adds the support for
managing this bit to cgpt.

BUG=b:70807006
BRANCH=None
TEST=Run unit tests.

Change-Id: Iaf87c828438b3df6730de502ae420fcf4c61277b
Reviewed-on: https://chromium-review.googlesource.com/902196
Commit-Ready: Ben Chan &lt;benchan@chromium.org&gt;
Tested-by: Ben Chan &lt;benchan@chromium.org&gt;
Reviewed-by: Mike Frysinger &lt;vapier@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Bit 0 in the GPT partition attributes is defined to indicate whether a
partition is required by the platform. This CL adds the support for
managing this bit to cgpt.

BUG=b:70807006
BRANCH=None
TEST=Run unit tests.

Change-Id: Iaf87c828438b3df6730de502ae420fcf4c61277b
Reviewed-on: https://chromium-review.googlesource.com/902196
Commit-Ready: Ben Chan &lt;benchan@chromium.org&gt;
Tested-by: Ben Chan &lt;benchan@chromium.org&gt;
Reviewed-by: Mike Frysinger &lt;vapier@chromium.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>make_dev_firmware.sh supports switching EC RO key</title>
<updated>2018-02-02T21:19:42+00:00</updated>
<author>
<name>Wai-Hong Tam</name>
<email>waihong@google.com</email>
</author>
<published>2018-01-26T01:45:06+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/coreboot/vboot.git/commit/?id=3585eb3d21da676db3d87e9e0490a0df92d597d2'/>
<id>3585eb3d21da676db3d87e9e0490a0df92d597d2</id>
<content type='text'>
For the EC supporting EFS boot, the RO section contains a
public key, and the RW is signed. For running FAFT, should
replace the RO key to a known one (the dev key under
vboot_reference), such that FAFT tests can resign the RW
using a known private key.

For BIOS image, we use make_dev_firmware.sh to do a similar
job to replace the key in BIOS. This CL makes the
make_dev_firmware script support changing EC key.

BUG=b:71769443
BRANCH=none
TEST=Modify files
$ # Check the original BIOS and EC images
$ futility show ec.bin
$ futility show bios.bin
$ ./make_dev_firmware.sh --change_ec -f bios.bin -t new_bios.bin \
  -e ec.bin -o new_ec.bin --backup_dir backup
$ # Check the new images, using new keys and verification succeeded
$ futility show new_ec.bin
$ futility show new_bios.bin

TEST=Modify live firmware
$ ./make_dev_firmware.sh --change_ec
And then run firmware_ECUpdateId with a Type-C charger.

TEST=Run sign_official_build.sh
$ sign_official_build.sh recovery recovery_image.bin \
~/trunk/src/platform/vboot_reference/tests/devkeys /tmp/out.bin

TEST=make runalltests

Change-Id: Id51e2c411a4e6d016e619cec91453ce918b7fff7
Reviewed-on: https://chromium-review.googlesource.com/889406
Commit-Ready: Wai-Hong Tam &lt;waihong@google.com&gt;
Tested-by: Wai-Hong Tam &lt;waihong@google.com&gt;
Reviewed-by: Daisuke Nojiri &lt;dnojiri@chromium.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
For the EC supporting EFS boot, the RO section contains a
public key, and the RW is signed. For running FAFT, should
replace the RO key to a known one (the dev key under
vboot_reference), such that FAFT tests can resign the RW
using a known private key.

For BIOS image, we use make_dev_firmware.sh to do a similar
job to replace the key in BIOS. This CL makes the
make_dev_firmware script support changing EC key.

BUG=b:71769443
BRANCH=none
TEST=Modify files
$ # Check the original BIOS and EC images
$ futility show ec.bin
$ futility show bios.bin
$ ./make_dev_firmware.sh --change_ec -f bios.bin -t new_bios.bin \
  -e ec.bin -o new_ec.bin --backup_dir backup
$ # Check the new images, using new keys and verification succeeded
$ futility show new_ec.bin
$ futility show new_bios.bin

TEST=Modify live firmware
$ ./make_dev_firmware.sh --change_ec
And then run firmware_ECUpdateId with a Type-C charger.

TEST=Run sign_official_build.sh
$ sign_official_build.sh recovery recovery_image.bin \
~/trunk/src/platform/vboot_reference/tests/devkeys /tmp/out.bin

TEST=make runalltests

Change-Id: Id51e2c411a4e6d016e619cec91453ce918b7fff7
Reviewed-on: https://chromium-review.googlesource.com/889406
Commit-Ready: Wai-Hong Tam &lt;waihong@google.com&gt;
Tested-by: Wai-Hong Tam &lt;waihong@google.com&gt;
Reviewed-by: Daisuke Nojiri &lt;dnojiri@chromium.org&gt;
</pre>
</div>
</content>
</entry>
</feed>
