| Manuel Pégourié-Gonnard | 63e7eba | 2015-07-28 14:17:48 +0200 | [diff] [blame^] | 1 | # mbed TLS selftest programs |
| 2 | |
| 3 | This application runs the various selftest function of individual mbed TLS components. It serves as a basic sanity check for mbed TLS on your platform. In the future, a wider portion of the mbed TLS test suite will be ported on mbed OS. |
| 4 | |
| 5 | ## Pre-requisites |
| 6 | |
| 7 | To build and run this example the requirements below are necessary: |
| 8 | |
| 9 | * A computer with the following software installed: |
| 10 | * [CMake](http://www.cmake.org/download/). |
| 11 | * [yotta](https://github.com/ARMmbed/yotta). Please note that **yotta has its own set of dependencies**, listed in the [installation instructions](http://armmbed.github.io/yotta/#installing-on-windows). |
| 12 | * [Python](https://www.python.org/downloads/). |
| 13 | * [ARM GCC toolchain](https://launchpad.net/gcc-arm-embedded). |
| 14 | * A serial terminal emulator (e.g. screen, pySerial, cu). |
| 15 | * An [FRDM-K64F](http://developer.mbed.org/platforms/FRDM-K64F/) development board, or another board supported by mbed OS (in that case you'll have to substitute frdm-k64f-gcc with the appropriate target below). |
| 16 | * A micro-USB cable. |
| 17 | * If your OS is Windows, please follow the installation instructions [for the serial port driver](https://developer.mbed.org/handbook/Windows-serial-configuration). |
| 18 | |
| 19 | ## Getting started |
| 20 | |
| 21 | 1. Connect the FRDM-K64F to the computer with the micro-USB cable, being careful to use the micro-usb port labeled "OpenSDA". |
| 22 | |
| 23 | 2. Navigate to the mbedtls directory supplied with your release and open a terminal. |
| 24 | |
| 25 | 3. Set the yotta target: |
| 26 | |
| 27 | ``` |
| 28 | yotta target frdm-k64f-gcc |
| 29 | ``` |
| 30 | |
| 31 | 4. Check that there are no missing dependencies: |
| 32 | |
| 33 | ``` |
| 34 | $ yt ls |
| 35 | ``` |
| 36 | |
| 37 | If there are, yotta will list them in the terminal. Please install them before proceeding. |
| 38 | |
| 39 | 5. Build mbedtls and the examples. This will take a long time if it is the first time: |
| 40 | |
| 41 | ``` |
| 42 | $ yt build |
| 43 | ``` |
| 44 | |
| 45 | 6. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-selftest.bin` to your mbed board and wait until the LED next to the USB port stops blinking. |
| 46 | |
| 47 | 7. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 9600 baud, 8N1, no flow control. |
| 48 | |
| 49 | 8. Press the reset button on the board. |
| 50 | |
| 51 | 9. The output in the terminal window should look like: |
| 52 | |
| 53 | ``` |
| 54 | {{timeout;40}} |
| 55 | {{host_test_name;default}} |
| 56 | {{description;mbed TLS selftest program}} |
| 57 | {{test_id;MBEDTLS_SELFTEST}} |
| 58 | {{start}} |
| 59 | |
| 60 | SHA-1 test #1: passed |
| 61 | SHA-1 test #2: passed |
| 62 | SHA-1 test #3: passed |
| 63 | |
| 64 | SHA-224 test #1: passed |
| 65 | SHA-224 test #2: passed |
| 66 | SHA-224 test #3: passed |
| 67 | SHA-256 test #1: passed |
| 68 | SHA-256 test #2: passed |
| 69 | SHA-256 test #3: passed |
| 70 | |
| 71 | [ ... several lines omitted ... ] |
| 72 | |
| 73 | CTR_DRBG (PR = TRUE) : passed |
| 74 | CTR_DRBG (PR = FALSE): passed |
| 75 | |
| 76 | HMAC_DRBG (PR = True) : passed |
| 77 | HMAC_DRBG (PR = False) : passed |
| 78 | |
| 79 | ECP test #1 (constant op_count, base point G): passed |
| 80 | ECP test #2 (constant op_count, other point): passed |
| 81 | |
| 82 | ENTROPY test: passed |
| 83 | |
| 84 | [ All tests passed ] |
| 85 | |
| 86 | {{success}} |
| 87 | {{end}} |
| 88 | ``` |