zephyr

History

Allan Stephens f4ba3b1d5d unified/test: Adapt floating point sharing test Microkernel and nanokernel tests now use customized source code to eliminate use of MICROKERNEL and NANOKERNEL config options. Change-Id: I7f9aff4729a7a257c4a0a0f5939ba0f5525af460 Signed-off-by: Allan Stephens <allan.stephens@windriver.com>		2016-10-25 00:10:35 +00:00
..
src	unified/test: Adapt floating point sharing test	2016-10-25 00:10:35 +00:00
Makefile	unified/test: Adapt floating point sharing test	2016-10-25 00:10:35 +00:00
README.txt	test_fp_sharing: Enable for Cortex-M4	2016-07-01 19:44:16 +00:00
prj.conf	tests: fp_sharing: removing dependency on ARCH	2016-09-15 21:16:40 +00:00
prj.mdef	tests: move kernel tests to tests/	2016-02-11 18:06:33 +00:00
testcase.ini	unified/test: Adapt floating point sharing test	2016-10-25 00:10:35 +00:00

README.txt

Title: Shared Floating Point Support

Description:

This test uses two tasks to independently compute pi, while two other tasks
load and store floating point registers and check for corruption. This tests
the ability of tasks to safely share floating point hardware resources, even
when switching occurs preemptively. (Note that both sets of tests run
concurrently even though they report their progress at different times.)

The demonstration utilizes microkernel mutex APIs, timers, semaphores,
round robin scheduling, and floating point support.

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

Building and Running Project:

This microkernel 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

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

Advanced:

Depending upon the board's speed, the frequency of test output may range from
every few seconds to every few minutes. The speed of the test can be controlled
through the variable PI_NUM_ITERATIONS (default 700000). Lowering this value
will increase the test's speed, but at the expense of the calculation's
precision.

    make qemu PI_NUM_ITERATIONS=100000

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

Sample Output:

Floating point sharing tests started
===================================================================
Pi calculation OK after 50 (high) + 1 (low) tests (computed 3.141594)
Load and store OK after 100 (high) + 29695 (low) tests
Pi calculation OK after 150 (high) + 2 (low) tests (computed 3.141594)
Load and store OK after 200 (high) + 47593 (low) tests
Pi calculation OK after 250 (high) + 4 (low) tests (computed 3.141594)
Load and store OK after 300 (high) + 66674 (low) tests
Pi calculation OK after 350 (high) + 5 (low) tests (computed 3.141594)
Load and store OK after 400 (high) + 83352 (low) tests
Pi calculation OK after 450 (high) + 7 (low) tests (computed 3.141594)
Load and store OK after 500 (high) + 92290 (low) tests
===================================================================
PROJECT EXECUTION SUCCESSFUL