Dear all,
I am coming to you as I have a problem I cannot solve with the ESP32-S2-MINI1. I have flashed the protoboard with AT firmware. The flash has been process successfully regarding the logs coming from UART0.
I can also see that at boot, I receives from the ESP-UART1-TX the "ready" message. However, after this, the ESP does not answer any AT command, even the simplest such as "AT\r\n" sent on the ESP-UART1-RX. Note that nothing goes out of the RX line after the "ready". No "\r\nERROR\r\n" or thing like this.
I have tried the same command with an AT firmware on an ESP32-WROOM and it worked straight !
Someone already encountered this kind of problem or could help me with this ?
Than you very much,
Victorien.
ESP32-S2-MINI does not respond to AT commandqs
Re: ESP32-S2-MINI does not respond to AT commandqs
Could you tell me which AT firmware you download?
You could receive the "ready" for from AT UART TX , but you sended AT commands to device and no responses return. I think the problem is on the RX UART pin of the device. So my suggestion is check the AT UART RX pin, because the TX and Rx pins of each module are different.
If you are using ESP32-S2 v2.1.0.0, you can refer to https://github.com/espressif/esp-at/blo ... m_data.csv for uart_tx_pin field and uart_rx_pin field
You could receive the "ready" for from AT UART TX , but you sended AT commands to device and no responses return. I think the problem is on the RX UART pin of the device. So my suggestion is check the AT UART RX pin, because the TX and Rx pins of each module are different.
If you are using ESP32-S2 v2.1.0.0, you can refer to https://github.com/espressif/esp-at/blo ... m_data.csv for uart_tx_pin field and uart_rx_pin field
Re: ESP32-S2-MINI does not respond to AT commandqs
Sorry for the late answer.
The problem was indeed the pin assignment of the UART which was by default wrongly in the factory_param.csv file. I changed it to the correct pin according to documentation and it worked.
The problem was indeed the pin assignment of the UART which was by default wrongly in the factory_param.csv file. I changed it to the correct pin according to documentation and it worked.
Who is online
Users browsing this forum: No registered users and 35 guests