bb5e1c3973
This PR fixes multiple issues in the source code to address issues raised by tests/scripts/check-files.py. Specifically: * incorrect file permissions * missing newline at the end of files * trailing whitespace * Tabs present * TODOs in the souce code
2.5 KiB
SHA-256 Hash Example
This application performs hashing of a buffer with SHA-256 using various APIs. It serves as a tutorial for the basic hashing APIs of mbed TLS.
Pre-requisites
To build and run this example you must have:
- A computer with the following software installed:
- CMake.
- yotta. Please note that yotta has its own set of dependencies, listed in the installation instructions.
- Python.
- The ARM GCC toolchain.
- A serial terminal emulator (Like screen, pySerial and cu).
- An FRDM-K64F development board, or another board supported by mbed OS (in which case you'll have to substitute frdm-k64f-gcc with the appropriate target in the instructions below).
- A micro-USB cable.
- If your OS is Windows, please follow the installation instructions for the serial port driver.
Getting started
-
Connect the FRDM-K64F to the computer with the micro-USB cable, being careful to use the "OpenSDA" connector on the target board.
-
Navigate to the mbedtls directory supplied with your release and open a terminal.
-
Set the yotta target:
yotta target frdm-k64f-gcc -
Build mbedtls and the examples. This may take a long time if this is your first compilation:
$ yotta build -
Copy
build/frdm-k64f-gcc/test/mbedtls-test-example-hashing.binto your mbed board and wait until the LED next to the USB port stops blinking. -
Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F.
Use the following settings:
- 115200 baud (not 9600).
- 8N1.
- No flow control.
-
Press the Reset button on the board.
-
The output in the terminal window should look like:
{{timeout;10}} {{host_test_name;default}} {{description;mbed TLS example on hashing}} {{test_id;MBEDTLS_EX_HASHING}} {{start}} Method 1: 315f5bdb76d078c43b8ac0064e4a0164612b1fce77c869345bfc94c75894edd3 Method 2: 315f5bdb76d078c43b8ac0064e4a0164612b1fce77c869345bfc94c75894edd3 Method 3: 315f5bdb76d078c43b8ac0064e4a0164612b1fce77c869345bfc94c75894edd3 Method 4: 315f5bdb76d078c43b8ac0064e4a0164612b1fce77c869345bfc94c75894edd3 DONE {{success}} {{end}}