AT Firmware Error

[Kurousagi]

I am having some difficulties. I tried to update the AT firmware with the firmware from Espressif's resource page. I think the firmware was successfully updated. I tried to update many different ways and the same error occurs. I downloaded the esp32-at git repo and used make flash, I used the latest ESPFlashDownloadTool_v3.6.4 (using both the individual bins and factory bin), and I even used esptool.py, writing the factory.bin file and I cannot access the ESP32-WROOM module through UART (IO16 and IO17). However, I can send an AT command through a UART connection on an Arduino compatible board and I get this message in return:

AT
ERR CODE:0x01030000

ERROR

and because I have a loop listening to the RX bus, I get this if I reset the module:

ready

I don't know what is going on. I am getting frustrated. I can't get a simple OK from the command AT.

[brian.wyld]

Hi

Did you get any fix for this issue? I have the same problem using latest (1.1.3) AT firmware direct from the ESP site...
---
ready
AT
^J

ERR CODE:0x010b0000

busy p...

OK
AT+GMR
^J+GMR

ERR CODE:0x010b0000

busy p...
AT version:1.1.3.0(5a40576 - Nov 28 2018 12:50:55)
SDK version:v3.0.7
compile time:Dec 21 2018 09:04:56
Bin version:1.1.3(WROOM-32)

OK
----

any fixes gratefully received

Brian

[Helen L]

The AT error code is in https://github.com/espressif/esp32-at/b ... e/esp_at.h

Code: Select all

typedef enum {
    ...
    ESP_AT_SUB_NO_AT                    = 0x03,              /*!<  not found AT or at or At or aT */
    ...
    ESP_AT_SUB_CMD_PROCESSING           = 0x0B,              /*!<  previous command is processing */
    ...
} esp_at_error_code;

`ERR CODE:0x01030000` is a little weird, it means not find "AT", will it be a hardware issue?

`ERR CODE:0x010b0000` means that the system is executing the previous AT command, cannot accept the next one for now.

[ESP_XCGuang]

If there are more characters after '\r\n', it will response 'busy p...'. Please check it.