gojimmypi

I believe I have all build issue resolved. The last problematic one was needing to add the `!defined(WOLFCRYPT_ONLY)` for the new `ShowExtendedSystemInfo` in `test.c`: ``` #if defined(HAVE_VERSION_EXTENDED_INFO) && !defined(WOLFCRYPT_ONLY) ShowExtendedSystemInfo();...

This PR will be mothballed for the time being. I've [moved](https://github.com/gojimmypi/wolfssl/commit/1a4a6a5ae6c3381a278b4c8b251ad5e63b9db3a6) the `ShowExtendedSystemInfo()` to the [wolfcrypt/src/port/Espressif/esp32_util.c](https://github.com/gojimmypi/wolfssl/blob/ED25519_SHA2_fix/wolfcrypt/src/port/Espressif/esp32_util.c) The functionality can still be used in [main.c](https://github.com/gojimmypi/wolfssl/blob/1a4a6a5ae6c3381a278b4c8b251ad5e63b9db3a6/IDE/Espressif/ESP-IDF/examples/wolfssl_benchmark/main/main.c#L194) Espressif code like this: ``` #ifdef...

We decided not to implement the extended version information in `version.c` at this time. There is however some extended information in the [esp32_util.c](https://github.com/wolfSSL/wolfssl/blob/master/wolfcrypt/src/port/Espressif/esp32_util.c) for the Espressif embedded target. Closing this...

As this issue is so specific to Espressif HW acceleration values, I'm pulling the PR as draft and will reconsider making changes to the [hardware acceleration code](https://github.com/wolfSSL/wolfssl/tree/master/wolfcrypt/src/port/Espressif) instead.

I'm closing this issue as I believe it is an irrelevant corner case.

There's a [WiFi networking example](https://github.com/espressif/esp-idf/blob/master/examples/wifi/getting_started/station/main/station_example_main.c) in the [Espressif ESP-IDF repo](https://github.com/espressif/esp-idf/) that may help. See also the [docs](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/network/esp_wifi.html).

Hi @dgarske and @JacobBarthelmeh - just wondering what's the status of this PR? I see there's a useful [DEBUG_PRINTF](https://github.com/JacobBarthelmeh/wolfTPM/blob/fc5ff50a799c8ac5154303748694e5c471ae4449/src/tpm2.c#L78) proposed. I almost when down a similar path, but ended up...

@JacobBarthelmeh I hear ya on the `goto`'s. I too, have mixed feeling about using them. It can be acceptable if used properly. @dgarske has quite a few instances of the...

Yes, that's appropriate, thanks. In any case, it is not working for me: `lsusb` returns an error code = 1 and no devices at all listed. That command used to...

Hello @ncmiller and thank you for the prompt reply! > I don't think there's anything in the Golioth code using those pins ... and you are right. those code segments...