1 Topic by dimax.main

(1 replies, posted in wolfSSL)

Hi,
I'm building with custom Makefile wolfssl library for STM32F2xx with FreeRTOS.
Library build passed OK but linking the final project with a libraty produce undefined references to _abort, _getpid and _sbrk.
I'm quite sure something is missing in configuration of the library. Please help...

Here is my user_settings.h

/*
*-------------------------------------------------------------------
* wolf SSL user_settings.h
*-------------------------------------------------------------------
*/
#ifndef USER_SETTINGS_H_INCLUDED
#define USER_SETTINGS_H_INCLUDED

/*
*-----------------------------------------------------------------------------
* wolfSSL options
*-----------------------------------------------------------------------------
*/
#define FREERTOS
#define WOLFSSL_STM32F2
#define USE_FAST_MATH
#define TFM_TIMING_RESISTANT

#define WOLFSSL_USER_IO
#define USER_TIME
#define USER_TICKS

#define STM32F2_RNG_COOLAUTOMATION
#define STM32F2_CRYPTO_COOLAUTOMATION

#define BUILD_TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
#define HAVE_DH
#define HAVE_AESGCM

//#define NO_AES
#define NO_FILESYSTEM
//#define NO_RABBIT (defined by WOLFSSL_STM32F2)
//#define NO_RSA
//#define NO_DSA (defined by FREERTOS)
//#define NO_DH
//#define NO_CERTS
#define NO_PWDBASED
#define NO_DES3
#define NO_MD4
#define NO_MD5
#define NO_ERROR_STRINGS
#define NO_OLD_TLS
#define NO_RC4
//#define NO_WRITEV (defined by FREERTOS)
//#define NO_SESSION_CACHE
//#define NO_DEV_RANDOM (defined by WOLFSSL_STM32F2)
//#define NO_WOLFSSL_SERVER ???
#define NO_PSK
#define NO_SHA
//#define NO_WOLFSSL_MEMORY ???
//#define NO_ASN
//#define NO_BIG_INT
//#define NO_CODING
//#define NO_HC128 (defined by FREERTOS)
//#define NO_INLINE ???
//#define NO_ASN_TIME

And this is an invocation of GCC:

Compiling file: ../wolfssl-3.9.10/src/ssl.c
C:/ARM_GCC/current/bin/arm-none-eabi-gcc -c -mcpu=cortex-m3 -mthumb -Os -Wall -Wstrict-prototypes -Wextra -Wformat=0 -std=gnu89 -fverbose-asm -nostdlib -funwind-tables -Wa,-ahlms=_output/ssl.lst -DWOLFSSL_USER_SETTINGS -I. -I../wolfssl-3.9.10/ -I../../STM32/lib/Core -I../../STM32/lib -I../../STM32/FreeRTOSv8.0.1/Source/include -I../../STM32/FreeRTOSv8.0.1/Source/portable/GCC/ARM_CM3 ../wolfssl-3.9.10/src/ssl.c -o _output/ssl.o

Go to forum: wolfSSL

2 Reply by dimax.main

(9 replies, posted in wolfSSL)

I get the same problem:

> ./client -h gmail.google.com -p 443 -d -g
err = -313, revcd alert fatal error
wolfSSL error: wolfSSL_connect failed

Go to forum: wolfSSL

3 Reply by dimax.main

(4 replies, posted in wolfSSL)

Thanks.
But I afraid you have not fully understand my question. I did see that wolfSSL can run over lwIP stack. But lwIP provides two different APIs. One is Berkley socket like API and another is proprietary lwIP netcon API.  My question was if netcon API is supported and if not where should I look at in wolfSSL to add a port for it.

Go to forum: wolfSSL

4 Topic by dimax.main

(4 replies, posted in wolfSSL)

Hi,
Just want to ask if WolfSSL can run over lwIP netcon API and not BSD Socket API ?

Thanks.

Go to forum: wolfSSL