esp-idf VS ElegantOTA

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?

As u/__deeetz__ pointed out, the esp32 already had a good OTA mechanism, and there are some libraries that simplify the whole process - probably one of the more popular ones is ElegantOTA: https://github.com/ayushsharma82/ElegantOTA If I understand what you're doing correctly, you'll really have just 2 layers, not 3 - one being your application (which effectively has the Kernel/OS compiled in), and then your scripting/LUA component. Technically the ESP32 also has a bootloader portion, but it's pretty uncommon to need to modify that in any way, so I would highly recommend against doing that. As far as dealing with the LUA scripts - you can easily download and run those - you'll store them into NV ram, and I believe the current recommended format is LittleFS. Keep in mind that on a normal ESP32 configured to do OTA updates there's 4MB of storage, 2x 1.8MB for the two bootable images, and ~200k for the file system (in this case LittleFS). There are also other boards which come with more flash memory, like the new S3R8 has 16MB of flash, so your OTA partitions stay about the same in most cases, but you now have ~12MB of storage, which I suspect would be way beyond anything you'd need for storing LUA.

I'm looking for a small, thin example of the ESP32 hosting a webserver to accept firmware update files for OTA updates. There's a handful of Arduino libraries that do exactly this (e.g. https://github.com/ayushsharma82/ElegantOTA) but I haven't come across anything clean that's just built around IDF.