zephyr

History

David B. Kinder b78ffc0e6b doc: add labels to basic sample docs Docs need a label at the top so we can use :ref:`labelname` to create a link to that doc from other docs. Change-Id: I57d65a8888f78aa61d776f607a5db86bdb35726c Signed-off-by: David B. Kinder <david.b.kinder@intel.com>		2017-04-04 19:51:47 +00:00
..
src	license: Replace Apache boilerplate with SPDX tag	2017-01-19 03:50:58 +00:00
Makefile	samples: tests: remove obsolete KERNEL_TYPE and kernel variables	2016-11-04 15:47:25 -04:00
README.rst	doc: add labels to basic sample docs	2017-04-04 19:51:47 +00:00
prj.conf	kernel: remove dependency on CONFIG_NANO_TIMERS/TIMEOUTS	2017-01-08 18:09:52 +00:00
testcase.ini	samples: add some missing testcase.ini	2017-02-23 13:28:03 +00: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_PORT
- 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:

.. code-block:: console

   $ cd samples/basic/blinky
   $ make BOARD=arduino_101
   $ make BOARD=arduino_101 flash

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