GitLab

Signed-off-by: Laura Nao <laura.nao@collabora.com>

If cros_sdk_branch variable is not defined in the .env file,
docker-compose substitutes it with an empty string and the
default value set in Dockerfile is never used.
Set the default value for the cros_sdk_branch argument in
the compose file instead.
Signed-off-by: Laura Nao <laura.nao@collabora.com>

The FW build process for some devices require invoking the
setup_project.sh script with device name and device profile as
arguments. Add support for additional variable in .env file to specify
the profile to be used when project setup is required.
Signed-off-by: Laura Nao <laura.nao@collabora.com>

Add support for additional variable in .env file that specifies the
groups of manifest projects to be initialized and synced with repo.
Signed-off-by: Laura Nao <laura.nao@collabora.com>

Signed-off-by: Laura Nao <laura.nao@collabora.com>

Ricardo Cañuelo authored Jul 21, 2021 and Ricardo Cañuelo Navarro committed Jul 26, 2021

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

Install the ssh package in the Dockerfile otherwise repo sync fails.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Signed-off-by: Mylène Josserand <mylene.josserand@collabora.com>

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

Ricardo Cañuelo Navarro authored Mar 22, 2021 and Douglas Targett committed Apr 15, 2021

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

During some of the previous Depthcharge and firmware image updates I
forgot to update the date in the binary file names. Modify them to match
the Depthcharge build date shown in the boot log.

Also, track the rammus firmware binary in cros-build instead of in
cros-build/firmware.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

This adds a custom build script for 'kevin' ('gru') that doesn't rely on
Docker, as the cros_sdk for gru doesn't support the --nouse-image flag.

The script (cros_build/build_kevin.sh) takes care of downloading the
sources and creating a sdk chroot appropriately. Once inside the chroot,
to build the firmware run:

  ./kevin.sh setup
  ./kevin.sh checkout
  ./kevin.sh build

and the resulting firmware binary will be in
cros_build/build_kevin/kevin.bin.

All the downloaded and generated files will be contained in the
cros_build/build_kevin directory.

This also includes the custom firmware binary for
kevin (firmware/kevin.bin), although it wasn't tested.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

This adds a custom build script for 'hana' ('oak') that doesn't rely on
Docker, as the cros_sdk for oak doesn't support the --nouse-image flag.

The script (cros_build/build_hana.sh) takes care of downloading the
sources and creating a sdk chroot appropriately. Once inside the chroot,
to build the firmware run:

  ./hana.sh setup
  ./hana.sh checkout
  ./hana.sh build

and the resulting firmware binary will be in
cros_build/build_hana/hana.bin.

All the downloaded and generated files will be contained in the
cros_build/build_hana directory.

This also includes the custom firmware binary for
hana (firmware/hana.bin), although it wasn't tested.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

This replaces the coral FW image with one that adds a commit by Julius
Werner (45f2be285df6c78b657304198d736e33a9992cc2) to increase the
allowed payload size of Depthcharge. This change was already present in
the firmwares of grunt, rammus and octopus, but missing in
coral. Depthcharge can now download up to 512MB of kernel + ramdisk
data.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

Move some documentation by gtucker from an Etherpad doc to
a new file and link it from README.md. The new document
(building_firmware_images.md) includes the steps to create
a Chromebook firmware image for LAVA from scratch and some examples.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

Normally, a ChromiumOS SDK comes with a set of Servo binaries installed
in /usr/share/servo_updater/firmware, but this is not advertised in the
SDK and there's no way to know which Servo v4 FW version comes with a
specific SDK version.

We found a web archive of Servo v4 firmwares in
https://gsdview.appspot.com/chromeos-localmirror/distfiles/



this is where these firmware binaries come from. These are the ones we
have tested so far.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

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

Update the firmware images for coral, grunt, octopus and rammus to
include a Depthcharge patch that enables support for Ethernet jumbo
frames.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

Update the octopus firmware binary with the rebuilt image based on the
collabora-20201104 Depthcharge revision from the
firmware-octopus-11297.83.B-collabora branch.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Switch the octopus Depthcharge firmware branch to the
firmware-octopus-11297.83.B-collabora which is the definitive one to
use in production.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

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

This includes a new environment file and build script for rammus to
generate the firmware-rammus-11275.B-collabora Depthcharge branch.

It also updates docker-compose.yaml to include a board-specific
setup directory in the environment.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

Add the grunt environment and build script to build the
firmware-grunt-11031.B-collabora Depthcharge branch.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

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

This includes a new coral.env and coral.sh files for building a
LAVA-compliant firmware for coral based on the R64-10068.111.0 dev
release.

The base serial firmware binary is also included.
Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>

Update the instructions about how to use the tools in this repository
and provide an example based on octopus.  This includes setting up a
Docker container and building a firmware image.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

The repository has moved from flash-tools to firmware-tools so update
the README.md accordingly.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Add commands to either enter the CrOS SDK chroot or open a shell in
the container, interactively or with some arbitrary commands.

For example, this makes it possible to call the bootstrap.sh script
and invoke a build script in the chroot to set everything up and build
a firmware image all in one go.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Ignore the "new" firmware images that are produced by the
buildscripts.  Only the firmware images with a full name should be
tracked under source control with Git LFS.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Add octopus.sh script to set up the CrOS SDK chroot for octopus, build
a custom branch of Depthcharge and replace the payload in the Coreboot
firmware image.  The output is stored in a new file in
firmware/octopus-new.bin which can be accessed from the host.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Mount the local firmware directory in src/scripts so it's accessible
from within the chroot.  Build scripts can now place their output
images directly there to make it easy to share them with the host
system.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Add the current octopus firmware image with a symlink as octopus.bin
too use in build scripts:

  image-bobba-R72-11297.144.0-octopus.serial-gtucker.bin
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Ricardo Cañuelo Navarro authored Oct 15, 2020 and Ricardo Cañuelo Navarro committed Oct 20, 2020

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

Move the Dockerfile to the setup directory and change the context
accordingly.  This is to restrict the Docker context to the files that
are really needed, and avoid copying things like the cache and chroot
directories when rebuilding the container.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>

Add the create-chroot.sh script to create the Chromium OS SDK chroot.
Install it in the Docker container and call it in the debotstrap.sh
script to automatically set everything up.
Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>