Linux: Yeah I've never had a problem with it.....
Latest Version: Ok Sorry about that I thought I downloaded the right version..... anyways downloaded from the link and.......
ESP8266 version check is
AT version:0.25.0.0(Jun 12 2015 20:26:28)\r\nSDK version:1.1.2\r\ncompile time:Jun 17 2015 22:11:51
now we have:
Connecting to Google
Connecting with TLS...
Loading the CA root certificate...
Loading the Client certificate...
Loading the Client Key...
Performing the SSL/TLS handshake...
ERROR: Failed! mbedtls_ssl_handshake returned -0x4290
ERROR: Failed! mbedtls_ssl_handshake returned -0x4290
and
ERROR: Failed! mbedtls_ssl_handshake returned Not enough memory
ERROR: Failed! mbedtls_ssl_handshake returned -0x4290
Right now I am really busy trying to understand exactly how this communication works. Do we really need the cert and key? I have a test client through NodeJs and it is sending fine with one of their known "root" CAs. I think these are them.
Much thanks for your help @Gordon. This is really going to do well for me once we get this figured out.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Linux: Yeah I've never had a problem with it.....
Latest Version: Ok Sorry about that I thought I downloaded the right version..... anyways downloaded from the link and.......
ESP8266 version check is
now we have:
and
Right now I am really busy trying to understand exactly how this communication works. Do we really need the cert and key? I have a test client through NodeJs and it is sending fine with one of their known "root" CAs. I think these are them.
Much thanks for your help @Gordon. This is really going to do well for me once we get this figured out.