1 Reply by eduardogabaelbr

(6 replies, posted in wolfTPM)

Issue is fixed now. Packet was not available in STM CubeMx until I added by hand. Thanks a lot for support

Go to forum: wolfTPM

2 Reply by eduardogabaelbr

(6 replies, posted in wolfTPM)

When I select wolfSSL(wolfCrypt) enabled I only get wolfSSL.I-CUBE-wolfSSL_conf.h at the output,  wolfSSL.I-CUBE-wolfTPM_conf.h is not generated by CubeMX.

Regards
Eduardo

Go to forum: wolfTPM

3 Reply by eduardogabaelbr

(6 replies, posted in wolfTPM)

Yes, I generated the project for IAR using CubeMX. And using IAR Embedded Workbench The code compiles correctly. I´ve found that  STM32 generates the configuration file as wolfSSL.I-CUBE-wolfSSL_conf.h instead wolfSSL.I-CUBE-wolfTPM_conf.h, it cuases a compilation issue. Can you confirm and rename the configuration file in tpm2_types.h?
Regards
Eduardo

Go to forum: wolfTPM

4 Topic by eduardogabaelbr

(6 replies, posted in wolfTPM)

Hi, I´ve been integrating wolfTPM using an STM32H7 microcontroller using IAR compiler and Cmake, compiler found an issue when it tries to integrate tpm2_types.h header, this has a preprocessor defines, but USE_HAL_DRIVER seems to be not defined. but once I defined It causes a lot o compilation issues.

#if defined(USE_HAL_DRIVER) && !defined(HAVE_CONFIG_H)
    /* STM Configuration File (generated by CubeMX) */
    #include "wolfSSL.I-CUBE-wolfTPM_conf.h"
#elif !defined(WOLFTPM_USER_SETTINGS)
    /* use generated options.h or a custom one */
    #include <wolftpm/options.h>
#endif

I got next error cannot open source file "wolfssl/options.h". or how could I use the CMakeLists file to compile my project for a STM32H7 micro?

Go to forum: wolfTPM