CIPCLOSE Issue

[SL!M]

Hi, there is a bug in the CIPCLOSE command in the latest update, to replicate:

1- set mode as AP and multi connection mode.
2- start a TCP server connection at port 80.
3- connect to the AP, and browse the the ESP ip: 192.168.4.1, you will see the HTTP request.
4- you will get an error when you try to disconnect(AT+CIPCLOSE=0), and the chip will reboot.

[ESP_Faye]

Hi,

Sorry that you have this problem , but we can not replicate it..
Our test steps are as follows:
"
AT+CWMODE=2

OK
AT+CWSAP="qwerty","123456789"

ERROR
AT+CWSAP="qwerty","123456789",5,3

OK
AT+CIPSERVER=1,80

ERROR
AT+CIPMUX=1

OK
AT+CIPSERVER=1,80

OK
0,CONNECT

+IPD,0,364:GET / HTTP/1.1
Host: 192.168.4.1
Connection: keep-alive
Cache-Control: max-age=0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
Accept-Encoding: gzip, deflate, sdch
Accept-Language: zh-CN,zh;q=0.8

AT+CIPCLOSE=0
0,CLOSED

OK
"
Could you offer us more information, like UART output logs ?

[SL!M]

Hi Faye, here is my log:
Thanks

AT+GMR<CR><LF>

AT+GMR<CR>
<CR><LF>
AT version:0.21.0.0<CR><LF>
SDK version:0.9.5<CR><LF>
<CR><LF>
OK<CR><LF>

AT+CIPMUX=1<CR><LF>

AT+CIPMUX=1<CR>
<CR><LF>
<CR><LF>
OK<CR><LF>

AT+CWMODE=2<CR><LF>

AT+CWMODE=2<CR>
<CR><LF>
<CR><LF>
OK<CR><LF>

AT+CIPSERVER=1,80<CR><LF>

AT+CIPSERVER=1,80<CR>
<CR><LF>
<CR><LF>
OK<CR><LF>

0,CONNECT<CR><LF>
1,CONNECT<CR><LF>

AT+CIPCLOSE=0<CR><LF>

AT+CIPCLOSE=0<CR>
<CR><LF>
<CR><LF>
+IPD,1,359:GET / HTTP/1.1<CR><LF>
Host: 192.168.4.1<CR><LF>
Connection: keep-alive<CR><LF>
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8<CR><LF>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.93 Safari/537.36<CR><LF>
Accept-Encoding: gzip, deflate, sdch<CR><LF>
Accept-Language: en-US,en;q=0.8,zh-CN;q=0.6,zh;q=0.4<CR><LF>
<CR><LF>
0,CONNECT FAIL<CR><LF>
<CR><LF>
OK<CR><LF>

<CR><LF>
ets Jan 8 2013,rst cause:4, boot mode:(3,0)<CR><LF>
<CR><LF>
wdt reset<CR><LF>
load 0x40100000, len 612, room 16 <CR><LF>
tail 4<CR><LF>
chksum 0x12<CR><LF>
load 0x3ffe8000, len 788, room 4 <CR><LF>
tail 0<CR><LF>
chksum 0x50<CR><LF>
load 0x3ffe8314, len 264, room 8 <CR><LF>
tail 0<CR><LF>
chksum 0x4a<CR><LF>
csum 0x4a<CR><LF>
<CR><LF>
2nd boot version : 1.1<CR><LF>
SPI Speed : 40MHz<CR><LF>
SPI Mode : QIO<CR><LF>
SPI Flash Size : 4Mbit<CR><LF>
jump to run user1<CR><LF>
<CR><LF>

rlNÿ<CR><LF>
?ready<CR><LF>

[SL!M]

The previous version didn't have this problem... and this problem happens ONLY on port 80. If you try to connect from any tcp client to port 80 and you send CIPCLOSE command you will get 0,CONNECT FAIL and the chip will reset.

[ESP_Faye]

Hi,

Thanks for bug reporting !

Please try it with the attachment bin files, and feel free to let us know if you have any question ~

[pa.gregor]

Hi,

Thanks for bug reporting !

Please try it with the attachment bin files, and feel free to let us know if you have any question ~

Hello,
thanks for help, but firmware with this files not work.
After i upgrade firmware module not communicate.
After reset i recived packet with rubbish on serial port.
if i send at command module not replay.
With other firmware module work (ok... with the bugs... )


THX
Greg

[ESP_Faye]

Hi,

Thanks for your interest in ESP8266 !

The AT bin we released can works fine , baudrate is 115200 , AT commands end with CR LF

Please download as picture below.

download_tool.png (44.15 KiB) Viewed 27557 times

[pa.gregor]

Hi,

Thanks for your interest in ESP8266 !

The AT bin we released can works fine , baudrate is 115200 , AT commands end with CR LF

Please download as picture below.

download_tool.png

hello,
thx for info.
I make mistake with offset.
After upload firmwa esp work.

Br
Greg

[SL!M]

Hi,

Thanks for bug reporting !

Please try it with the attachment bin files, and feel free to let us know if you have any question ~

I tested the attached firmware and the bug is not fixed, still getting the same "0,CONNECT FAIL" and reboot after CIPCLOSE command... I'm sure its flashed correctly "AT version:0.22.b1.0"
anyone else tested the firmware?
Regards,
Ali

[jyke]

Hi,

Thanks for this correction it helped a lot...

i found next issue that happens randomly:
When sending message it looks like second message send fails all the time. So my esp listens tcp port 80 and responds with html message when client connect:

Arduino AT commeand Dubug:

Data available:
0,2 Client connected

AT+CIPSEND=0,64 Sending Firts message
HTTP/1.1 200 OK
Content-Type: text/html
Connection : close

TRUE (TRUE) Message send success
AT+CIPSEND=0,19 [b][i]Sending second message[/i][/b]
<body>
<h1>Hello :TRUE (TRUE) Sending success
AT+CIPSEND=0,70 Sending third message
6</h1><h2> World!</h2><button type="submit" value="LED1">LED1</button>TRUE (TRUE) Sending success
AT+CIPSEND=0,59
<button type="submit" value="LED2">LED2</button>
</body>
TRUE Sending success
AT+CIPCLOSE=0
TRUE


Telnet Client:


HTTP/1.1 200 OK
Content-Type: text/html
Connection : close

Location of missing second message
6</h1><h2> World!</h2><button type="submit" value="LED1">LED1</button><button ty
pe="submit" value="LED2">LED2</button>
</body>

br,
Jyke