ESP32 Forum

Hi, I'm currently trying to make AT commands work on a DevKit v1 board. I know it's not an official ESP32 board produced by espressif, but it shares the WROOM-32 chip and I assumed I wouldn't have too many problems making things work out.

I tried flashing the WROOM-32 AT firmware and, after toying with pins for a bit, I still have some issues. I also tried downloading the firmware from the official GitHub repository, toying around with the configuration, but still came up empty. The UART communication appears to work: after pressing the EN button, I see the board information being printed out correctly, and on the AT interface a "ready" appears. However, whenever I try sending AT commands, the board doesn't seem to respond in any way. I'm aware the pinout is different from the built-in configuration options, but even setting the AT interface to overlap with the debug interface didn't seem to affect the core issue. I'm reading and sending commands from an Ubuntu 20.04 system using minicom, but I've also tried doing the same from a board running a Buildroot system with the same outcome.

Where could I go from here? Is there someone who managed to make it work?

Hi, could you please compile the AT firmware in your PC and see what happen from AT log port (GPIO1).

Use latest master branch and enable more logs to see what happened:
Compile guide: https://docs.espressif.com/projects/esp ... ect-config

in the step 5, configurate the following options:
python build.py menuconfig -> Component config -> Log output -> Default log verbosity -> Debug
python build.py menuconfig -> Component config -> AT -> Enable ESP-AT Debug
(Disable BT to reduce bin size) python build.py menuconfig -> Component config -> Bluetooth -> Deselect

The AT log port output should give more logs.