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>
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>
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>
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>
