mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-31 01:55:51 +00:00
b78ffc0e6b
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>
40 lines
949 B
ReStructuredText
40 lines
949 B
ReStructuredText
.. _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.
|