bloaty VS esp-idf

ESP32s aren't really ‘lower level’ in the sense that anyone is likely to write assembly code for them (compared to, say, 8051 or PIC), other than maybe some driver author at Espressif. The big win from using RISC-V, other than name recognition, is mainstream compiler support (which is nothing to sneeze at, especially when it's largely funded by someone else).

When I worked on Matter¹, the Xtensa and RISC-V versions were basically fungible from the software point of view. (And really, so were other vendors' various ARMs.) We did find that Bloaty McBloatface² didn't support Xtensa, so I had to write an alternative.

¹ https://github.com/project-chip/connectedhomeip/

² https://github.com/google/bloaty

I’ve gotten good insight into what takes up space in binaries by profiling with Bloaty (https://github.com/google/bloaty). My last profiling session showed that clang’s ThinLTO was inlining too aggressively in some cases, causing functions that should be tiny to be 75 kB+.

I'm surprised they didn't go for the binary size analysis tools like

https://github.com/google/bloaty

Or goweight.

I was able to shave a few % off our app binary with Bloaty. It’s pretty hard to use but once you figure out how to make regular expressions to properly classify things from your codebase, you can really visually analyze what your binary is composed of.

Bloaty

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?