tree 45697c4fe37b863fc78e5503e9645f33f21cd3ea
parent 44648d011f17c2d9440d889d25085ed5cd75bfe7
author Vadim Bendebury <vbendeb@chromium.org> 1354921354 -0800
committer Gerrit <chrome-bot@google.com> 1355796558 -0800

Add an autotest reporgramming DUT firmware through servo.

This autotest allows to program firmware on an 'unresponsive' Chrome
OS DUT, using the servo device. As submitted it supports only Link,
more platforms will be integrated shortly.

A new module (server/cros/programmer.py) is being added to provide the
firmware programmer interface and implementation and
server/cros/servo.py is being extended to export the new module as a
servo object service and adds an interface to execute an arbitrary
shell command on the host controlling the servo device.

Chrome OS DUTs use two distinct firmware types, EC and and AP (a.k.a
bootprom) firmware. Bad firmware can easily brick a DUT, this is why
it is necessary to be able to program firmware on 'dead' DUTs. Servo
devices provide the means of doing it, the new module requires the DUT
to be connected to a servo device. Servo device state is preserved
across the programming process.

The new module is still incomplete, it fully supports Link devices but
not Lucas (ARM platforms) yet.

BUG=chrome-os-partner:15610
TEST=try reporgramming a Link connected to both local and remote servo:

  . observe current FW versions on the DUT:

   $  echo $(ssh 192.168.1.4 ectool version)
   RO version: link_v1.1.618-52440ef RW version: link_v1.1.618-52440ef Firmware copy: RO Build info: link_v1.1.618-52440ef 2012-12-05 10:42:46 @build51-m2
   $ echo  $(ssh 192.168.1.4  crossystem fwid)
   Google_Link.3354.0.0

  . local servo
   run_remote_tests.sh --board=link --servo --remote=192.168.1.4 --allow_offline_remote fwupdate --args \
    'fwurl=gs://chromeos-releases/canary-channel/link/3419.0.0/ChromeOS-firmware-R25-3419.0.0-link.tar.bz2 \
     board=link'

  . observe the test succeed, check versions
   $ echo $(ssh 192.168.1.4 ectool version)
   RO version: link_v1.1.626-e927d15 RW version: link_v1.1.626-e927d15 Firmware copy: RO Build info: link_v1.1.626-e927d15 2012-12-17 10:42:49 @build51-m2
   $ echo  $(ssh 192.168.1.4  crossystem fwid)
   Google_Link.3419.0.0

  . connect servo to a Beaglebone (at 192.168.1.103), reboot the board and verify that servod is running

  . run with remote servo
   run_remote_tests.sh --board=link --remote=192.168.1.4 --allow_offline_remote fwupdate --args \
    'fwurl=gs://chromeos-releases/canary-channel/link/3354.0.0/ChromeOS-firmware-R25-3354.0.0-link.tar.bz2 \
     board=link \
     servo_host=192.168.1.103 \
     servo_port=9999'

  . observe the test succeed, check versions
    $ echo $(ssh 192.168.1.4 ectool version)
    RO version: link_v1.1.618-52440ef RW version: link_v1.1.618-52440ef Firmware copy: RO Build info: link_v1.1.618-52440ef 2012-12-05 10:42:46 @build51-m2
    $ echo  $(ssh 192.168.1.4  crossystem fwid)
    Google_Link.3354.0.0

    BUG=chrome-os-partner:15610
    TEST=manual
      The new methods were used in an upcoming autotest module. It allowed
      to reprogram EC and AP firmware on a Link controlled by both local
      and remote servos.

Change-Id: I7ce48ff4cc5135f9ac10c3b4bc94bd9826e2f103
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/39408