From cc6624b1395b008d58cb56edd0676d422e2040f4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ricardo=20Ca=C3=B1uelo?= <ricardo.canuelo@collabora.com> Date: Thu, 17 Dec 2020 14:23:05 +0100 Subject: [PATCH] boards/chromebooks: add a requirement checklist for lab deployment MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> --- .../boards/chromebooks/04-bootloader_setup.md | 6 ++--- .../chromebooks/05-requirements_checklist.md | 22 +++++++++++++++++++ 2 files changed, 24 insertions(+), 4 deletions(-) create mode 100644 content/boards/chromebooks/05-requirements_checklist.md diff --git a/content/boards/chromebooks/04-bootloader_setup.md b/content/boards/chromebooks/04-bootloader_setup.md index d651644..fb76d14 100644 --- a/content/boards/chromebooks/04-bootloader_setup.md +++ b/content/boards/chromebooks/04-bootloader_setup.md @@ -21,9 +21,8 @@ Chrome OS firmwares contain some binary blobs that we can't build from scratch, so a way to generate a firmware with a modified version of Depthcharge is to take a release firmware binary from Google and replacing the payload with a custom modified Depthcharge binary built -from the branch above. More info -[here](https://gitlab.collabora.com/chromium/firmware-tools). - +from the branch above. More info in the documentation of the +[firmware-tools repo](https://gitlab.collabora.com/chromium/firmware-tools/-/blob/master/README.md). ## Chromebook bootup in a LAVA setup @@ -34,7 +33,6 @@ Chromebook has a network link to a DHCP and TFTP server, a Linux kernel can be booted like this: ``` -(depthcharge): enet dhcp (depthcharge): tftpboot dhcp bzImage args initrd.cpio.gz ``` diff --git a/content/boards/chromebooks/05-requirements_checklist.md b/content/boards/chromebooks/05-requirements_checklist.md new file mode 100644 index 0000000..b1ced1c --- /dev/null +++ b/content/boards/chromebooks/05-requirements_checklist.md @@ -0,0 +1,22 @@ +--- +title: Requirements for deploying a Chromebook in a LAVA lab +weight: 5 +--- + +Before a Chromebook can be deployed in a LAVA lab it has to meet some +requirements: + + - [CCD](../02-ccd) is open. + - `servod` can setup a Cr50 interface for the Chromebook. + - The following operations can be issued using at least one debugging + interface (`SuzyQ`, `Servo v4`), ideally tested OK with both: + - `dut-control -p <device_port> cold_reset:on` + - `dut-control -p <device_port> cold_reset:off` + - The CPU serial console is usable and stable. + - After powering up the Chromebook, the Depthcharge prompt can be + reached in the serial console. + - The Chromebook is able to send/receive packets through an Ethernet + interface (ideally using the `Servo v4` as a USB-Eth adapter). + - The Chromebook is able to boot a Linux kernel through TFTP (see + [Bootloader setup for LAVA](../04-bootloader_setup) + and the documentation linked there for more info). -- GitLab