Search results for:

I'm having some issues with TLS. I want to establish a client to request HTTPS uris.
However, after creating and signing and validating the keys I get an error as follows.

Wifi Connected
Connecting with TLS...
Loading the CA root certificate...
Loading the Client certificate...
Loading the Client Key...
Performing the SSL/TLS handshake...
Connecting with TLS...
ERROR: Unable to create socket
ERROR: Failed! mbedtls_ssl_handshake returned -0x1
Uncaught Error: CIPSTART failed (0,CLOSED)
 at line 1 col 52
throw Error("CIPSTART failed ("+(a?a:"Timeout")+")");
                                                   ^
in function called from system
 at line 1 col 52
throw Error("CIPSTART failed ("+(a?a:"Timeout")+")");
                                                   ^
in function called from system

I looked up the error -0x1 and I can't find anything specific for that error only codes with addtional alphanumeric chars appended.

Firmware is the bundled 1.87 that the Espruino Wifi came with. I'm inferring the Espruino Wifi does support TLS and HTTPs as the Pico does.

I think this would be very valuable. It's visual. Especially helpful on the peripheral side when looking at new stuff where the pin references might not be so familiar.

That's where I wanted to go with this.

https://github.com/olliephillips/esp-up

The flashing piece was a bit above my pay grade at the time. But it will configure the wifi, so you can then connect over telnet directly from the Espruino IDE

Can we save a wifi configuration, similar to how ESP8266 wifi.save() implementation works, so the board joins the network or acts as AP when powered up?

Mine arrived today. Very nice looking board. Finish is great.

Hey looks nice. Noticed the URI you've set up for the board above does not tally with the URI printed on the board itself.

I think so - but the news of this seems to have been and gone and nobody really cared. I guess it'll hit the news again when everything stops working though :)

More "punch drunk" than uncaring.. SEO moving goalposts, Google Reader retirement, various API deprecations, and now Chrome Apps.. It's what we've come to expect/accept.

If you can connect and upload over Wifi that's good. Odd that you have problems over serial. I haven't experienced it that way round.

wifi.save() is for setting up your wifi connection and storing so the board will join your network (or say act as an AP) when booted. For saving other programs it's save(). It won't be stored unless you save it.

Check out E.on("init",...) if you want that code to run when your board is restarted.

You should also check out this page http://www.espruino.com/Quick+Start

One final thing. If you're new to Espruino, you'll make better progress if you get a Pico or original Espruino. It will work out the box - and speed you up the curve. Plus you can test code on there before you move it to ESP8266.

Have you made certain IDE is set to 115200?

Are you saving the script, and having it load on board reboot? Depending on what you are loading that could lock you out. Maybe post the script you're sending over the IDE

Actually the connection should close and released after every request thus there should only one socket open at all

Yes. But not much headroom if things error and can't close. Have you made progress on this - I see you've posted to Gitter?

As I understand it socket errors on ESP8266 are commonly down to the fact you can only have so many open sockets. It's not many - I seem to think I've read 5. As for catching I don't know. If you slow down your poll rate does that help?

Maybe jump on the gitter.im/Espruino/espruino channel. There's people more familiar with this stuff on there.

Yes you can write to free flash check out the Flash module

http://www.espruino.com/Reference#Flash

How did you erase the flash?
What build of Espruino did you try to flash?
Do you have the Espruino Chrome IDE? Can you connect or use console (left pane) there @ baud 115200, using that?

Something like this

esptool.py --port /dev/tty.SLAB_USBtoUART --baud 460800 erase_flash

Note there is a different flashing command for smaller boards - 512k? Check the README_flash.txt included in the build's .tgz to make sure you're using the right command for your board.

Are you using esptool to flash? Maybe do "erase_flash" first. This will clear any saved javascript code. I understand that sometimes addresses of stuff change between builds so you can't guarantee that previously saved code will run. Wiping the board entirely with erase_flash usually sorts problems like this.

@Gordon that looks smart, and very small. I've been dipping in/out here, so apologies if I've missed it - what's the likely pricing for this board?

@allObjects :) You left a sitter for us to point out - 175% pledged and 75% time left

Looks great. So nearly bought a pack of Estimotes recently - glad I didn't - backed!!

Since you have ESPtool, and you've previously been using the ESP8266 for Arduino sketches, maybe use ESPtool's erase_flash command then flash again. The flashing command does not touch the area where Espruino saves programs, maybe there is some garbage in that memory area that is not helping. I generally wipe all my ESP8266 boards before flashing, whether I've used for Espruino or not.

In your first example you are using the js module which is intended for use when ESP8226 is purely used as Wifi Adapter - i.e Pico + ESP8266

Your second example is correct, and you can generally ignore module not found warnings.

The acid test is can you do anything with the wifi object - can you get status with wifi.getStatus()? If you can, your module is loaded and available.

Don't know TBH. I use an entry in hosts to avoid keying the IP, and I'm also aware that we have an ability to set a hostname (http://www.espruino.com/Reference#l_Wifi_setDHCPHostname) for the board when it is connected as a station to another Wifi network, but I think what you want there is a bridge too far. Two people that would know are @tve and @Gordon - maybe they can jump in.

I can't help with that. You'd need some sort of local DNS or hosts file equivalent to make that happen, actually residing on the ESP8266. I don't "think" we have anything like this.

@Ruprect99, your issue is the host/IP addressing, when ESP8266 is operating as Access Point and you are connected to it, the IP you need is 192.168.4.1

I don't have experience of the NodeMCU firmware programmer - maybe try gitter.im/espruino/Espruino, there are some Windows users on there I think who may be using.

Garbage/errors in left window/console can indicate a baud rate problem in the IDE - it should be 115200, but only time I could not key to console was a Mac OS problem so I can't be much help sorry. At least make sure you are set at 115200 in the IDE.

Also, you might want to try ESPtool.py. There are some example flash scripts you can run for the 512kb/4mb boards include in each archive. Makes flashing fairly straightforward, although I don't know if that is your issue here.