Follow the instructions on the SiFive GitHub here and SiFive website here to download the freedom-e-sdk and software tools.
Run a simple hello application on your development board to confirm that your board functions as expected and the communication between your computer and the board works.

Usage

You can start with a wolfcrypt example project to integrate the wolfSSL source code. wolfSSL supports a compile-time user configurable options in the IDE/ECLIPSE/SIFIVE/user_settings.h file.

The IDE/ECLIPSE/SIFIVE/main.c example application provides a function to run the selected examples at compile time through the following two #defines in user_settings.h. You can define these macro options to disable the test run.

- #undef NO_CRYPT_TEST
- #undef NO_CRYPT_BENCHMARK

Setup

Setting up the SDK with wolfSSL

Download the wolfSSL source code or a zip file from GitHub and place it under your SDK $HOME directory. You can also copy or simlink to the source.

  For example,
  $ cd $HOME
  $ git clone --depth=1 https://github.com/wolfSSL/wolfssl.git

Copy the wolfcrypt example project into your freedom-e-sdk/software directory.

  $ cp -rf ~/wolfssl/IDE/ECLIPSE/SIFIVE ~/freedom-e-sdk/software/wolfcrypt

Edit your ~/freedom-e-sdk/scripts/standalone.mk and add the following line after the last RISCV_CFLAGS entry:

  RISCV_CFLAGS += -I$(WOLFSSL_SRC_DIR) -I$(WOLFSSL_SRC_DIR)/IDE/ECLIPSE/SIFIVE -DWOLFSSL_USER_SETTINGS

WOLFSSL_SRC_DIR variable must be set in the environment when GNU make is started.

  $ export WOLFSSL_SRC_DIR=~/wolfssl

Setup your riscv64 compiler

  $ export RISCV_OPENOCD_PATH=/opt/riscv-openocd

(Optional) Setup OpenOCD if your target supports it:

  $ export RISCV_OPENOCD_PATH=/opt/riscv-openocd

Building and Running

You can build from source or create a static library.

Using command-line:

  $ cd freedom-e-sdk
  $ make PROGRAM=wolfcrypt TARGET=sifive-hifive1-revb CONFIGURATION=debug clean software upload

This example cleans, builds and uploads the software on the sifive-hifive1-revb target but you can also combine and build for any of the supported targets.

Review the test results on the target console.

Building a static library for RISC-V using a cross-compiler:

$ cd $WOLFSSL_SRC_DIR

$./configure --host=riscv64-unknown-elf  \
CC=riscv64-unknown-elf-gcc \
AR=riscv64-unknown-elf-ar \
AS=riscv64-unknown-elf-as \
RANLIB=$RISCV_PATH/bin/riscv64-unknown-elf-gcc-ranlib \
LD=riscv64-unknown-elf-ld \
CXX=riscv64-unknown-elf-g++ \
--disable-examples --enable-static --disable-shared \
CFLAGS="-march=rv32imac -mabi=ilp32 -mcmodel=medlow -ffunction-sections -fdata-sections -I~/freedom-e-sdk/bsp/sifive-hifive1/install/include -O0 -g -DNO_FILESYSTEM -DWOLFSSL_NO_SOCK -DNO_WRITEV -DWOLFCRYPT_ONLY -DWOLFSSL_SIFIVE_RISC_V"

$make
$sudo make install

You can now build and link your software to the wolfSSL libwolfssl.a static library.

`wolfcrypt_test()`

wolfcrypt_test() prints a message on the target console similar to the following output:

SiFive HiFive1 Demo
Setting clock to 320MHz
Actual Clock 320MHz

error    test passed!
MEMORY   test passed!
base64   test passed!
asn      test passed!
SHA      test passed!
SHA-256  test passed!
SHA-512  test passed!
Hash     test passed!
HMAC-SHA test passed!
HMAC-SHA256 test passed!
HMAC-SHA512 test passed!
GMAC     test passed!
Chacha   test passed!
POLY1305 test passed!
ChaCha20-Poly1305 AEAD test passed!
AES      test passed!
AES192   test passed!
AES256   test passed!
AES-GCM  test passed!
RANDOM   test passed!
ECC      test passed!
ECC buffer test passed!
CURVE25519 test passed!
ED25519  test passed!
logging  test passed!
mutex    test passed!
Test complete

