Add a couple flags to west update to do shallow fetch for both the main
repo and modules, and don't fetch any tags. Should speed things up a bit
by only fetching the target version code for all modules.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Uses Zephyr's new version infrastruction system for configuring the
version of the application and displaying it.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Twister is more useful in a CI context because we can easily test
multiple combinations of the firmware using a single command.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
RTT is something proprietary, not all boards/programmers have. Let's
make the application simpler.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
These actions are triggering warnings about usage of deprecated features
(e.g. NodeJS 12). Use latest version of the actions.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
This repo also demonstrates Zephyr modules, since it's a module itself.
Add a link to the list of features.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Schedule a daily build, so that we can quickly spot regressions in the
application due to changes in Zephyr.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Zephyr now requires `int main(void)`. Main must return 0, all other
values are reserved.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
This commit updates the example-application to point back to the Zephyr
main branch after the Zephyr v3.3.0 release.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
This makes it easier to rename this repository and use it under its
new name. For example, with this patch, if you push the repository to
GitHub user 'foo' as repository 'bar', you can do:
west init -m https://github.com/foo/bar my-workspace
And you will get:
- my-workspace/.west/config says manifest.path is 'bar'
- my-workspace/bar exists as a git repository
By contrast, with the current 'self: path:' setting, you will instead
get:
- my-workspace/.west/config says manifest.path is
'example-application'
- my-workspace/example-application exists as a git
repository
Let's let people name this repository whatever they want, and get the
expected results, instead of forcing the name example-application
Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
Test was including Kernel for nothing, and missed limits.h
(likely included by Kernel)
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
This is not necessary since it's running in the zephyr docker image,
that already contains them.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Enhance the example-application repository with a configurable,
trivial library example and associated test cases.
.
This implementation appears to make no assumptions.
.
This implementation was verified by running the following commands
in an example-application workspace and verifying all tests passed.
1. `west build -b native_posix -p always example-application/tests/lib/custom_lib/`
2. `./build/zephyr/zephyr.exe`
3. `west build -b native_posix -p always example-application/tests/lib/custom_lib/ -- -DCONFIG_CUSTOM_LIB_GET_VALUE_DEFAULT=6`
4. `./build/zephyr/zephyr.exe`
5. `zephyr/scripts/twister -T example-application/tests/ \
-p qemu_cortex_m0`
6. `cd zephyr/doc && make clean && make` built cleanly.
.
Note that `twister` does not follow the `zephyr/module.yml:tests`
setting to discover tests in modules, so the testcase-root must be
explicitly provided.
Fixes#35177
Signed-off-by: Gregory Shue <gregory.shue@legrand.us>
Create lib subsystem with empty Kconfig menu, subsystem build file.
Updated top-level build and documentation to include subsystem.
This was created to provide an example of how the `lib/` directory
can be connected to the Zephyr build system through `module.yml`,
and so that CI can verify that the extension settings used here
work with these sub-trees.
.
The approach follows the pattern of paralleling the Zephyr tree.
An empty subsystem was implemented rather than a non-empty one
in order to isolate the core changes from any specific library.
This provides a clean reference for users.
.
It was assumed that some users will want to strip out the `lib/`
subsystem separate from existing subsystems, and vice versa.
.
This was verified by:
- visually verifying a clean build of:
`west build -b custom_plank -p always example-application/app/`
- visually verifying the subsystem appeared in the correct
location in a clean build of:
`west build -b custom_plank -p always example-application/app/`
Signed-off-by: Gregory Shue <gregory.shue@legrand.us>
Add a working example for how to implement a west command within the
user's manifest repository. There is documentation for this, but we
should have some working code in here just to make life easier for
people.
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
With the recent changes in how Kconfig options are enabled using DT
helpers, using select leads to a better/more scalable pattern. Each
driver Kconfig option is expected to select its dependencies now.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
The option is no longer needed, zephyr,examplesensor driver will
automatically be selected based on DT (and because we enable all of its
dependencies, including CONFIG_SENSOR).
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Make zephyr,examplesensor driver option dependent on it being defined in
Kconfig and set its default based on DT status as well.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Link to the relevant sections in the Zephyr documentation, including
application development and west topologies.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
-s/--source is a legacy option. There's a proposal to actually use it
for something else in Zephyr now:
https://github.com/zephyrproject-rtos/zephyr/pull/40669
Let's update README.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Zephyr includes are now prefixed with <zephyr/...>. While the old path
can still be used when CONFIG_LEGACY_INCLUDE_PATH=y, it's better to be
prepared for the future.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
