tree 8cb57488f0876353c343e2ba37949a21cb5cafb5
parent 329564b254c0a5f4a62528f0b3c49a50b9e4911f
author Chun-Ta Lin <itspeter@google.com> 1593828866 +0800
committer Chun-ta Lin <itspeter@chromium.org> 1596945009 +0000

minidiag: add entry

The entry `Launch diagnostics` in recovery screen will set
VB2_NV_DIAG_REQUEST and reboot.

BRANCH=none
BUG=b:155848434
TEST=( export CC=x86_64-pc-linux-gnu-clang DEBUG=1 DIAGNOSTIC_UI=0
    MINIMAL=1 TPM2_MODE= MOCK_TPM=; make clean &&
    make -j32 test_setup && make runtests; echo $? )
TEST=( export CC=x86_64-pc-linux-gnu-clang DEBUG=1 DIAGNOSTIC_UI=1
    MINIMAL=1 TPM2_MODE= MOCK_TPM=; make clean &&
    make -j32 test_setup && make runtests; echo $? )
TEST=LOCALES="en" USE="menu_ui minidiag" emerge-nami chromeos-bmpblk
     vboot_reference depthcharge chromeos-bootimage
TEST=Unset by
       &= ~VB2_SECDATA_KERNEL_FLAG_DIAGNOSTIC_UI_DISABLED manually;
     trigger recovery mode on device;
     visually confirmed `Launch diagnostics` is shown;
     select, reboot and confirm behavior from serial output:
       "Unset diagnostic request (undo display init)".

Cq-Depend: chromium:2282643, chromium:2282664, chromium:2289814
Change-Id: I34af282edee66c5b9943e2d11fb514bac9ccddd8
Signed-off-by: Chun-Ta Lin <itspeter@google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/2282867
Tested-by: Chun-ta Lin <itspeter@chromium.org>
Reviewed-by: Joel Kitching <kitching@chromium.org>