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.

HTTPS API for TM4C1294NCPD NDK

Other Parts Discussed in Thread: TM4C1294NCPDT, CC3100

hi,

I'm evaluating the TM4C1294NCPD, I can't find the HTTPS API, does it exist this function? if yes, where can i find these API?

  • Eric,

    HTTPS support was recently updated in the TI-RTOS 2.14.00.10 release for TivaC.  Please see the description in Chapter 6  “TI-RTOS Network Services” in the TI-RTOS 2.14 User’s Guide (tirtos_User_Guide.pdf) in the release.  A link for downloading the release can be found here: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/tirtos/index.html

    Scott

  • Dear Scott,

    Thanks for your information, but why it get error when i build the sample project "HTTPS Client GET"? My CCS is 6.1 full license. 

  • Erik,

    Did you download and build the wolfSSL libraries?  The file “httsget_readme.txt” in the project points to the following wiki page, with instructions for doing this: http://processors.wiki.ti.com/index.php/Using_wolfSSL_with_TI-RTOS

    If you did follow those steps and still have a problem please let me know…

    Thanks,
    Scott

  • I was already builded and include library of wolfssl.arm4f(Maybe i lost sth.):

     But still got build error:

    step 1)Build wolfssl

    Building wolfSSL libraries

    After performing the set up steps, build the wolfSSL libraries as follows:

    1. Open your choice of terminal or command prompt.
    2. Type the following command: 
      cd tirtos_install_dir
    3. To build: 
      make -f tirtos.mak wolfssl
    4. To clean: 
      make -f tirtos.mak clean-wolfssl

    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.

    C:\ti\tirtos_tivac_2_14_00_10>..\xdctools_3_31_01_33_core\gmake
    -f tirtos.mak wolfssl

    step 2)include library and setting

    Add '<WolfSSL_dir>' path to the example compiler include path.

    In IAR Embedded Workbench:

    12. Read the "Example Usage" section of the tcpEchoTLS_readme.txt file for steps to test the application, including how to connect to a client tool (either Socat or the wolfSSL echoclient).

    Add the WolfSSL library to example linker options:
           '<WolfSSL_dir>/tirtos/packages/ti/net/wolfssl/lib/wolfssl.a<target>'

        Does wolfssl.a<target> is mean wolfssl.arm4f?


        NOTE: Make sure the library ordering is correct on the linker command line
              to avoid linker errors.

    step 3)got error.

    Building TI-RTOS wolfSSL example applications

  • Erik,

    Can you please post the full build error message that you got?  It was truncated in the attached picture.

    I can try to recreate this tomorrow…

    Thanks,
    Scott

  • Dear Scott,

    Below is the error message:

    Error while running "c:/ti/xdctools_3_31_01_33_core/xs" 
    --xdcpath="c:/ti/tirtos_tivac_2_14_00_10/packages;c:/ti/tirtos_tivac_2_14_00_10/products/bios_6_42_01_20/packages;c:/t
    i/tirtos_tivac_2_14_00_10/products/ndk_2_24_03_35/packages;c:/ti/tirtos_tivac_2_14_00_10/products/uia_2_00_02_39/p
    ackages" iar.tools.configuro -c "C:\Program Files\IAR Systems\Embedded Workbench 7.2\arm" --cc "C:\Program Files\
    IAR Systems\Embedded Workbench 7.2\arm\bin\iccarm.exe" --device "TM4C1294NCPDT" --compileOptions "-o C:\ti\
    tirtos_tivac_2_14_00_10\tirtos_tivac_2_14_00_10_examples\IAR\EK_TM4C1294XL\tcpEchoTLS\Debug\Obj\ --no_cse 
    --no_unroll --no_inline --no_code_motion --no_tbaa --no_clustering --no_scheduling --debug --endian=little 
    --cpu=Cortex-M4 -f C:\ti\tirtos_tivac_2_14_00_10\tirtos_tivac_2_14_00_10_examples\IAR\EK_TM4C1294XL\
    tcpEchoTLS/configPkg/compiler.opt.defs --diag_suppress=Pa050 
    -Ic:/ti/tirtos_tivac_2_14_00_10/products/TivaWare_C_Series-2.1.1.71b 
    -Ic:/ti/tirtos_tivac_2_14_00_10/packages/ti/drivers/wifi/cc3100/Simplelink 
    -Ic:/ti/tirtos_tivac_2_14_00_10/packages/ti/drivers/wifi/cc3100/Simplelink/Include -DPART_TM4C1294NCPDT -Dewarm 
    -DTIVAWARE --debug --silent -Ic:/ti/tirtos_tivac_2_14_00_10/products/ndk_2_24_03_35/packages/ti/ndk/inc/bsd 
    -DWOLFSSL_TIRTOS -Dc:\ti\wolfssl_commercial_3_6_0_01\wolfssl -e --fpu=VFPv4_sp --dlib_config \"C:\Program Files\
    IAR Systems\Embedded Workbench 7.2\arm\INC\c\DLib_Config_Normal.h\" -Ol" --linkOptions "-o C:\ti\
    tirtos_tivac_2_14_00_10\tirtos_tivac_2_14_00_10_examples\IAR\EK_TM4C1294XL\tcpEchoTLS\Debug\Exe\mytest1.out 
    --config C:\ti\tirtos_tivac_2_14_00_10\tirtos_tivac_2_14_00_10_examples\IAR\EK_TM4C1294XL\
    tcpEchoTLS/mytest1_EK_TM4C1294XL.icf -f C:\ti\tirtos_tivac_2_14_00_10\tirtos_tivac_2_14_00_10_examples\IAR\
    EK_TM4C1294XL\tcpEchoTLS/configPkg/linker.cmd --semihosting C:\ti\wolfssl_commercial_3_6_0_01\tirtos\packages\
    ti\net\wolfssl\lib\wolfssl.arm4f --entry __iar_program_start --vfe" --profile release --projFile "C:\ti\tirtos_tivac_2_14_00_10\
    tirtos_tivac_2_14_00_10_examples\IAR\EK_TM4C1294XL\tcpEchoTLS\mytest1.ewp"
     
    Total number of errors: 1
    Total number of warnings: 0

    =======================================================

    Environment:
    OS: Windows 7
    IDE: IAR 7.2
    TIRTOS:tirtos_tivac_2_14_00_10
    wolfssl:wolfssl-3.6.0

    Target of examples: tcpEchoTLS、httpsget

  • Erik,

    Looking at your screenshots, in the command window it looks like the wolfSSL libraries didn’t build.  When I do the build there is a bunch of output as the build proceeds, followed by the archiver running to archive the objects, and then finally the all files complete at the end.  This generates multiple screens of output, not a single screen as you show.  For example, at the start of the build:

    Have you verified that the library files exist?  My build directory is different, but you should see something like this:


    Note that the  <target> extension is “aem4f”.  The ‘a’ is for archive, the ‘e’ is for elf, ‘m4’ is the device, and ‘f’ is floating point.

    Can you please verify that the libraries exist for you?  If not, can you try doing a clean (with “gmake –f tirtos.mak clean-wolfssl”) and then build again (with “gmake –f tirtos.mak clean-wolfssl”)?

    Thanks,
    Scott

  • Dear Scott,

    is it successful building the wolfssl or not?(please refer to picture below) 

    if it was successful, i try to clean and rebuild my project, it still got error message same with before.

  • Erik,

    OK, thanks, I see the libraries were built.  It is very odd though that you don’t see any build status info in your command window. And sorry, for an IAR build the proper extension is indeed “.arm4f”.  (For builds with TI tool it is “.aem4f”.)

    I followed the instructions on the “Using wolfSSL with TI-RTOS” wiki, and the project built for me without any errors.  I then tried making a few changes to the project to see if I could get the same error as you show, but I didn’t; instead I saw useful error messages that indicated the problem that I would expect, for example “.. could not open file…”. 

    In the message you post, it says “Total number of errors: 1”, but nothing else to indicate what the specific error is.

    Just now as I was typing my response... I noticed that in your build message the IAR installation directory is “C:\Program Files\IAR Systems\Embedded Workbench 7.2\arm” .  I think the error you are seeing probably relates to the spaces in the IAR install directory path.  There are sometimes odd build errors when a path includes spaces.  I have not seen exactly what you are showing, but I’ve seen other odd problems on other devices because of this same problem with spaces in a path name. 

    In the Creating TI-RTOS aps in IAR workbench wiki (http://processors.wiki.ti.com/index.php/Creating_TI-RTOS_Applications_in_IAR_Embedded_Workbench), under “One-Time Initial Setup”, there is this warning:

    Can you please try re-installing IAR in a different install directory, which doesn’t have spaces in the directory path?  And please repeat those “One-Time Intial Setup” steps for the new install.

    I know this is a pain, but I think this will make the build error go away…

    Regards,
    Scott