OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/crypto/test_ctr
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 tests: move crypto tests to tests/crypto 2016-02-11 18:00:35 +00:00
prj.conf samples: get rid of obsolete usage of ARCH variable 2016-05-12 10:57:28 +00:00
prj.mdef tests: move crypto tests to tests/crypto 2016-02-11 18:00:35 +00:00
testcase.ini tests: move crypto tests to tests/crypto 2016-02-11 18:00:35 +00:00

README.txt 

Title: test_aes

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 AES128-CTR mode tests:
Performing CTR tests:
CTR test #1 (encryption SP 800-38a tests):
===================================================================
PASS - test_1_and_2.
CTR test #2 (decryption SP 800-38a tests):
===================================================================
PASS - test_1_and_2.
All CTR tests succeeded!
===================================================================
PASS - mainloop.
===================================================================
PROJECT EXECUTION SUCCESSFUL