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: Remove board.h include	2018-11-01 13:15:18 +01:00
CMakeLists.txt	cmake: increase minimal required version to 3.13.1	2019-01-03 11:51:29 -05:00
README.rst	…
prj.conf	samples: threads: Fix ASSERTION FAIL without gpio driver	2019-03-03 23:48:11 -05:00
sample.yaml	samples: define harness for samples	2019-03-04 08:14:29 -05:00

README.rst

.. _96b_carbon_multi_thread_blinky:

Basic Thread Example
####################

Overview
********

This example demonstrates spawning of multiple threads using K_THREAD_DEFINE.

The example works by spawning three threads. The first two threads control a
separate LED. Both of these LEDs (USR1 and USR2) have their individual loop
control and timing logic defined by separate functions.

After either thread toggles its LED, it also pushes information into a
FIFO identifying which thread toggled its LED and how many times it
was done.

The third thread, ``uart_out()``, uses printk (over the UART) to
display the information that comes through the FIFO.

- blink1() controls the USR1 LED that has a 100ms sleep cycle
- blink2() controls the USR2 LED that has a 1000ms sleep cycle

Each thread is then defined at compile time using K_THREAD_DEFINE.

Building
********

.. zephyr-app-commands::
   :zephyr-app: samples/basic/threads
   :board: 96b_carbon
   :goals: build flash
   :compact: