From 1bd59910f0f7649a3431a0401bbd549cb8d04df2 Mon Sep 17 00:00:00 2001 From: mparuchuri Date: Wed, 4 May 2022 08:37:00 +0000 Subject: README: Update emerge EC binary path After building the ChromeOS EC repo using emerge, the ec.bin is not found in the current path mentioned in Readme. This commit is updating that path. BUG=none BRANCH=none TEST=Manually check the ec.bin file at current and updated path Signed-off-by: Madhurima Paruchuri Change-Id: If91e290637cfaa5fdb404fc348ca17c4ff5cd413 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3626474 Reviewed-by: Fabio Baltieri Reviewed-by: Boris Mittelberg --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 777c190efd..0a10859b93 100644 --- a/README.md +++ b/README.md @@ -210,6 +210,14 @@ The generated EC binary from emerge is found at: (chroot) $ /build//firmware/ec.bin ``` +or + +``` +(chroot) $ /build//firmware//ec.bin +``` + +The `devicename` is the name of a device (also referred as board or variant) which belongs to a family of baseboard. `boardname` is the baseboard name in this case. Example : `/build/dedede/firmware/madoo/ec.bin` + The ebuild file used by Chromium OS is found [here](https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/main/chromeos-base/chromeos-ec/chromeos-ec-9999.ebuild): @@ -249,6 +257,14 @@ If you build Chrome OS with `build_packages` the firmware image will be at: (chroot) $ /build//firmware/ec.bin ``` +or + +``` +(chroot) $ /build//firmware//ec.bin +``` + +The `devicename` is the name of a device (also referred as board or variant) which belongs to a family of baseboard. `boardname` is the baseboard name in this case. Example : `/build/dedede/firmware/madoo/ec.bin` + Specifying `--image` is optional. If you leave off the `--image` argument, the `flash_ec` script will first look for a locally built `ec.bin` followed by one generated by `emerge`. -- cgit v1.2.1