| 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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove support for v2.5 for all projects which still indicate it's
supported.
BUG=b:195571108
BRANCH=none
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I5c22e382545741181866a4e88cb3d486a392f2f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3086365
Reviewed-by: Fabio Baltieri <fabiobaltieri@google.com>
Reviewed-by: Keith Short <keithshort@chromium.org>
Commit-Queue: Keith Short <keithshort@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add 2.6 to list of supported versions.
Note: need to drop the USE flag from hatch overlay before we can drop
v2.5 support in zmake.yaml.
BUG=b:195571108
BRANCH=none
TEST=flash on kohaku, boot to S0
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: Ia50e62155826f21aee094ccf80cb699a99a18978
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3072415
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "raw" packer used to be a binary packer which simply forwarded
zephyr.bin to the output directory with no modifications.
A history of CLs has repurposed this packer to be specific to binman
RO/RW format, with the RO expected to generate a Nuvoton loader at the
beginning of the image. So it's hardly "raw" anymore.
Rename it to "npcx" so we can bring back the original "raw" packer,
needed by chameleon. (Note this is done in a follow-up CL).
BUG=b:180545676
BRANCH=none
TEST=zmake testall
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I73e13426d7c87db1ccf3514dd321640ebc625068
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2702494
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
coreboot-sdk is working now, this hack can go away.
BUG=b:178363068
BRANCH=none
TEST=compile without -t coreboot-sdk, run on device
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: Ifc5b05557ecf623e709bfd2b464648bd24197e1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2647536
Reviewed-by: Patrick Georgi <pgeorgi@chromium.org>
Commit-Queue: Patrick Georgi <pgeorgi@chromium.org>
Tested-by: Patrick Georgi <pgeorgi@chromium.org>
|
|
|
Kohaku uses the same EC chip as volteer. Adding a second device will
help give us a tiny bit more build diversity too, which is a good
thing probably.
This just adds a minimal build for kohaku with just UART support. No
power sequencing, keyboard, USB-C, charging, etc.
BUG=b:177609422
BRANCH=none
TEST=flash onto kohaku, observe working shell and timers
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I277510081c9e06b516b6c29f790e16dd1dfe8028
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2631361
Reviewed-by: Simon Glass <sjg@chromium.org>
|
