Hi BKPatel,

For our curiousity here at wolfSSL could you give us some details about your project. What are the end goals of your project, how will it be used etc. We are always excited to hear how consumers are using our product!

I have a few questions pertaining to your post:

1. Is there a reason it has to be CyaSSL 3.0.0 and you can not upgrade to wolfSSL 3.3.3 or later?
    (wolfSSL 3.6.6 would be the most recent)
    I ask because while we have support for both, TI has quickly adopted our library with the name-changed to wolfSSL
    as of release wolfSSL 3.3.3
    TI has shifted their development efforts from CyaSSL to wolfSSL.

2. Are you developing in Code Composer Studio or some other IDE/Environment?
    If in CCS see the end of this response for possible solution.

3. Have you seen our quick-start Readme for TivaC and wolfSSL here:
    https://github.com/wolfSSL/wolfssl-exam … /README.md

4. Is there a reason you are trying to build a .lib instead of using the TivaC .aem4f format?

Possible solution if using CCS:

You can follow these steps from the quick-start guide on linking to the .aem4f library. That is the format expected by TivaC.

Right click on your project and select Properties (usually near the bottom)
Under Build -> ARM Linker -> File Search Path

In the browser window on the right under "Include library file or command file as input"
Click the add button and add this line "C:\wolfssl\tirtos\packages\ti\net\wolfssl\lib\wolfssl.aem4f"

In the browser window on the right under "Add dir to library search path"
Click the add button and add this line "C:\wolfssl\tirtos\packages\ti\net\wolfssl\lib"

Kind Regards,

Kaleb

Hi BKPatel,

Your issue is clear to me now. What is the problem with TI-RTOS that makes you want to use FREE-RTOS. In researching your questions I have found many questions asked about building freeRTOS with TivaC, most of which have little or no response and all mention this is not a well-documented process. What are the end-goals for your project and are there any deadlines?

I ask because I am leaving for vacation tonight after work and will be out of the office until Sept. 14th. That is when I would begin tracking down a solution / building a toolchain to cross-compile. I know you had not gotten any response from the Texas Instruments support but I would have to point you back their way if you are pressed for time.

The best way to contact TI in this regards is to use http://e2e.ti.com/support/development_tools/ and search for old cases or ask about tool chains for compiling an external c library on linux for use in CCS.

In the recent past we did a build of our libraries with freeRTOS using the Rowley Crossworks compiler. Without looking into it much further my best guess is that it will require something along those lines, but it may be too early to say for sure.

I am aware that the TivaC is typically flashed with a .aem4f formatted library which is abstracted above binary so I'm not sure the current approach of attempting to output a binary library will work on the TivaC processor. I am not 100% on that however. I would need to contact TI and see what they have to say on the matter.
See: http://www.ti.com/lit/ug/spru523i/spru523i.pdf

The file extensions for pre-built libraries provided with the NDK include the following:

.aem4 For Cortex-M4 targets (ELF format, little endian, TI compiler)
.am4g For Cortex-M4 targets (ELF format, little endian, GNU compiler)
.arm4 For Cortex-M4 targets (ELF format, little endian, IAR compiler)
.aem4f For Cortex-M4F floating point targets (ELF format, little endian, TI compiler)
.am4fg For Cortex-M4F floating point targets (ELF format, little endian, GNU compiler)
.arm4f For Cortex-M4F floating point targets (ELF format, little endian, IAR compiler)

Thank You for contacting us. I hope you can resolve this quickly. Otherwise I look forward to supporting you upon my return.

Kind Regards,

Kaleb

Hi Kaleb,

Thanks for the reply. I tried but not able to resolve the issue.
I have included FreeRTOS with LWIP in to the project and that is working well. Now my requirement is REST APIs (GET,POST etc) which are called should be secured.
I tried with CyaSSL 3.3.0 and WolfSSL 3.4.6. I tried to build the code using Visual Studio and it is not allowing to build lib for ARM.
I also tried it with Ubuntu as mentioned in section 2.6 https://wolfssl.com/wolfSSL/Docs-wolfss … lfssl.html
But it is always generating .a file for Intel x86 not for ARM.

With TI-RTOS I am getting Stack Overflow errors after continuously sending GET, POST command even without using HTTPS so can not continue with it .
Can you help me to build library file which can be used with Tiva C Processor than I can start further coding?
My project is currently in Development stage and deadline is 20th Sep to complete Secure GET and POST command using HTTPS.

