Thanks for your interest, from a hardware viewpoint we preferred the ESP32-S2/3 architecture for 2 main reasons: greater GPIO availability and native USB support, moreover the rich integrated FLASH/PSRAM is an extra. Then, from a software viewpoint we chose ESP32-S2 among the two because of the curr...

Thanks for having read my (a bit off-topic) final note about the availability of an ESP-IDF framework upgrade (beyond v.5.0.x) for ESP-AT and the availability of a guide for compiling ESP-AT on every EspressIf SOC, given the importance of this application and the lack of a complete coverage. I had a...

I have a question for the ESP-AT developers. I would to perform the following: 1) activate support for a SPI ethernet module to ESP-AT (assigning 5 pins: SI,SO,CK,CS1,INT) 2) share the same SPI with another chip, driven by my custom AT commands (assigning 5 pins: SI,SO,CK,CS2,INT) As you can see, SI...

I solved it myself. As it can be seen on the standard error output, the problem occurred due to the usage of a wrong version for ESP-IDF (v5.3) with ESP-AT instead of the correctly referenced v5.0; that happend because - in the attempt of saving some disk space - I had just deleted the older framewo...

Hi everybody, I've just cloned the ESP-AT repository on my local machine, executed 'build.py install' (both without any error) but cannot execute the next 'build.py build' due to a fatal error. Here is the standard error output of cmake, clearly showing the error point: esp-at branch: master esp-at ...