boards/chromebooks: add a requirement checklist for lab deployment

Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

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
 ```
 

content/boards/chromebooks/05-requirements_checklist.md

+---
+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).