eCTS: Enable Tests to Run in Cros Environment |
||||||
Issue descriptionCurrently, ects doesn't run inside cros chroot environment because the openocd in the chroot doesn't have stm32l4discovery.cfg. Maybe there are more things to be fixed (e.g. tty ports, lsusb, udevadm).
,
Apr 4 2017
,
Apr 4 2017
,
Jun 20 2017
,
Jun 22 2017
eCTS tests now can run inside chroot.
,
Jun 22 2017
,
Jun 23 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/ec/+/577e599f57825f184cb828e08d9b6cc1d3959a71 commit 577e599f57825f184cb828e08d9b6cc1d3959a71 Author: Daisuke Nojiri <dnojiri@chromium.org> Date: Fri Jun 23 07:51:19 2017 eCTS: Switch execution environment to chroot Openocd is upgraded to 0.10.0, which supports stm32l476. So, now we can run eCTS inside chroot. This allows new developers to spend no time on setting up software as all necessary tools (e.g. specific version of make, openocd, lsusb, ARM toolchains) come with cros_sdk. BUG= chromium:653949 BRANCH=none TEST=cts/cts.py -m meta Change-Id: Iba7ba94e95ceadcedcb53b76e47054ba1b2b47dd Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/542017 Reviewed-by: Randall Spangler <rspangler@chromium.org> [modify] https://crrev.com/577e599f57825f184cb828e08d9b6cc1d3959a71/cts/common/board.py
,
Jan 22 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by gkihumba@google.com
, Mar 31 2017