mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-12 23:56:10 +00:00
The seasonal overhaul of test identifiers aligning the terms being used and creating a structure. This is hopefully the last time we do this, plan is to document the identifiers and enforce syntax. The end-goal is to be able to generate a testsuite description from the existing tests and sync it frequently with the testsuite in Testrail. Signed-off-by: Anas Nashif <anas.nashif@intel.com> |
||
---|---|---|
.. | ||
src | ||
CMakeLists.txt | ||
prj.conf | ||
README.rst | ||
sample.yaml |
.. _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 devicetree 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.