Thanks,
Bhavesh

Hi Kaleb,

I tried using sudo sh ./configure --host=arm-none-eabi but still it is giving below error.

checking build system type... i686-pc-linux-gnu
checking host system type... arm-none-eabi
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-none-eabi-strip... arm-none-eabi-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking how to print strings... printf
checking for style of include used by make... GNU
checking for arm-none-eabi-gcc... arm-none-eabi-gcc
checking whether the C compiler works... no
configure: error: in `/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6':
configure: error: C compiler cannot create executables
See `config.log' for more details

Attaching config.log for more details.

I ran  sudo sh ./configure --host=arm-none-eabi CC=gcc It built for intel processor. With this when I include generated .a in CCS than at linking it is generating following error.
fatal error #10178: attempt to link an object file that is not built for Advanced RISC Machines ARM ("/usr/local/lib/libwolfssl.a<src_libwolfssl_la-ssl.o>" = Intel 80386)

Have anyone encounered this kind of issue on any other ARM processor?
I also tried WolfSSL 3.6.6 instead of CyaSSL 3.3.0. But still results are same. Log attached is for WolfSSL3.6.6

Thanks,
Bhavesh

Hi BKPatel,

Here is what I have done so far:

Try:

arm-none-eabi-gcc --version

If it is not found do the following:

sudo apt-get install gcc-arm-none-eabi
sudo apt-get install libnewlib-arm-none-eabi

cd into wolfssl directory.
Edit

wolfssl/wolfcrypt/settings.h

by uncommenting

#define FREERTOS

and run the following:

./configure --host=arm-none-eabi C_EXTRA_FLAGS="-O3 -mthumb -mcpu=cortex-m4" LDFLAGS="-lc -lrdimon -specs=rdimon.specs" CC=arm-none-eabi-gcc-4.8.2 

(This assumes you are using cortex-m4, if the mcpu needs to be changed update it to your mcpu)

At this point you will need the project specific header files all in the relevant places. Which unfortunately I can not test as I don't have access to your project etc.

It is my hope that you can get it working from there. If you have any further questions please let us know.

Kind Regards,

Kaleb

I have changed src/ and wolfssl/ folders.
Attaching tar files for these two. Full library is excedding size of 10 MB so not able to updload it.
If possible how can full directory can be saved?

Changes made:

in settings.h:
- uncommented #define FREERTOS and #define WOLFSSL_LWIP. Without  WOLFSSL_LWIP it was giving sys/socket.h not found error at src/io.c:87:36.
- added LWIP folder from /lwip-1.4.1/src/include and changed path of include files.

Hi Kaleb,

Making changes for some of pre-processor I am able to build libwolfssl.la file.
But when I run command make install libwolfssl.lib I am getting following error:

