mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-22 14:15:22 +00:00
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 | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _rgb-led-sample: PWM: RGB LED ############ Overview ******** This is a sample app which drives a RGB LED using PWM. There are three single-color component LEDs in an RGB LED. Each component LED is driven by a PWM port where the pulse width is changed from zero to a fusion flicker threshold (the minimum flicker rate where the LED is perceived as being steady), causing each component LED to step from dark to max brightness. Three **for** loops (one for each component LED) generate a gradual range of color changes from the RGB LED, and the sample repeats forever. Wiring ****** Hexiwear K64 ============ No special board setup is necessary because there is an on-board RGB LED connected to the K64 PWM. Building and Running ******************** This samples does not output anything to the console. It can be built and flashed to a board as follows: .. zephyr-app-commands:: :zephyr-app: samples/basic/rgb_led :board: hexiwear_k64 :goals: build flash :compact: