New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 713979 link

Starred by 1 user
Status: Fixed
Owner:
marcochen@chromium.org
Closed: Jun 2017
Cc:
█ charliemooney@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Streamline touch FW uploading process

Project Member Reported by marcochen@chromium.org, Apr 21 2017 
In order to deploy the new touch firmware into the DUT, the corresponding files
would need to be added or modified. In addition, a tarball should be created to
contain all related firmwares and be uploaded into BCS.

Scripts here help users to achieve these works by automatically processing
corresponding files thus users are more easy to complete this change.
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 28 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/touch_updater/+/1460fef6c50eda2b09825311dbad6f169feef3b3

commit 1460fef6c50eda2b09825311dbad6f169feef3b3
Author: Marco Chen <marcochen@chromium.org>
Date: Fri Apr 28 05:54:51 2017

Script to update new touch firmware automatically.

  1. Uprev existed touch firmware -
    a. Change fw version in ebuild.
    b. Bump ebuild revision.
    c. Download tarball from BCS.
    d. Add new firmware blob into tarball and remove old one.
    e. Upload new tarball to BCS. (ACL issue now, so would need users to upload by themselves)
    f. Call "ebuild manifest" to update Manifest.
    g. Verify CL on the remote DUT via "cros deploy" and check logs in the remote DUT.
    h. Generate CLs based on modified content above. (users need to
do it by themselves)

  2. Add new firmware
    a. Add new settings in ebuild.
    b. If it is neccessary, add INPUT_DEVICES=xxx into make.conf.
    c. Others are the same with "uprev firmware".

  3. Create initial chromeos-touch-firmware-xxx
    a. Add initial ebuild.
    b. Add initial symbolic link of ebuild.
    c. Add dependency into chromeos-bsp-XXX-private's ebuild for chromeos-touch-firmware-xxx.
    d. Others are the same with "add new firmware".

BUG= chromium:713979 
TEST=1. Execute "host_scripts/test_update_new_firmware_version.sh -b reef"
     2. check generated files

Change-Id: I4e83a3a63defb88c4a8c2ca87cfc2855c04da740
Reviewed-on: https://chromium-review.googlesource.com/459361
Commit-Ready: Marco Chen <marcochen@chromium.org>
Tested-by: Marco Chen <marcochen@chromium.org>
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>

[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/template.ebuild.txt
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/testdata/200.0_1.0.bin
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/testdata/wacom_200.hex
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/testdata/33.3_1.0.bin
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/test_update_new_firmware_version.sh
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/testdata/154.0_4.0.bin
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/update_new_firmware_version.sh
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/testdata/154.0_3.0.bin
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/README
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/testdata/wacom_100.hex
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/testdata/100.4_1.0.fw
[add] https://crrev.com/1460fef6c50eda2b09825311dbad6f169feef3b3/host_scripts/testdata/100.4_2.0.fw

Comment 2 by marcochen@chromium.org, Jun 28 2017

Status: Fixed (was: Untriaged)
►

Sign in to add a comment