OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/microkernel/test/test_mail/README.txt

62 lines
2.6 KiB
Plaintext
Raw Normal View History

First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
Title: test_mail
Description:
This test verifies that the microkernel mailbox APIs operate as expected.
--------------------------------------------------------------------------------
Building and Running Project:
This microkernel project outputs to the console. It can be built and executed
on QEMU as follows:
Fixed make target for running in qemu (microkernel) To run qemu, we only call 'make qemu' now Change-Id: Iedf70434c8d757d9b9a252652110eb1d91489d86 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-06-06 09:48:58 +08:00
make qemu
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
--------------------------------------------------------------------------------
Revise misleading instructions in sample project README.txt files Removes the instruction directing users to issue "make pristine" before building a sample project, as this should be unnecessary under normal circumstances and can cause the user to unexpectedly lose their current configuration information. In its place, a section on troubleshooting is added that describes how to rebuild a project using the desired configuration. Change-Id: I4eaace2888000c3ec5d101c27a38c74c2987312e Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2015-06-01 22:30:09 +08:00
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
--------------------------------------------------------------------------------
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
Sample Output:
Starting mailbox tests
===================================================================
MsgSenderTask: task_mbox_put to non-waiting task is OK
MsgRcvrTask: task_mbox_get when no message is OK
MsgSenderTask: task_mbox_put_wait_timeout to non-waiting task is OK
MsgRcvrTask: task_mbox_get_wait_timeout when no message is OK
MsgRcvrTask: task_mbox_get_wait from specified task is OK
MsgSenderTask: task_mbox_put to specified waiting task is OK
MsgRcvrTask: task_mbox_get from anonymous task is OK
MsgSenderTask: task_mbox_put_wait_timeout to anonymous non-waiting task is OK
MsgSenderTask: task_mbox_put_wait of empty message is OK
MsgRcvrTask: task_mbox_get_wait of empty message is OK
MsgRcvrTask: task_mbox_get_wait of message header #3 is OK
MsgRcvrTask: task_mbox_data_get of message data #3 is OK
MsgSenderTask: task_mbox_put_wait_timeout for 2 part receive test is OK
MsgRcvrTask: task_mbox_get_wait_timeout of message header #4 is OK
MsgRcvrTask: task_mbox_data_get cancellation of message #4 is OK
MsgSenderTask: task_mbox_put_wait for cancelled receive test is OK
MsgRcvrTask: task_mbox_get_wait of message header #1 is OK
pipes/mailboxes: rename functions using mem blocks task_pipe_put_async -> task_pipe_block_put task_mbox_put_async -> task_mbox_block_put task_mbox_data_get_async_block -> task_mbox_data_block_get task_mbox_data_get_async_block_wait -> task_mbox_data_block_get_wait task_mbox_data_get_async_block_wait_timeout -> task_mbox_data_block_get_wait_timeout Previous names, focusing on 'async', were misleading, because: - some of those APIs can be used synchronously as well - other APIs can also do asynchronous transfer, and don't have 'async' in their names - the key concept of these APIs is that they use memory pool blocks rather than raw data buffers. Change-Id: I0c08a6cf950ab23bb4172ce25eb6f9886b037649 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-11 05:37:25 +08:00
MsgRcvrTask: task_mbox_data_block_get of message data #1 is OK
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
MsgSenderTask: task_mbox_put_wait for block-based receive test is OK
MsgRcvrTask: task_mbox_get_wait of message header #2 is OK
pipes/mailboxes: rename functions using mem blocks task_pipe_put_async -> task_pipe_block_put task_mbox_put_async -> task_mbox_block_put task_mbox_data_get_async_block -> task_mbox_data_block_get task_mbox_data_get_async_block_wait -> task_mbox_data_block_get_wait task_mbox_data_get_async_block_wait_timeout -> task_mbox_data_block_get_wait_timeout Previous names, focusing on 'async', were misleading, because: - some of those APIs can be used synchronously as well - other APIs can also do asynchronous transfer, and don't have 'async' in their names - the key concept of these APIs is that they use memory pool blocks rather than raw data buffers. Change-Id: I0c08a6cf950ab23bb4172ce25eb6f9886b037649 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-08-11 05:37:25 +08:00
MsgRcvrTask: task_mbox_data_block_get of message data #2 is OK
First commit Signed-off-by: <inaky.perez-gonzalez@intel.com>
2015-04-11 07:44:37 +08:00
MsgSenderTask: task_mbox_put_wait for block-exhaustion receive test is OK
MsgRcvrTask: task_mbox_get_wait of message header #3 is OK
MsgRcvrTask: task_mbox_data_get of message data #3 is OK
MsgSenderTask: task_mbox_put_wait_timeout for long-duration receive test is OK
===================================================================
Eliminate VxMicro branding in sample project output Gets rid of obsolete OS name, which isn't really necessary anyway. Change-Id: Ic25b3addd43c84a75dacd6c61fdcc7a53217d320 Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2015-06-05 20:24:47 +08:00
PROJECT EXECUTION SUCCESSFUL