407b49b35c
Using find_package to locate Zephyr.
Old behavior was to use $ENV{ZEPHYR_BASE} for inclusion of boiler plate
code.
Whenever an automatic run of CMake happend by the build system / IDE
then it was required that ZEPHYR_BASE was defined.
Using ZEPHYR_BASE only to locate the Zephyr package allows CMake to
cache the base variable and thus allowing subsequent invocation even
if ZEPHYR_BASE is not set in the environment.
It also removes the risk of strange build results if a user switchs
between different Zephyr based project folders and forgetting to reset
ZEPHYR_BASE before running ninja / make.
Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
|
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| README.rst | ||
| prj.conf | ||
| prj_mec15xxevb_assy6853.conf | ||
| sample.yaml | ||
README.rst
.. kscan-sample: KSCAN Interface #################################### Overview ******** This sample demonstrates how to use the :ref:`KSCAN API <kscan_api>`. Callbacks are registered that will write to the console indicating KSCAN events. These events indicate key presses and releases. Building and Running ******************** The sample can be built and executed on boards supporting a Keyboard Matrix. Please connect a Keyboard Matrix to exercise the functionality. You need to obtain the right keymap from the vendor because they vary across different manufactures. Sample output ============= .. code-block:: console KSCAN test with a Keyboard matrix Note: You are expected to see several callbacks as you press and release keys!