`benchmark_test()`

benchmark_test() prints a message on the target console similar to the following output.

TARGET=sifive-hifive1-revb:

SiFive HiFive1 Demo
Setting clock to 320MHz
Actual Clock 320MHz

------------------------------------------------------------------------------
 wolfSSL version 4.0.0
------------------------------------------------------------------------------
wolfCrypt Benchmark (block bytes 1024, min 1.0 sec each)
RNG                200 KB took 1.044 seconds,  191.519 KB/s
AES-128-CBC-enc     50 KB took 1.657 seconds,   30.174 KB/s
AES-128-CBC-dec     50 KB took 1.659 seconds,   30.141 KB/s
AES-192-CBC-enc     50 KB took 1.837 seconds,   27.220 KB/s
AES-192-CBC-dec     50 KB took 1.839 seconds,   27.194 KB/s
AES-256-CBC-enc     25 KB took 1.009 seconds,   24.784 KB/s
AES-256-CBC-dec     25 KB took 1.010 seconds,   24.761 KB/s
AES-128-GCM-enc     25 KB took 1.493 seconds,   16.739 KB/s
AES-128-GCM-dec     25 KB took 1.564 seconds,   15.986 KB/s
AES-192-GCM-enc     25 KB took 1.591 seconds,   15.716 KB/s
AES-192-GCM-dec     25 KB took 1.662 seconds,   15.044 KB/s
AES-256-GCM-enc     25 KB took 1.684 seconds,   14.843 KB/s
AES-256-GCM-dec     25 KB took 1.755 seconds,   14.245 KB/s
CHACHA               1 MB took 1.004 seconds,    0.997 MB/s
CHA-POLY           675 KB took 1.021 seconds,  661.060 KB/s
POLY1305             2 MB took 1.007 seconds,    2.230 MB/s
SHA                  1 MB took 1.016 seconds,    1.321 MB/s
SHA-256            425 KB took 1.005 seconds,  422.909 KB/s
SHA-512            225 KB took 1.009 seconds,  223.073 KB/s
HMAC-SHA             1 MB took 1.010 seconds,    1.378 MB/s
HMAC-SHA256        425 KB took 1.037 seconds,  409.781 KB/s
HMAC-SHA512         25 KB took 2.075 seconds,   12.050 KB/s
ECC      256 key gen         2 ops took 1.099 sec, avg 549.271 ms, 1.821 ops/sec
ECDHE    256 agree           2 ops took 1.093 sec, avg 546.555 ms, 1.830 ops/sec
ECDSA    256 sign            2 ops took 1.167 sec, avg 583.694 ms, 1.713 ops/sec
ECDSA    256 verify          2 ops took 2.136 sec, avg 1067.795 ms, 0.937 ops/sec
CURVE  25519 key gen         2 ops took 1.693 sec, avg 846.451 ms, 1.181 ops/sec
CURVE  25519 agree           2 ops took 1.689 sec, avg 844.299 ms, 1.184 ops/sec
ED     25519 key gen         1 ops took 1.702 sec, avg 1702.057 ms, 0.588 ops/sec
ED     25519 sign            2 ops took 3.650 sec, avg 1824.753 ms, 0.548 ops/sec
ED     25519 verify          2 ops took 5.788 sec, avg 2894.012 ms, 0.346 ops/sec
Benchmark complete

Tested Configurations

P-RNG (NIST DRBG) with SHA-256
SHA 1/256/512
AES 128/192/256 CBC/GCM
ECC 256 sign/verify/shared secret with fast math or Single Precision (SP) library
ED25519/Curve25519
HMAC
ChaCha20/Poly1305

Known Caveats

If you find the wolfcrypt test stuck on early_trap_vector error, it is like related to memory issues
Using the __stack_size default value of 0x400 will not be enough for the ECC test to pass. The IDE/ECLIPSE/SIFIVE/Makefile overwrites the value with 0x1000 (4 KBytes)
Enabling RSA will cause the ECC test to fail due to memory shortage.

References

The test results were collected from a SiFive reference platform target with the following hardware, software and tool chains:

HiFive1 Rev A/Rev B: HiFive1 Development Board with the Freedom Everywhere SoC, E300
freedom-e-sdk
wolfssl latest version

For more information or questions, please email support@wolfssl.com