zephyr

History

Anas Nashif f62d86c42b samples: get rid of obsolete usage of ARCH variable Using ARCH variable to select different configurations for the different architectures is misleading and conflicts with the variable ARCH being used by the build system. The variable is not needed, it is application specific and an application can be built without the need to specify ARCH on the command line. This is yet another item specific to samples and test cases that wrongfully being used and documented for every application. We need to use another variable and just make it clear it is specific to samples and how they are written. One possible solution is to have a script that gets the architecture based on the board being used. Attachments Jira: ZEP-238 Change-Id: Ieccbc087a41858fb96fb361c0aaa04705e968a4e Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2016-05-12 10:57:28 +00:00
..
src	move include directory for tests cases to tests/	2016-02-11 18:08:08 +00:00
Makefile	samples: get rid of obsolete usage of ARCH variable	2016-05-12 10:57:28 +00:00
README.txt	…
prj.conf	samples: get rid of obsolete usage of ARCH variable	2016-05-12 10:57:28 +00:00
prj.mdef	…
testcase.ini	…

README.txt

Title: test_aes_ccm

Description:

This test verifies that the TinyCrypt AES 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:

    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() - Performing CCM tests:
Performing CCM test #1 (RFC 3610 test vector #1):
===================================================================
PASS - do_test.
Performing CCM test #2 (RFC 3610 test vector #2):
===================================================================
PASS - do_test.
Performing CCM test #3 (RFC 3610 test vector #3):
===================================================================
PASS - do_test.
Performing CCM test #4 (RFC 3610 test vector #7):
===================================================================
PASS - do_test.
Performing CCM test #5 (RFC 3610 test vector #8):
===================================================================
PASS - do_test.
Performing CCM test #6 (RFC 3610 test vector #9):
===================================================================
PASS - do_test.
Performing CCM test #7 (no associated data):
===================================================================
PASS - test_vector_7.
Performing CCM test #8 (no payload data):
===================================================================
PASS - test_vector_8.
All CCM tests succeeded!
===================================================================
PASS - mainloop.
===================================================================
PROJECT EXECUTION SUCCESSFUL