Search found 63 matches

by doughboy
Tue Apr 28, 2015 9:39 am
Forum: AT+ Commands
Topic: At v23 fails to boot on 512kB, fatal exception - RESOLVED
Replies: 24
Views: 22726

Re: At v23 fails to boot on 512kB, fatal exception

ok, my first test program, I got garbage for server ip. So apparently, this does not work anymore. this is what I get on cipsta, which I know is incorrect. +CIPSTA:ip:"108.48.114.52" +CIPSTA:gateway:"108.48.114.1" +CIPSTA:netmask:"255.255.255.0" and I also now get the c...
by doughboy
Tue Apr 28, 2015 9:34 am
Forum: AT+ Commands
Topic: At v23 fails to boot on 512kB, fatal exception - RESOLVED
Replies: 24
Views: 22726

Re: At v23 fails to boot on 512kB, fatal exception

I just tried it and it worked for me. I'm going to run my test programs to confirm . AT+CIPSTA? +CIPSTA:ip:"0.0.0.0" +CIPSTA:gateway:"0.0.0.0" +CIPSTA:netmask:"0.0.0.0" OK AT+CWMODE=1 OK AT+CIPMUX=1 OK AT+CWJAP="x","x" WIFI CONNECTED WIFI GOT IP OK A...
by doughboy
Tue Apr 28, 2015 8:54 am
Forum: AT+ Commands
Topic: At v23 fails to boot on 512kB, fatal exception - RESOLVED
Replies: 24
Views: 22726

Re: At v23 fails to boot on 512kB, fatal exception

I've never used 1.2 boot, can you try 1.3? If you are able to get AT to respond, enter command AT+CIPSTA? if you blanked user area, it will be all 0. if it is garbage, that means the firmware is reading the data where code is. After you connect to your router, AT+CIPSTA? should show your ip address,...
by doughboy
Tue Apr 28, 2015 12:09 am
Forum: AT+ Commands
Topic: At v23 fails to boot on 512kB, fatal exception - RESOLVED
Replies: 24
Views: 22726

Re: At v23 fails to boot on 512kB, fatal exception

try 0x00000 boot_v1.2 (or 1.3) 0x01000 user1.1024.new.bin 0x7e000 blank.bin make sure to select 8mbit even if your module is 4mbit. I found out if you select 4mbit, that setting is stored in firmware and firmware code will write to address 0x3E000, which contains firmware code. I have not actually t...
by doughboy
Mon Apr 27, 2015 12:53 pm
Forum: AT+ Commands
Topic: AT+CIPSENDxxx performance
Replies: 1
Views: 2398

AT+CIPSENDxxx performance

I did a load test using the different AT+CIPSEND commands, and this is what I found out. v1.0.1b2 using any of the CIPSEND command, I get 1.8tps (555ms) sending 2.5kb of data (one 2k and second .5k). using v1.0.1, CIPSEND and CIPSENDEX performance is reduced to half (transmit time DOUBLED!!!). CIPSE...
by doughboy
Mon Apr 27, 2015 11:08 am
Forum: AT+ Commands
Topic: SSL connection via AT commands
Replies: 15
Views: 19445

Re: SSL connection via AT commands

ok, thank you for the explanation. Do you think it is still possible to optimize the firmware code some more? v0.93SDK has no problem connecting using SSL to real websites like google and yahoo. There is a real world need to be able to connect to SSL server, particularly for sending email or connect...
by doughboy
Thu Apr 23, 2015 11:12 am
Forum: AT+ Commands
Topic: SSL connection via AT commands
Replies: 15
Views: 19445

Re: SSL connection via AT commands

The sample code has the call to espconn_secure_set_size commented out. I bet if you uncomment that and set size to 8192 and compile that with patched ssl library, you will also get wdt reset. I tried different values and if I set > 5k, espconn_secure_connect will wdt even connecting to iot.espressif...
by doughboy
Thu Apr 23, 2015 11:09 am
Forum: AT+ Commands
Topic: SSL connection via AT commands
Replies: 15
Views: 19445

Re: SSL connection via AT commands

ok, I tried one more time, using the patched SSL library, but this time, I removed the call to espconn_secure_set_size, and I am able to connect to iot.espressif.cn 8443, but not port 443.

So I'm pretty sure the bug is in espconn_secure_set method. It cause the module to wdt reset.
by doughboy
Thu Apr 23, 2015 10:55 am
Forum: AT+ Commands
Topic: SSL connection via AT commands
Replies: 15
Views: 19445

Re: SSL connection via AT commands

ok, some correction. Using exactly the same code, if I used the patched ssl, I get wdt reset. I was using the older libssl.a from 1.0sdk in my previous post. So there is something wrong with the patched ssl library. AT+CIPSTARTSSL="iot.espressif.cn",8443 host: iot.espressif.cn port:8443 Fr...
by doughboy
Thu Apr 23, 2015 10:33 am
Forum: AT+ Commands
Topic: SSL connection via AT commands
Replies: 15
Views: 19445

Re: SSL connection via AT commands

I looked at the sample, and it is similar to my current program. So I tried to connect to iot.espressif.cn port 8443 and I got a successful connection. But if I connect to iot.espressif.cn port 443, I get -11. I have already set the buffer to 8192. you need to make ssl api work with normal websites ...

Go to advanced search