zephyr

History

Kumar Gala ee5c8ac7fb samples: blinky: cleanup to use just DT and remove board.h Now that we set LED info in the device tree for all boards we don't need to special case handle in the name/led pin (it comes from DT). We can also remove include board.h. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>		2018-11-09 11:53:18 -05:00
..
src	samples: blinky: cleanup to use just DT and remove board.h	2018-11-09 11:53:18 -05:00
CMakeLists.txt	samples, tests: Use semi-accurate project names	2018-10-27 21:31:25 -04:00
README.rst	samples: Allow use of "CONTROLLER" postfix for LED and GPIO	2018-04-19 09:32:39 -05:00
prj.conf	kernel: remove dependency on CONFIG_NANO_TIMERS/TIMEOUTS	2017-01-08 18:09:52 +00:00
sample.yaml	tests/samples: cleanup tags	2018-10-16 09:17:51 -04: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 with user defined buttons and that
have defined the LED0\_* variables in :file:`board.h`.

The :file:`board.h` must define the following variables:

- LED0_GPIO_NAME (or LED0_GPIO_CONTROLLER)
- LED0_GPIO_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: arduino_101
   :goals: build flash
   :compact:

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