zephyr

History

Anas Nashif dc96f16bcd samples: define harness for samples Most of the basic tests trigger LEDs or expect button press and would hang in device testing because we can't parse success or failure from the console. Define harness for this with the intent to skip those in sanitycheck device testing and until we have a better way to test those. Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2019-03-04 08:14:29 -05:00
..
src	samples: blinky: cleanup to use just DT and remove board.h	2018-11-09 11:53:18 -05:00
CMakeLists.txt	cmake: increase minimal required version to 3.13.1	2019-01-03 11:51:29 -05:00
prj.conf	kernel: remove dependency on CONFIG_NANO_TIMERS/TIMEOUTS	2017-01-08 18:09:52 +00:00
README.rst	samples/basic: Update readme for blinky/button/disco	2018-12-26 09:46:59 -05:00
sample.yaml	samples: define harness for samples	2019-03-04 08:14:29 -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:

- 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.