Hello Kaleb:

Thanks for looking into this.

I now included #define SINGLE_THREADED and also created a project level #define WOLFSSL_LWIP but I still get the same "Conflicting types Aes" error.

(in my previous post I said including SINGLE_THREADED the project compiled, but I was including a function that call the wolfssl stack so the error was still there...).

If I don't include WOLFSSL_LWIP I get additional errors...

It seems Atmel port handles this issue as in wolfssl/wolfcrypt/src/port/atmel/atmel.c these lines remap those structures;

#include <wolfssl/wolfcrypt/settings.h>

#ifdef WOLFSSL_ATMEL

#include <wolfssl/wolfcrypt/memory.h>
#include <wolfssl/wolfcrypt/error-crypt.h>
#include <wolfssl/ssl.h>
#include <wolfssl/internal.h>

#define Aes Aes_Remap
#define Gmac Gmac_Remap
#include "asf.h"
#undef Aes
#undef Gmac

#include <wolfssl/wolfcrypt/port/atmel/atmel.h>

static bool mAtcaInitDone = 0;

#ifdef WOLFSSL_ATECC508A

/* List of available key slots */

.......

but it still fails...

I would appreciate any guide on this.

Thanks

Gus

Hi gussabina,

I never heard back from you so here is my educated guess of what is occurring. You stated the ATSAM4E has AES hardware crypto engine available so I bet the headers for that device have API's that provide access to that crypto engine (and also an Aes Structure definition that you are getting a conflict with). You would need to reference one of our existing pre-processor macros where we have added hardware support for other devices. One good one would be

STM32F2_CRYPTO

.

By referencing that macro and where it is used throughout the wolfCrypt sources, as it pertains to AES, you will get a good idea of the sections of the library that will need to be updated for your porting effort.

Let me know if this helps.

Warm Regards,

Kaleb