Bug in FW ESP8266_NO_OS_KRAK

edison_cz
Posts: 1
Joined: Fri Nov 24, 2017 9:29 pm

Bug in FW ESP8266_NO_OS_KRAK

Postby edison_cz » Fri Nov 24, 2017 10:28 pm

Dear community,

recently I upgraded to KRAK patch (AT version:1.5.0.0(Oct 24 2017 12:03:18)
SDK version:2.1.0(ace2d95)
compile time:Oct 24 2017 15:48:02
Bin version(Wroom 02):1.5.1)

and have issue with server mode and IE11. The (shortened) sequence follows:

> AT+CWJAP
> AT+CIPSERVER=1,80
< 0,CONNECT
< +IPD: xxx
> AT+CIPSENDBUF=0,2048 ...
< 0,SEND OK
> AT+CIPSENDBUF=0,2048 ...
< 0,SEND OK
> AT+CIPSENDBUF=0,2048 ...
...
< 0,SEND OK
< 0,CLOSED

The following connection proceeds with error:

< 0,CONNECT
< +IPD: xxx
< 1,CONNECT
< +IPD: xxx

and very quickly follows

< 0:CONNECT FAIL
< 1:CONNECT FAIL
< 0:CONNECT
< 1:CONNECT

several times. After some time (seconds, far below timeout), the 0,CONNECT reports successful connection, but
AT+CIPSENDBUF=0,2048
never confirms reception ready with '>'.

Even if the connection times out after 30 seconds and IE11 requests another packet, the AT+CIPSENDBUF doesn't get the ESP '>' response.

In Chrome, where the x,CONNECT FAIL doesn't happen, the multi-threaded server responds correctly.

So, my 2 questions: what x,CONNECT FAIL means in server mode and why ESP8266 stops listening to AT commands (at least to AT+CIPSENDBUF)?

Thank you!

Tomas

ESP_Faye
Posts: 1632
Joined: Mon Oct 27, 2014 11:08 am

Re: Bug in FW ESP8266_NO_OS_KRAK

Postby ESP_Faye » Wed Nov 29, 2017 10:32 am

Hi,

x,CONNECT FAIL means the connection fail to be established.

Could you provide the entire test steps so that we can test it exactly as your way to reproduce your problem?

And could you capture the packets by wireshark for debugging?

Thanks for your interest in ESP8266!

Who is online

Users browsing this forum: No registered users and 3 guests