zephyr

History

Anas Nashif 66cfcc26bc tests: introduce Makefile.test To customise test builds and support test related features such as time stamps and a boot banner, introduce a Makefile variant that is dedicated to testing. Initially we introduce a new config overlay that is used for all tests, in this case we enable BOOT_BANNER and BUILD_TIMESTAMP. This will print the current version and the date, useful when reporting bugs and also an indicator that the system has booted before the test has started. For example: [QEMU] CPU: qemu32 *** BOOTING ZEPHYR OS v1.6.99 - BUILD: Dec 21 2016 19:57:13 *** tc_start() - Test Nanokernel CPU and thread routines Initializing nanokernel objects ... .. Change-Id: I224318cdeb55a301964ea366dbc577e2e3a09175 Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2017-01-03 17:48:44 +00:00
..
Makefile	tests: introduce Makefile.test	2017-01-03 17:48:44 +00:00
README.txt	…
prj.conf	kernel: disable MDEF by default	2016-12-12 20:25:07 +00:00
prj.mdef	…
testcase.ini	samples: tests: tag all legacy test cases and samples	2016-11-30 21:45:22 +00:00

README.txt

Title: Private Mailboxes

Description:

This test verifies that the microkernel mailbox APIs operate as expected.
This also verifies the mechanism to define private mailboxes and their usage.

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

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

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

Sample Output:

Starting mailbox tests
===================================================================
MsgSenderTask: task_mbox_put(TICKS_NONE) to non-waiting task is OK
MsgRcvrTask: task_mbox_get when no message is OK
MsgSenderTask: task_mbox_put(timeout) to non-waiting task is OK
MsgRcvrTask: task_mbox_get(timeout) when no message is OK
MsgRcvrTask: task_mbox_get(TICKS_UNLIMITED) from specified task is OK
MsgSenderTask: task_mbox_put(TICKS_NONE) to specified waiting task is OK
MsgRcvrTask: task_mbox_get from anonymous task is OK
MsgSenderTask: task_mbox_put(timeout) to anonymous non-waiting task is OK
MsgSenderTask: task_mbox_put(TICKS_UNLIMITED) of empty message is OK
MsgRcvrTask: task_mbox_get(TICKS_UNLIMITED) of empty message is OK
MsgRcvrTask: task_mbox_get(TICKS_UNLIMITED) of message header #3 is OK
MsgRcvrTask: task_mbox_data_get of message data #3 is OK
MsgSenderTask: task_mbox_put(timeout) for 2 part receive test is OK
MsgRcvrTask: task_mbox_get(timeout) of message header #4 is OK
MsgRcvrTask: task_mbox_data_get cancellation of message #4 is OK
MsgSenderTask: task_mbox_put(TICKS_UNLIMITED) for cancelled receive test is OK
MsgRcvrTask: task_mbox_get(TICKS_UNLIMITED) of message header #1 is OK
MsgRcvrTask: task_mbox_data_block_get of message data #1 is OK
MsgSenderTask: task_mbox_put(TICKS_UNLIMITED) for block-based receive test is OK
MsgRcvrTask: task_mbox_get(TICKS_UNLIMITED) of message header #2 is OK
MsgRcvrTask: task_mbox_data_block_get of message data #2 is OK
MsgSenderTask: task_mbox_put(TICKS_UNLIMITED) for block-exhaustion receive test is OK
MsgRcvrTask: task_mbox_get(TICKS_UNLIMITED) of message header #3 is OK
MsgRcvrTask: task_mbox_data_get of message data #3 is OK
MsgSenderTask: task_mbox_put(timeout) for long-duration receive test is OK
===================================================================
PROJECT EXECUTION SUCCESSFUL