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>
|
||
|---|---|---|
| .. | ||
| boards | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _pca9633: PCA9633: 4-Channel RGB ###################### Overview ******** This sample controls 4 LEDs connected to a PCA9633 driver, using the following pattern: 1. turn on LEDs 2. turn off LEDs 3. set the brightness to 50% 4. turn off LEDs 5. blink the LEDs 6. turn off LEDs Building and Running ******************** Build the application for the :ref:`stm32373c_eval_board` board, and connect a PCA9633 LED driver on the bus I2C-1 at the address 0x62. .. zephyr-app-commands:: :zephyr-app: samples/drivers/led_pca9633 :board: stm32373c_eval :goals: build :compact: For flashing the application, refer to the Flashing section of the :ref:`stm32373c_eval_board` board documentation. References ********** - PCA9633: https://www.nxp.com/docs/en/data-sheet/PCA9633.pdf