2ae311c901
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> |
||
---|---|---|
.. | ||
common | ||
gpio | ||
hook | ||
i2c | ||
interrupt | ||
meta | ||
mutex | ||
task | ||
timer | ||
README | ||
build.mk | ||
cts.py | ||
cts.tasklist |
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.