chrome-ec/cts
Daisuke Nojiri 2ae311c901 eCTS: Test task priority
CTS task wakes up A and C then goes to sleep:

  CTS -> A, C -> A -> B -> C

Since C has a higher priority, C should run first. This should result
in C running one more time than A (or B).

BUG=chromium:663873
BRANCH=none
TEST=cts.py -m task

Change-Id: I89c733ba3aab09b293edf8583d6ed73791531e59
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/409535
Reviewed-by: Randall Spangler <rspangler@chromium.org>
2016-11-10 21:28:33 -08:00
..
common cts: Fix back-to-back build 2016-10-14 16:05:49 -07:00
gpio cts: Added corruption detection 2016-08-09 12:43:19 -07:00
hook cts: Add hook test 2016-07-15 21:39:29 -07:00
i2c cts: Add I2C tests for read8/16/32 and write8/16/32 2016-10-05 20:58:20 -07:00
interrupt eCTS: Add nested interrupt test (High->Low) 2016-11-09 23:26:31 -08:00
meta cts: Added meta tests (testing cts suite itself) 2016-08-10 15:30:26 -07:00
mutex cts: Add mutext test 2016-07-15 21:39:27 -07:00
task eCTS: Test task priority 2016-11-10 21:28:33 -08:00
timer cts: Add timer test 2016-07-29 15:02:44 -07:00
README cts: First patch flashes blank tests 2016-07-09 01:41:01 -07:00
build.mk cts: Add I2C tests for read8/16/32 and write8/16/32 2016-10-05 20:58:20 -07:00
cts.py eCTS: Add nested interrupt test (High->Low) 2016-11-09 23:26:31 -08:00
cts.tasklist Add cts.tasklist 2016-07-11 21:27:46 -07:00

README

The first time you use this with a particular th,
connect only th and run ./cts/cts.py --th from
the ec directory.

Then connect both boards and you can run
./cts/cts to flash both boards.