zephyr/samples/nanokernel/test/test_timer
Benjamin Walsh 3ade2211de test_timer: remove lingering mentions of 'node' in API names
Change-Id: I9d6e64470e0c7128a620d8af3d0c813a63964860
Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-02-05 20:15:36 -05:00
..
src test_timer: remove lingering mentions of 'node' in API names 2016-02-05 20:15:36 -05:00
Makefile Renames supported platform configurations 2016-02-05 20:14:39 -05:00
prj_arc.conf sanitychecks: add conf files for arc tests 2016-02-05 20:15:35 -05:00
prj_arm.conf First commit 2015-04-10 16:44:37 -07:00
prj_x86.conf CONFIG_DRV_RANDOM is obsolete 2016-02-05 20:15:35 -05:00
README.txt Update Title in sample project README.txt files 2016-02-05 20:15:21 -05:00
testcase.ini initial commit for next-gen sanity checks 2016-02-05 20:14:42 -05:00

Title: Timer APIs

Description:

This test verifies that the nanokernel timer APIs operate as expected.

---------------------------------------------------------------------------

Building and Running Project:

This nanokernel project outputs to the console.  It can be built and executed
on QEMU as follows:

    make qemu

---------------------------------------------------------------------------

Troubleshooting:

Problems caused by out-dated project information can be addressed by
issuing one of the following commands then rebuilding the project:

    make clean          # discard results of previous builds
                        # but keep existing configuration info
or
    make pristine       # discard results of previous builds
                        # and restore pre-defined configuration info

---------------------------------------------------------------------------

Sample Output:

tc_start() - Test Nanokernel Timer
Task testing basic timer functionality
  - test expected to take four seconds
Task testing timers expire in the correct order
  - test expected to take five or six seconds
Task testing the stopping of timers
  - test expected to take six seconds
Fiber testing basic timer functionality
  - test expected to take four seconds
Fiber testing timers expire in the correct order
  - test expected to take five or six seconds
Task testing the stopping of timers
  - test expected to take six seconds
Fiber to stop a timer that has a waiting fiber
Task to stop a timer that has a waiting fiber
PASS - main.
===================================================================
PROJECT EXECUTION SUCCESSFUL