zephyr

History

Kumar Gala db167c606d dts: Rename LED._GPIO_* -> DT_ALIAS_LED._GPIOS_* We use the following commands to rename any LED._GPIO_{CONTROLLER,PIN,FLAGS} to DT_ALIAS_LED._GPIOS_{CONTROLLER,PIN,FLAGS} git grep -l LED._GPIO_CONTROLLER \| xargs sed -i 's/LED\(.\)_GPIO_CONTROLLER/DT_ALIAS_LED\1_GPIOS_CONTROLLER/g' git grep -l LED._GPIO_PIN \| xargs sed -i 's/LED\(.\)_GPIO_PIN/DT_ALIAS_LED\1_GPIOS_PIN/g' git grep -l LED._GPIO_FLAGS \| xargs sed -i 's/LED\(.\)_GPIO_FLAGS/DT_ALIAS_LED\1_GPIOS_FLAGS/g' Signed-off-by: Kumar Gala <kumar.gala@linaro.org>		2019-07-02 08:26:37 -04:00
..
src	dts: Rename LED._GPIO_* -> DT_ALIAS_LED._GPIOS_*	2019-07-02 08:26:37 -04:00
CMakeLists.txt	license: cleanup: add SPDX Apache-2.0 license identifier	2019-04-07 08:45:22 -04:00
README.rst	dts: Rename LED._GPIO_* -> DT_ALIAS_LED._GPIOS_*	2019-07-02 08:26:37 -04:00
prj.conf	…
sample.yaml	dts: Rename DT_._GPIO_ to DT_._GPIOS_	2019-06-27 13:02:34 -05:00

README.rst

.. _blinky-sample:

Blinky Application
##################

Overview
********

The Blinky example shows how to configure GPIO pins as outputs which can also be
used to drive LEDs on the hardware usually delivered as "User LEDs" on many of
the supported boards in Zephyr.

Requirements
************

The demo assumes that an LED is connected to one of GPIO lines. The
sample code is configured to work on boards that have defined the led0
alias in their board device tree description file. Doing so will generate
these variables:

- DT_ALIAS_LED0_GPIOS_CONTROLLER
- DT_ALIAS_LED0_GPIOS_PIN


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/blinky
   :board: reel_board
   :goals: build flash
   :compact:

After flashing the image to the board, the user LED on the board should start to
blink.