ESP8266 Not accepting any AT Commands anymore
Posted: Wed Jun 07, 2017 3:55 amDear all,
I have a solution with a Seeeduino Arch-Pro interfaced via UART to the ESP8266.
I have a fairly complex but reliable LWM2M Client running on the Arch-Pro which can run for days collecting data (basically 7 x ~100KB encrypted packets per seconds sent via AT+CIPSEND ...)
The issue is that sometimes the ESP module somehow doesn't accept anymore the AT+CIPSEND Command. My routine timeouts, the ESP8266 module is then resetted via the GPIO pin (driving to GND and back to VDD) and reconfigured.
At this point whatever error has happened into the ESP8266 I would expect to disappear due to the hard reset.
However what happens is that the module doesn't accept the ANY AT command anymore. The watchdog barks, my platform reboots and consequently also the ESP8266 is HW resetted at boot, but still no answer for any command.
Even if I manually reboot the platform nothing. The only solution is to manually unplug from VDD.
How could I solve this?
Apologies for the long explanation but I've been banging my head for quite a few time and never found a solution to this.
Thanks and Kind Regards,
Riccardo.
I have a solution with a Seeeduino Arch-Pro interfaced via UART to the ESP8266.
I have a fairly complex but reliable LWM2M Client running on the Arch-Pro which can run for days collecting data (basically 7 x ~100KB encrypted packets per seconds sent via AT+CIPSEND ...)
The issue is that sometimes the ESP module somehow doesn't accept anymore the AT+CIPSEND Command. My routine timeouts, the ESP8266 module is then resetted via the GPIO pin (driving to GND and back to VDD) and reconfigured.
At this point whatever error has happened into the ESP8266 I would expect to disappear due to the hard reset.
However what happens is that the module doesn't accept the ANY AT command anymore. The watchdog barks, my platform reboots and consequently also the ESP8266 is HW resetted at boot, but still no answer for any command.
Even if I manually reboot the platform nothing. The only solution is to manually unplug from VDD.
How could I solve this?
Apologies for the long explanation but I've been banging my head for quite a few time and never found a solution to this.
Thanks and Kind Regards,
Riccardo.