mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-10 21:46:29 +00:00
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 |
.. _fade-led-sample: PWM: Fade LED ############# Overview ******** This is a sample app which fades a LED using PWM. The LED will start from dark and increases its brightness gradually for 10 seconds. Then, the brightness reduces gradually for 10 seconds and finally the LED becomes dark again. The LED will repeat this cycle for ever. Wiring ****** Nucleo_F401RE, Nucleo_L476RG ============================ Connect PWM2(PA0) to LED Nucleo_F103RB ============= Connect PWM1(PA8) to LED Nucleo_L496ZG ============= No special board setup is necessary because there are three on-board LEDs (red, green, blue) connected to the Nucleo's PWM. Hexiwear K64 ============ No special board setup is necessary because there is an on-board RGB LED connected to the K64 PWM. nrf52840dk_nrf52840 =================== No special board setup is necessary because there is an on-board LED connected. Building and Running ******************** This sample can be built for multiple boards, in this example we will build it for the nrf52840dk_nrf52840 board: .. zephyr-app-commands:: :zephyr-app: samples/basic/fade_led :board: nrf52840dk_nrf52840 :goals: build flash :compact: