Hello gabriel and thank you for your interest in wolfSSL.

It does appear that your local project component directory is correctly structured.

Without seeing your source code, it is difficult to say exactly what the root cause of the problem may be, but I do have some suggestions for you.

I started with the bare-bones Espressif template example here:

https://github.com/wolfSSL/wolfssl/tree … s/template

Using your example of  needing`wc_InitRsaKey()`, the `ed25519.h` file needs to be included.

The two most important things to remember:

1) `WOLFSSL_USER_SETTINGS` needs to be defined. See the first line in the `template/main/CMakeLists.txt`:

set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -DWOLFSSL_USER_SETTINGS")

2) It is important to include the wolfssl/wolfcrypt/settings.h files before any other wolfSSL includes.

#ifdef WOLFSSL_USER_SETTINGS
    #include <wolfssl/wolfcrypt/settings.h>
    #ifndef WOLFSSL_ESPIDF
        #warning "Problem with wolfSSL user_settings."
        #warning "Check components/wolfssl/include"
    #endif
    #include <wolfssl/wolfcrypt/port/Espressif/esp32-crypt.h>
#else
    /* Define WOLFSSL_USER_SETTINGS project wide for settings.h to include   */
    /* wolfSSL user settings in ./components/wolfssl/include/user_settings.h */
    #error "Missing WOLFSSL_USER_SETTINGS in CMakeLists or Makefile:\
    CFLAGS +=-DWOLFSSL_USER_SETTINGS"
#endif

#include <wolfssl/wolfcrypt/ed25519.h>

Then I added these two lines to `void app_main(void)` int `main.c`:

    ed25519_key key;
    wc_ed25519_init(&key);

I was able to confirm the template example would compile.

If you try these steps and the file still cannot be found, please reply with the CMake output, in particular the sections that include the `WOLFSSL_ROOT` keyword. Ensure you are using a recent CMakeLists.txt, such as the one on the example template `components/wolfssl` directory. There should be something like this in the log:

-- Starting FIND_WOLFSSL_DIRECTORY: 
-- The WOLFSSL_ROOT environment variable is not set. Searching...
-- WOLFSSL_ROOT found in sdkconfig/KConfig: ~/workspace/wolfssl
-- CONFIG_CUSTOM_SETTING_WOLFSSL_ROOT sdkconfig setting = ~/workspace/wolfssl
-- WOLFSSL_ROOT Variable defined, but source code not found: C:/Users/<user>/workspace/wolfssl
-- CMAKE_CURRENT_SOURCE_DIR = .

After the lines of search, there should be an indication of the wolfSSL directory found:

-- Found wolfssl in CURRENT_SEARCH_DIR = C:/workspace/wolfssl-<user>
-- Found WOLFSSL_ROOT via CMake specification.

You may consider setting an environment variable `WOLFSSL_ROOT` that points your wolfSSL source code directory if your directory structure is such that wolfSSL is not in a parent directory from your project. Moving your project into the wolfSSL directory structure is also an option.

There's additional information and a link to a YouTube video on Getting Started with wolfSSL on the ESP32 here:

https://github.com/wolfSSL/wolfssl/tree … /Espressif

If these tips don't help, it would be great if you could supply a small reproducer app sample so I can further assist you.

Please let me know how it goes. Thank you.

Jim

Hi parmstrong3 - if you'd be able to get your workflow operational with the ESP-IDF, I suspect we could also get it  working with PlatformIO.

My personal skill set is certainly stronger with the ESP-IDF, but I'd be happy to do all I can to assist with your build process, particularly as a commercial customer. After you reach out to your contact, let's arrange a time for a call to discuss your specific needs.

Thank you for your interest in wolfSSL.

Jim

Hi Adam,

That's excellent! Glad we are making progress. Now onto the OpenSSL conversion:

Are you using the same user_settings.h that we were working with when you were using the PlatformIO environment:

https://github.com/gojimmypi/wolfssl/bl … settings.h

I'm able to add that to a sample project and build successfully. I assume the error you are seeing is occurring in your codebase, outside of wolfSSL? Any additional details would be helpful, although OpenSSL is not one of my specialties. I may need to reach out for additional help on that.

Best Regards,

Jim

Hi Adam -

Oh! An excellent find. Thank you for pointing that out. I'll get a PR together right away to fix it.

TL;DR: There's a mistake in the component cmake file:

 [project]/components/wolfssl/CMakeLists.txt

Change line 85 of the template CMakeLists.txt file:

https://github.com/wolfSSL/wolfssl/blob … ts.txt#L85

Specifically: replace the

if("${FOUND_WOLFSSL}")

with:

if( FOUND_WOLFSSL )

In more detail, Here's what I did:

In my C:\test directory, I created an "Adam" directory, and cloned wolfSSL into it:

c:\test\adam\wolfssl

Also in my C:\test directory, I created a "MyProject" directory: 

c:\test\myproject.

(for now, let's make sure there are no spaces in any of the paths)

I copied the contents of the sample template project:

C:\test\adam\wolfssl\IDE\Espressif\ESP-IDF\examples\template 

to the c:\test\myproject directory.

There should now be a VisualGDB directory, here:

C:\test\myproject\VisualGDB

I used the system control panel applet to set the environment variables:

Variable Name:
WOLFSSL_ROOT

Variable Value:
C:\test\adam\wolfssl

make sure there are no embedded spaces, particularly if using commandline:

WOLFSSL_ROOT=C:\test\adam\wolfssl

Open the VisualGDB project:

C:\test\myproject\VisualGDB\wolfssl_template_IDF_v5.1_ESP32.vgdbproj

(observe error at project load time)

Edit the cmake file as described above.

C:\test\myproject\components\wolfssl\CMakeLists.txt

Right click and reload the project. All should be well now.

Please give that a try and let me know how it goes.

My sincere apologies for this problem. Best Regards.

Jim

edit: I've created GitHub issue 7148 to fix this.

https://github.com/wolfSSL/wolfssl/pull/7148

Hi Adam -

Good to hear about your progress and continued interest!

At the moment, I don't yet have any good instructions for VS Code & PlatformIO. But I do have a major update in the works to publish an official wolfSSL to both Ardiuno and PlatformIO sites, along with improved Arduino examples. Stay tuned.

Would you happen to be using Windows? If so, I highly recommend the VisualGDB extension for Visual Studio. I've found it to be an incredibly productive development environment tool. Couple that with the Tigard JTAG board and there's an excellent ESP32 debugger for single step, breakpoints, variable inspection, memory & register peeking and more.

I gave a YouTube webinar last year on this topic that you may find helpful:

https://www.youtube.com/watch?v=CzwA3ZBZBZ8

Although the ESP Registry is awesome for getting started, it is not as robust as I want for ongoing development. I need to further develop the KConfig to make changes via the ESP-IDF menuconfig, as otherwise the user_settings.h file in a managed component cannot be edited.

There are some Espressif examples to help get started with the ESP-IDF here:

https://github.com/wolfSSL/wolfssl/tree … F/examples

Note in particular that wolfSSL does not need to be installed in the local project. See the CMakeLists.txt file in components/wolfssl directory.

The user_settings.h is then found in this directory:

[your project]/components/wolfssl/include

As you move forward, please note that wolfSSL offers special pre-sales support to help get your project kickstarted.

Cheers

Jim

Hi Adam -

How's your evaluation coming along? Will you have any customers in China? One of the things to consider is wolfSSL SM Chinese ShangMi support:

https://www.wolfssl.com/wolfssl-adds-sh … wolfcrypt/

I have that working for the ESP32, but the samples need just a little fine tuning with regards to the static sample certs.

Heads up I received approval to work on an official wolfssl repository for PlatformIO.

Status will be tracked at GitHub issue #85 for platformio/platformio-registry here:

https://github.com/platformio/platformi … /issues/85

I need to wrap up a few other items before I get started on that, but in the meantime please let me know if there's anything else I can do to help you.

Cheers

Hi Adam -

That's excellent you've made progress!

I suggest putting them in the `user_settings.h` instead:

#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

I've updated my sample `user_settings.h` here:

https://github.com/gojimmypi/wolfssl/bl … ings.h#L39

The library for wolfSSL is highly tunable. See the documentation for details on the options available:

https://www.wolfssl.com/documentation/m … ave_aesgcm

One possible solution to the error you are seeing is to turn on AESGCM in `user_settings.h` like this:

#define HAVE_AESGCM

Please let me know if that works for you.

Cheers!

Hi Adam -

I'm not familiar with the PlatformIO method of building a project. I definitely recommend using the ESP-IDF if at all possible. There are wolfSSL examples here:

https://github.com/wolfSSL/wolfssl/tree … /Espressif

There's also the capability of using Managed Components from the ESP Registry:

https://www.wolfssl.com/wolfssl-now-ava … -registry/

That said, I do think the Arduino projects should at least work. If there's no mechanism for including or excluding files in PlatformIO, there's always the brute force method of simply deleting all the files you don't want to be included (e.g. all the assembly language suffix "*.s" files in wolfcrypt/src)

Additionally, it's really best to use a wolfssl `user_settings.h` file. It gets included by pretty much every wolfssl source file (via wolfcrypt/settings.h) & controls which features are compiled in - such as your missing wc_GenerateSeed().

I suppose it should in theory also work to add "-D" build flags. See the example template user_settings.h:

https://github.com/wolfSSL/wolfssl/blob … settings.h

In particular, you will at least need `-DWOLFSSL_ESPIDF` and `-DWOLFSSL_ESP32` defined project-wide.

If you choose to use the user_settings.h file, I'd probably drop it in place with settings.h in wolfssl/wolfcrypt. When using the ESP-IDF instead, the file belongs in the components/wolfssl/include directory.

If you choose to use the ESP-IDF (you can still edit with VS Code) - I'll be able to help you much more. I'd still like to get the PlatformIO working, but I'll need to spend some time on that. If you can point to your example online, or something similar, that would be helpful to get me started.

Cheers