EK-TM4C129EXL: wolfSSL in to TO-RTOS

Hi Philippe,

I pulled the relevant info from the page and pasted it here.

That's all the support I can really provide here as our team has no knowledge of WolfSSL.

This content is pretty old so it may not work, but at least it's something you can try and use.

WolfSSL

Download the wolfSSL product from:

• WolfSSL github downloads -- a GPL licensed product
• For commercial licenses, please contact wolfSSL

Installation

Install TI-RTOS and wolfSSL as follows:

TI-RTOS

• Run the installer and follow the instructions. We recommend installing TI-RTOS in the default location (i.e. C:/ti).

WolfSSL

• If you downloaded an installer, run the installer and follow the instructions.
• If you downloaded a *.zip file, extract the contents to your disk (for example, in C:/ti/wolfssl).

Build Instructions

Setup

1. Open a terminal or command prompt and type:
   cd wolfSSL_install_dir/tirtos
2. Edit the products.mak file. Update the XDC_INSTALL_DIR, BIOS_INSTALL_DIR, NDK_INSTALL_DIR and TIVAWARE_INSTALL_DIR variables. XDCtools, BIOS, NDK, Tivaware products are part of the TI-RTOS installation. Update the code generation tools path for any of the tool chains - ti.targets.arm.elf.M4F (i.e. TI), iar.targets.arm.M4F (i.e. IAR) or gnu.targets.arm.M4F (i.e. GCC). After modification, these variable definitions should look similar to the following if you are working on Windows. (Windows users: note the use of "/" in the path).
   XDC_INSTALL_DIR = C:/ti/xdctools_3_31_01_33
BIOS_INSTALL_DIR = C:/ti/tirtos_tivac_2_16_00_00/products/bios_6_45_01_23
NDK_INSTALL_DIR = C:/ti/tirtos_tivac_2_16_00_00/products/ndk_2_25_00_08
TIVAWARE_INSTALL_DIR = C:/ti/tirtos_tivac_2_16_00_00/products/TivaWare_C_Series-2.1.1.71b
ti.targets.arm.elf.M4F = C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.4

For example: export XDCTOOLS_JAVA_HOME = C:/ti/ccsv6/eclipse/jre

Build

WolfSSL library for TI-RTOS has been configured to include the ciphers that are enabled by default. Users can update the configuration to include/exclude ciphers from the library. The TI-RTOS configuration in wolfSSL can be found wolfssl_install_dir/wolfssl/wolfcrypt/settings.h under #ifdef WOLFSSL_TIRTOS. Read building wolfSSL manual for the various build defines.

After configuration update (if any), build the wolfSSL libraries as follows:

1. To build:
   make -f wolfssl.mak all
2. To clean:
   make -f wolfssl.mak clean

If the "make" tool is not installed on your machine, you can use the "gmake" tool available in XDCtools which is installed along with TI-RTOS.

Linking with the wolfSSL library in your TI-RTOS application

Examples are provided as a part of the TI-RTOS product. See TI-RTOS for TivaC Getting Started Guide (SPRUHU5) for detailed information on importing projects into CCS or IAR and a list of examples that use WolfSSL.

The wolfSSL library path must be added to both the compiler and linker build options.

This process differs based on the compiler toolchain that you are building for (TI, IAR, and GNU). The library file path wolfSSL_lib will either be:

For software based cipher:

wolfSSL_install_dir/tirtos/packages/ti/net/wolfssl/lib/wolfssl.atarget

For hardware accelerated cipher (works only on Crypto Connected Launchpad):

wolfSSL_install_dir/tirtos/packages/ti/net/wolfssl/lib/wolfssl_tm4c_hw.atarget

Example building with the TI compiler:

For the EK-TM4C129EXL that supports hardware acceleration, the library could be)

C:/ti/wolfssl/tirtos/packages/ti/net/wolfssl/lib/wolfssl_tm4c_hw.aem4f

TI Compiler builds within CCS

1. Add the wolfSSL_install_dir path to Add dir to.. window within Build->ARM Compiler->Include Options.

2. Add the wolfSSL_lib to the Include Library File window within Build->ARM Linker->File Search Path.

For Command line builds

The wolfssl library path must be added to the makedefs file to ensure the library ordering is correct to avoid linker errors.

Within the generated TIRTOS examples directory, located within your TIRTOS install directory, edit the
”TIRTOS_examples_dir”/”COMPILER”/”BOARD_dir”/makedefs file and add the correct WolfSSL library(See above) to the LFLAGS variable.

For reference, example link lines are shown for each toolchain below

For TI Command line builds

Ex 1) LFLAGS = -l"<WOLFSSL_lib>" <LINKERFLAGS> -llibc.a

Ex 2)

LFLAGS = -l"<WOLFSSL_lib>" -l$(TIVAWARE_INSTALL_DIR)/grlib/ccs/Debug/grlib.lib -l$(TIVAWARE_INSTALL_DIR)/driverlib/ccs/Debug/driverlib.lib EK_TM4C1294XL.cmd -m$(NAME).map --warn_sections --rom_model -i$(CODEGEN_INSTALL_DIR)/lib -llibc.a

Best Regards,

Ralph Jacobi