This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WolfSSL with TM4C1294XL

I wanted to use HTTPS client example with TM4C1294XL on IAR compiler.

I build WolfSSL by modifying setting.h file located in "C:\ti\wolfssl-3.9.10\wolfssl\wolfcrypt" directory and added following configurations

 #define WOLFSSL_IAR_ARM

 #define WOLFSSL_TIRTOS

However, the final library did not work. I continuously got the error message when HTTPS GET command was sent. I then tried to build the library on my laptop and accidently use the Setting.h file of "ctaocrypt" folder, instead of "Wolfssl" Folder. 

I was able to get the follow response after building the library. 


Sending an HTTPS GET request to 'www.example.com:443'
HTTP Response Status Code: 200
Received 1270 bytes of payload

So the question is why WolfSSL did not work the first time when I modified Settings.h of "C:\ti\wolfssl-3.9.10\wolfssl\wolfcrypt. 

I am using

1. "tirtos_tivac_2_16_01_14"

2. wolfssl-3.9.10

3. IAR 7.4

 

  • Fehan,

    We have documented instructions on TIRTOS & WolfSSL usage here.

    Hope this helps,

    Derrick

  • Hi,

    I did use these instructions to successfuly build and use the wolfSSL for the TI-RTOS. I just needed to know why wolfSSL does not work if following are defined in "setting.h file located in "C:\ti\wolfssl-3.9.10\wolfssl\wolfcrypt

    #define WOLFSSL_IAR_ARM

    #define WOLFSSL_TIRTOS

    Or should I ask this question in WolfSSL forum?
  • Fehan,

    It looks like you want to use the IAR ARM compiler with TIRTOS.

    You should only have #define WOLFSSL_TIRTOS.

    To use the IAR ARM compiler, examine step 2 of Build Instructions>Setup.

    Edit the products.mak file. Update the XDC_INSTALL_DIRBIOS_INSTALL_DIRNDK_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).

    For example:

    iar.targets.arm.M4F    = C:/IAR/<compiler path>

    Derrick

  • There was a suggested answer and since there has been no active on this thread for more than a week, the suggested answer was marked as verify. Please feel free to select the "Reject Answer" button and reply with more details.