`pvPortMallocinternal.c:'
(.keys.c:text+(.0x1808)text+: 0x362)undefined : reference undefined to reference `vPortFreeto '
`pvPortMallocsrc/'
.libskeys.c:/libwolfssl.a(.(src_libwolfssl_latext+-internal.o0x378))::  Inundefined  functionreference  `to FreeX509Name'`pvPortMalloc:
'
internal.c:keys.c:(.(.text+text+0x18d8)0x38a): : undefined undefined reference reference to to `vPortFree`pvPortMalloc'
'
src/keys.c:.libs(./libwolfssl.atext+(src_libwolfssl_la0x39c)-internal.o: ):undefined  Inreference  functionto  ``pvPortMallocFreeX509''
:
src/internal.c:.libs(./libwolfssl.atext+(src_libwolfssl_la0x1966)-keys.o: ):undefined keys.c:reference (.to text+`vPortFree0x3ae)'
: src/more .libsundefined /libwolfssl.areferences (src_libwolfssl_lato -internal.o`pvPortMalloc):' internal.c:follow
(.text+0x1fbc): more undefined references to `vPortFree' follow
src/.libs/libwolfssl.a(src_libwolfssl_lacollect2: error: ld returned 1 exit status
-io.o): In function `EmbedReceive':
io.c:(.text+0xa): undefined reference to `lwip_recv'
src/.libs/libwolfssl.a(src_libwolfssl_la-io.o): In function `EmbedSend':
io.c:(.text+0x7a): undefined reference to `lwip_send'
src/.libs/libwolfssl.a(src_libwolfssl_la-keys.o): In function `SetKeysSide':
keys.c:(.text+0x34e): undefined reference to `pvPortMalloc'
keys.c:(.text+0x362): undefined reference to `pvPortMalloc'
keys.c:(.text+0x378): undefined reference to `pvPortMalloc'
keys.c:(.text+0x38a): undefined reference to `pvPortMalloc'
keys.c:(.text+0x39c): undefined reference to `pvPortMalloc'
src/.libs/libwolfssl.a(src_libwolfssl_la-keys.o):keys.c:(.text+0x3ae): more undefined references to `pvPortMalloc' follow
collect2: error: ld returned 1 exit status
make[1]: *** [wolfcrypt/test/testwolfcrypt] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [wolfcrypt/benchmark/benchmark] Error 1
make[1]: Leaving directory `/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6'
make: *** [install] Error 2

I am not able to link .la file directly into CCS. Due to following error:

<Linking>
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 1: error #19027-D: invalid directive libwolfssl - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 2: error #19027-D: invalid directive Generated - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 4: error #19027-D: invalid directive Please - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 5: error #19027-D: invalid directive It - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 7: error #19027-D: invalid directive The - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 8: error #10045-D: illegal input character:  "'"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 10: error #19027-D: invalid directive Names - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 11: error #10045-D: illegal input character:  "'"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 13: error #19027-D: invalid directive The - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 14: error #10045-D: illegal input character:  "'"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 16: error #19027-D: invalid directive Linker - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 17: error #10045-D: illegal input character:  "'"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 19: error #19027-D: invalid directive Libraries - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 20: error #10045-D: illegal input character:  "'"
error #10008-D: cannot find file "c"
error #10008-D: cannot find file "rdimon"
error #10008-D: cannot find file "m'"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 22: error #19027-D: invalid directive Names - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 23: error #10045-D: illegal input character:  "'"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 25: error #19027-D: invalid directive Version - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 27: error #10043-D: expecting "";"" instead of "age"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 28: error #10043-D: expecting "";"" instead of "revision"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 30: error #19027-D: invalid directive Is - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 33: error #19027-D: invalid directive Should - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 36: error #19027-D: invalid directive Files - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 37: error #10045-D: illegal input character:  "'"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 38: error #10045-D: illegal input character:  "'"
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 40: error #19027-D: invalid directive Directory - ignored
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 41: error #10045-D: illegal input character:  "'"

undefined                 first referenced
  symbol                       in file     
---------                 ----------------
wolfSSL_CTX_new           ./eth_socket.obj
wolfSSL_Init              ./eth_socket.obj
wolfSSL_free              ./eth_socket.obj
wolfSSL_new               ./eth_socket.obj
wolfSSL_read              ./eth_socket.obj
wolfSSL_set_fd            ./eth_socket.obj
wolfTLSv1_2_client_method ./eth_socket.obj

error #10234-D: unresolved symbols remain
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 31: error #10104: undefined symbol "no" used in expression
"/media/bhavesh/F4F24186F2414DD4/tiNew/wolfssl-3.6.6/src/libwolfssl.la", line 34: error #10104: undefined symbol "no" used in expression
error #10010: errors encountered during linking; "Test_Project.out" not built

>> Compilation failure
gmake: *** [Test_Project.out] Error 1
gmake: Target `all' not remade because of errors.

So wolfssl.a file is required for linking.
Can you help me to sort out make install issue.
Attaching .la file if that can be helpful.

Thanks,
Bhavesh

Hi BKPatel,

Could you double check and ensure that by using "sudo ./configure" it is not restricting access to the resulting library IE making it sudo only?

If your autoconf and autoreconf are up to day there should be no need to tell it to read the configure script in shell (sudo sh). The only necessary commands should be as follows.

./autogen.sh
./configure <options here>
make
sudo make install

(We only have sudo here because default it targets /usr/local/lib which is restricted to sudo)
You can opt to do the following instead:

./configure <other options> --prefix=/home/user/my/custom/install/directory
make
make install

You can install the library where ever you want it so that it resides in a user accessible directory.
All of these options and more can be seen with

./configure --help

Kind Regards,

Kaleb