esp-idf VS wolfssl

For returning to deep sleep from the wake-up stub you can take a look at how it is done in https://github.com/espressif/esp-idf/tree/master/examples/system/deep_sleep_wake_stub

You can find the examples here: https://github.com/espressif/esp-idf/tree/master/examples

I found the spi_lcd_touch example and flashed it, and it seems to run fine with either ili9341 or gc9a01 drivers selected (although both are mirrored, and one has the colours inverted compared to the other - both of which I assume are things I can fix in either driver).

If that's the case: You register a GPIO as event source and make a task waiting for it, that then just performs the I2C-transaction. Follow this example https://github.com/espressif/esp-idf/blob/master/examples/peripherals/gpio/generic_gpio/main/gpio_example_main.c

IDF contains stuff like https://github.com/espressif/esp-idf/blob/master/pytest.ini and https://github.com/espressif/esp-idf/blob/master/tools/ci/idf_pytest/constants.py which are not part of the pytest-embedded package.

ugh.. arduino.

Better to start with ESP-IDF, there's a pretty full featured well documented web server, and a lot more.

https://github.com/espressif/esp-idf/tree/master/examples/pr...

i've looked over the the ble peripheiral example https://github.com/espressif/esp-idf/blob/master/examples/bluetooth/nimble/bleprph/README.md and i see it's using

Hi, I have device ESP32-S3-DevKitM-1 and i want to catch keystrokes from keyboard. I tried using this https://github.com/tanakamasayuki/EspUsbHost and example from espressif https://github.com/espressif/esp-idf/tree/release/v5.1/examples/peripherals/usb/host/hid/main but when i connect keyboard it is just connecting and disconnecting. Can anyone help me with this?

Or something a bit more lightweight - https://github.com/wolfSSL/wolfssl

> I have no room for TLS on micro computer

How micro is your micro? There are embedded TLS stacks such as wolfSSL[1]. If you carefully select the cipher suite and certificate requirements, and perhaps limit TLS payload sizes, you may be able to fit on a lot more systems than you initially suspect. x.509 is expensive in code space though, if that's the constraint, you may do better with an application specific certificate replacement of some sort.

[1] https://www.wolfssl.com/

There are many notable open-source projects (SSLyze, CipherScan, testssl.sh, tls-scan, …) and several SaaS solutions (CryptCheck, CypherCraft, Hardenize, ImmuniWeb, Mozilla Observatory, SSL Labs, …) to do a security setting analysis, especially when we are talking about TLS, which is the most common and popular cryptographic protocol. However, most of these tools heavily depend on one or more versions of one or more cryptographic protocol libraries, like GnuTLS, OpenSSL, or wolfSSL. But why is this such a problem?

wolfSSL 5.0.0