I have updated line 85 and reloaded the project. I now get the following error, there is no spaces in the path?

-

- USERNAME = AdamHeavens
-- THIS_USER = AdamHeavens
-- ************************************************************************************************
-- wolfssl component config:
-- ************************************************************************************************
-- Starting FIND_WOLFSSL_DIRECTORY
-- Found WOLFSSL_ROOT via Environment Variable:
-- CMAKE_CURRENT_SOURCE_DIR = .
-- CURRENT_SEARCH_DIR = D:/Projects/<PROJECTNAME>/components/wolfssl
-- Looking in D:/Projects/<PROJECTNAME>/components/wolfssl
-- Next CURRENT_SEARCH_DIR = D:/Projects/<PROJECTNAME>/components
-- Looking in D:/Projects/<PROJECTNAME>/components
-- Next CURRENT_SEARCH_DIR = D:/Projects/<PROJECTNAME>
-- Looking in D:/Projects/<PROJECTNAME>
-- Next CURRENT_SEARCH_DIR = D:/Projects
-- Looking in D:/Projects
-- Next CURRENT_SEARCH_DIR = D:/
-- Looking in D:/
-- Next CURRENT_SEARCH_DIR = D:/
-- NEW wolfssl directory not found.
CMake Error at components/wolfssl/CMakeLists.txt:176 (message):
  Could not find wolfssl in .

  Try setting WOLFSSL_ROOT environment variable or git clone.

Cheers

Adam

Hi Jim,

Can I check if I am missing any steps here, I have now imported the project to VS with VisualGDB. However I can't get the build to complete due to wolfSSL dependencies.

I have completed the following

Git clone wolfSSL to local folder
Ran the following wolfssl\IDE\Espressif\ESP-IDF> .\setup_win.bat C:\SysGCC\esp32\esp-idf\v5.1 which copies the files into the component directory in the ESP-IDF framework. This creates a user_seetings.h file in \wolfssl\IDE\Espressif\ESP-IDF>

Edited user_settings.h to include 
 
#define SINGLE_THREADED
#define HAVE_ECC
#define WOLFSSL_SMALL_STACK
#define WOLFSSL_ESPIDF
#define WOLFSSL_ESP32
#define OPENSSL_EXTRA
#define OPENSSL_ALL
#define HAVE_TLS_EXTENSIONS
#define HAVE_SUPPORTED_CURVES
#define HAVE_AESGCM

I then try to build the project in VS. Do I need to complete any other steps to get wolfSSL to build

Cheers

Adam

Hi,

We have moved the project to use the esp-idf framework rather then Arduino, have to say it was a great recommendation as the there is far greater control.

Is there any instructions for integrating wolfSSL into VSCode / PlatformIO with esp-idf or is it simply a matter of copying the same user-settings.h into the managed_components/wolfssl__wolfssl folder?

idf.py add-dependency "wolfssl/wolfssl^5.6.6-stable-update2-esp32"

Cheers

Adam

Hi gojimmypi,

Thanks for checking in, yes we certainly will. One of the reasons I am looking at wolfSSL is that we can tailor the SSL/TLS requirements per geographic region or client base.

That is great news and look I forward to using a later build as we keep getting some weird random build issues which is slowing down integration/testing.

For example

wolfssl/openssl/sha.h:73:25: error: conflicting declaration 'typedef WOLFSSL_SHA_CTX SHA_CTX'

Also had to implement custom rand generate block as the #error "you need to write an os specific wc_GenerateSeed() here" error returned. This is with the same user_settings.h as before.

    -DCUSTOM_RAND_GENERATE_BLOCK=custom_rand_generate_block

#include "helper/custom_rand.h"

#include <esp_system.h>

int custom_rand_generate_block(byte *output, word32 sz, WC_RNG *rng)
{

    word32 rand;
    while (sz > 0)
    {
        word32 len = sizeof(rand);
        if (sz < len)
            len = sz;
        /* Get one random 32-bit word from hw RNG */
        rand = esp_random();
        XMEMCPY(output, &rand, len);
        output += len;
        sz -= len;
    }

    return 0; // Return success (0) or appropriate error code
}

Admittedly we are in the process of porting from openssl to wolfSSL so may be us, but some of the weird build issues have been resolved by simply closing the IDE and re-opening.

So hopefully the latest supported version of wolfSSL will help resolve some of these integration issues.

Cheers

Adam

Thank you, I have updated the user_settings.h and added HAVE_AESGCM and this has enabled me to build the project. I can now proceed with testing the implementation.

Many thanks for your support

Cheers

Adam

Hi gojimmypi,

Thank you for taking the time to do this, very much appreciate the support. wolfSSL 5.5.4 now builds correctly in my project. That was just the steps I needed and gives me more of an insight into wolfSSL configuration.

Are there any plans to have an official version published by wolfSSL in the PlatformIO registry? Happy to help with that if I can.

If not I can directly integrate from the GitHub repo will just need to figure out how to build but I expect that is easier now I have the correct user_settings.h to use.

Looks like it would be worth the time as I can see some of the newer commits include enhanced support on the ESP32-S3.

Cheers

Adam

Thanks Eric,

Much appreciated.

We are in the process of porting some Certificate Management class' from openssl to wolfSSL due to the limited openssl support on the ESP32. This is being used to handle certificates as part of an EV Charge Point product. So we can implement Vehicle to Grid (V2G) support.

Cheers

Adam