diff options
| -rw-r--r-- | README.md | 16 |
1 files changed, 16 insertions, 0 deletions
@@ -210,6 +210,14 @@ The generated EC binary from emerge is found at: (chroot) $ /build/<boardname>/firmware/ec.bin ``` +or + +``` +(chroot) $ /build/<boardname>/firmware/<devicename>/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/<boardname>/firmware/ec.bin ``` +or + +``` +(chroot) $ /build/<boardname>/firmware/<devicename>/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`. |