| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the interest of making long-term branch maintenance incur as little
technical debt on us as possible, we should not maintain any files on
the branch we are not actually using.
This has the added effect of making it extremely clear when merging CLs
from the main branch when changes have the possibility to affect us.
The follow-on CL adds a convenience script to actually pull updates from
the main branch and generate a CL for the update.
BUG=b:204206272
BRANCH=ish
TEST=make BOARD=arcada_ish && make BOARD=drallion_ish
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I17e4694c38219b5a0823e0a3e55a28d1348f4b18
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3262038
Reviewed-by: Jett Rink <jettrink@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our GitLab builder uses different toolchains than the supported ones
we use for development. At present, this means that the GitLab CI
needs to call -t for each build with the desired toolchain, preventing
us from using the more general commands "zmake coverage" or "zmake
testall".
Extend the idea of toolchain in our config files to be "supported
toolchains" instead (i.e., multiple toolchains can be supported
instead of one. We do this by refactoring our toolchain support code
to consist of two related methods:
- "probe" returns True if the toolchain is detected on the system, or
False otherwise
- "get_toolchain_config" returns the BuildConfig associated with the
toolchain for the system, mirroring the functionality previously
implemented in lambda functions.
Also dropped support for arm-none-eabi, as I believe this was only
used early on during scarlet development, and am not aware of any
current users.
BUG=b:178731498
BRANCH=none
TEST=./run_tests.sh
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I9b2ad508ae6703f0c3b56518fc32606c0ff1777c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3134668
Commit-Queue: Jeremy Bettis <jbettis@chromium.org>
Reviewed-by: Jeremy Bettis <jbettis@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Switch the host tests and posix-ec build to Zephyr v2.6.
Note: need to disable one assert in the hooks test until b/195971523
is resolved.
BUG=b:195571108,b:195971523
BRANCH=none
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I01b386b2f54cf5b752bede707ff9fbda0faad80a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3072414
Reviewed-by: Fabio Baltieri <fabiobaltieri@google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Drop support for Zephyr OS v2.4 on all boards, since the v2.5 uprev is
successful.
If someone still needs to manually compile for v2.4 for testing, one
can do so by passing --zephyr-base=$PATH_TO_ZEPHYR_24 and
--ignore-unsupported-zephyr-version to zmake.
BUG=b:180409973
BRANCH=none
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I0b3922c0b7f47811b26bad4e7f99125cabdaed91
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2715345
Commit-Queue: Simon Glass <sjg@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Zephyr v2.5 will build for all projects now, mark it as supported for
all projects and it will be enabled by default.
We can delete v2.4 from this list once v2.5 gets a bit more battle
testing.
If you need to build for v2.4 in the interim, you should pass the
--zephyr-base flag to zmake, like so:
$ zmake --zephyr-base ~/trunk/src/third_party/zephyr/main/v2.4 ...
BUG=b:180409973
BRANCH=none
TEST=zmake testall
TEST=flash on delbin, test UART console functioning
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I9cb7902455b2c6f231bea5c0b08b0e18bca0ddd8
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2705192
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Switch all zmake.yaml files to chroot-supported toolchains (chroot
llvm for these files) so that we can run "zmake testall" without
grabbing the Zephyr SDK.
BUG=b:175248887
BRANCH=none
TEST=zmake testall
Cq-Depend: chromium:2590992
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I6c57ca734c18bdcc159b185709a3dd22a52a8b52
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2591628
Commit-Queue: Simon Glass <sjg@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change will make the firmware builder auto-detect new tests.
BRANCH=none
BUG=none
TEST=Ran zephyr's firmware_builder.py
Cq-Depend: chromium:2551964
Signed-off-by: Yuval Peress <peress@chromium.org>
Change-Id: I70ba1b32b67e2cb4e3676d228b299294028597a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2552848
Reviewed-by: Jett Rink <jettrink@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
|
|
|
Add the zmake config file for test that don't have one
BRANCH=none
BUG=none
TEST=zmake builds both tests
zmake configure -b /tmp/test
~/chromiumos/src/platform/ec/zephyr/test/tasks
zmake build /tmp/test
Signed-off-by: Jett Rink <jettrink@chromium.org>
Change-Id: Ibd9fd114e7fff008bb07cb616529d82cdb774a0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2521064
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
|
