Espruino JavaScript
Pico and ESP8266 #5135
Replies: 1 comment
-
|
Posted at 2015-05-02 by DrAzzy ESP8266 is supported in all builds since I think 75? It's done via networkjs instead of a custom build that has the driver written in C. What is all the code you're using? Does it always fail like that? Sometimes I get that, but the next try, it'll work. Posted at 2015-05-02 by gnz I think since 76, at least the build that it shipped with (iirc was 75) was complaining about missing networkjs. Now I've 1v78. Test code is basically the same from the tutorial + some logging: I get this consistently, never works. I tried 3 different ESP8266 modules I have, and it's all the same. I tried 9600 and 115200 setup. In fact, I even tried disconnecting everything and I get the same error, so, something must be really wrong on my side I guess. Posted at 2015-05-02 by DrAzzy Did you put the cap across the supply? The available ESP8266 breakout boards don't have enough caps to work without adding caps. On the shim, I put a 47 uf 1210 cap on mine, and it works beautifully, didn't even connect without it. Posted at 2015-05-03 by gnz No capacitor, I'll get some tomorrow to try that. Thanks Posted at 2015-05-03 by DrAzzy Between Gnd and Vcc. Also - not sure what value capacitor you'll need. I'll try to play around with that later today and see if I can figure out how large a cap you need on it. I have a 0.1uf and a 1uf ceramic cap on an ESP8266 breakout board, and it seems to work fine. I guess I was being overly pessimistic when I went with a 47uf one on the shim. I would definitely use a ceramic cap, though. Posted at 2015-05-04 by gnz Thanks @drazzy! I'll play with it this week. Posted at 2015-05-05 by @gfwilliams Hi,
I guess one question is: Have you connected Posted at 2015-05-05 by DrAzzy Sometimes the ESP8266 responds to AT+RST with "ERROR" In that case, sending an AT+RST again seems to sort it out. Posted at 2015-05-05 by @gfwilliams
That usually happens if Espruino has been reset/restarted and there happened to be half a line of text already in the ESP8266's input buffer. Potentially it'd be fixed just by sending Posted at 2015-05-06 by gnz Still no luck. I added different capacitors, sometimes I see that when I plug it, the blue led turns on and stays, but as soon as I upload the sample js code which does One dumb question: I have the esp8266 in a breadboard, and it is wired to the Pico with jumperwires, no soldering anywhere. Could that be the cause? At some point I think I've read something about the proximity of capacitors affecting this, so I wonder if the fact that it's wired instead of soldiered in close proximity a problem. Keep in mind that I am absolute zero when it comes to electronics, so, try not to laugh too hard if this question is non-sense :) Posted at 2015-05-06 by DrAzzy The cap should be as close as possible to the ESP8266. Where and when did you get them? (wondering if they have the right firmware version - there are multiple mutually incompatible firmwares for the ESP8266) What we meant is whether you had the wires reversed, not the pin numbers in the code. I can't tell you how many times I've been certain I had TX/RX or SCL/SDA right, then reversed the connector, and found that I had them backwards. Usually what I see is the red light coming on, with no activity from the blue light until I start communicating with the ESP8266. Posted at 2015-05-06 by gnz I got them in February 8th from aliexpress (http://www.aliexpress.com/snapshot/6482384681.html). But, it does not matter: I think i just fried my Pico :( I was trying to re-write the thing for the 100th time, and I missed by one pin: wired vbat instead of 3.3, then the smell of burnt electronic followed and now can't detect the Pico anymore.... bad luck, I guess I'll just wait in line to buy new ones from the next batch! :P Posted at 2015-05-06 by gnz Btw, thanks for your help, guys!! Posted at 2015-05-07 by DrAzzy Shorting vbat to ground should only be able to destroy the fet or the diode (if running off BAT_IN or usb, respectively). The diode seems to be the first thing to go - luckily also probably the easiest part on the board to fix. I think Gordon said he was able to squeeze in a polyfuse in the next run of the pico, which will be great. Do be aware that USB ports get unhappy if too much current is drawn from them, and some won't work until the system is powercycled (I've also managed to kill one port on a hub apparently for good) Posted at 2015-05-07 by @gfwilliams Argh, that's a shame. Just to add that your Pico might not be totally dead. If you have a breadboard power supply or similar, try connecting it between the 'Bat' and 'GND' pins. The Pico may still be usable like that. Posted at 2015-05-09 by Schweigi The So to summarize:
What I saw until now is that the wifi module seems a bit unstable. I get random errors when connecting. For example:
Usually a reboot solved the issues and it works fine for some time. I will try to keep an eye on the issues. I think it may be related to the AT commands. Maybe the prior command is still in the command buffer of the ESP8266 after I restart the Pico. Posted at 2015-05-09 by DrAzzy SD card must be setup... is an uploading problem, where your code is trying to use a js module that hasn't been loaded (these get autoloaded when you reference them from the left side of the IDE and send to espruino. no change I think just indicates that it was already connected to that network. Make sure you are using latest version. Also, don't try to do multiple connections at a time - this is broken currently. Also, put a ceramic capacitor between power and ground right next to the ESP8266. 0.1uf wasn't enough, but 1 uf seemed to work. Posted at 2015-05-10 by Schweigi I didn't try the capacitor yet but I think most of the problems I wrote occurred because I loaded new code onto the Pico while a prior request was still running. Because once I stopped that the issues mostly disappeared. Posted at 2015-05-11 by hansamann I am also trying to make my pico work with the esp8266 right now. I get the errors above and after looking at the tutorial again I discovered CH_PD was not connected. I s this really not required for the pico ? The table cell is empty when using the pico, so many here would try not connecting CH_PD to 3.3V. Does it need to be connected? BTW it does not fix it. ... Still cannot make the code example work. Posted at 2015-05-11 by hansamann When CH_PD is connected, I strangely cannot make anythign work (pico). So I disconnected 3.3V from CH_PD again. Now I get this error, as described before (v1.78): Uncaught no 'ready' after at+rst.. how do I copy code from teh web ide??? Posted at 2015-05-11 by @gfwilliams
No, I'm pretty sure there's a pullup/down resistor internally.
Your code would have uploaded fine, this is the general error message you get if there is no communication with the ESP8266. Are you using an ESP8266 that came with the Espruino Pico KickStarter, or another one? ESP8266s all come with different firmwares which have different baud rates and subtly different AT command sets.
If you're getting other errors, please can you post up the exact ones? People have posted up a bunch of different errors here.
Copy it from the Web IDE? Just click and drag on the left-hand side. It'll automatically copy it to the clipboard. Posted at 2015-05-16 by Rene I've the same problem. there is an Error: I can't see any red or blue LED on the esp8266 board. Posted at 2015-05-16 by DrAzzy It takes the 3.3v supply from the pico - it's one of those 3 little pins on the side of the shim - make sure you soldered those. You need to put a ~1 uf+ cap between power and ground (there are pads for an SMD one on the shim), it seems like (at least in most cases) to get reliable operation. I've also found that sometimes it takes two tries to get AT+RST to work, if the ESP8266 isn't power cycled between attempts to use it. Posted at 2015-05-17 by Rene @drazzy that could be the right hint. Thx. Do I have to connect that middle pin to the esp8266 too ? Posted at 2015-05-17 by Rene yeah, connecting the middle pin (3.3V) solves the problem. Than the red LED is on and the blue LED flashes on wifi transmission. thanx to@drazzy Posted at 2015-05-18 by @gfwilliams Glad you got it sorted in the end!
The Video does tell you do do it, from 3 min 11 sec onwards: https://youtu.be/zqI_g-T0HP0?t=3m11s It's a shame I insert the wire offscreen, but maybe I could add some text to the video to explain what's being done. Posted at 2015-05-19 by cool_acid I've got the same problem. "No 'ready' after AT+RST". I got my pico from the kickstarter as well as the ESP8266 module. I can't get it to work. Blue led doesn't even light up. Posted at 2015-05-19 by @gfwilliams Do you get the red LED lit up on the ESP8266? And when you initially plug the board in, do you not get the blue LED flashing even momentarily? Posted at 2015-05-19 by Eric Got mine up and running after updating firmware. Works perfectly. Great video, thanks. What would be nice is some example http server code to compliment the client connect code. I am attempting to create a network of sensors controlled by a Raspberry Pi server. The Pi connects to the remote Pico's and issues commands to the listening pico's. These commands could be to retrieve values directly from the pins or to set pins to a state or call functions stored on the pico. Got a simple version working via the USB interface, but now I would like to wirelessly connect. Any help will be useful. Posted at 2015-05-19 by DrAzzy You can take a look at this: https://github.com/SpenceKonde/AzzyProjects/blob/master/ESPtest.js It was me messing around with a generic http server to run on a Pico w/ESP8266. You can uncomment that SD card stuff and it should serve stuff off the SD card, if you connect it as indicated. No warranty express or implied. Posted at 2015-05-19 by cool_acid The red LED is lit up all the time, but the blue one has never lit up. Posted at 2015-05-19 by DrAzzy It sounds like there was no communication between espruino and ESP8266. Did you get any errors after you sent the code? Whjat was printed to console? Blue light should start blinking when it runs the require("ESP8266WiFi").connect(...) line - how is it connected to the Espruino? Are you using the shim? Are you sure all the wires are connected well? Have you installed a 1uf (or more) capacitor next to the ESP8266 (there are pads on the shim for a smd one)? The ESP8266 modules seem to need one to function reliably. Posted at 2015-05-20 by cool_acid When I send the sample code I get this error: I'm using the shim, and I've checked a lot of times that all is connected where it is meant to be. I installed a 10uF cap in the shim. Posted at 2015-05-20 by Stevie @cool_acid: My ESP boards worked fine with the shim without any cap. Using the example. Except that the web server will get stuck if more than one request comes in at the same time. And of course the web client will get stuck after doing about 300 requests, most of the time. I have some auto-reset code catching that condition. None of that is the problem of the Pico, I am sure. The ESPs are notorious for these kinds of things. But more general, in my experience those ESP boards are divas. They are cheap in more than one way. Sometimes they just don't work. Mine won't work with anything else than the Pico. For whatever reason, I don't know. Power? TX lines too long? No idea. Maybe yours just does not work. Do you have a second one to try? Posted at 2015-05-20 by @gfwilliams @cool_acid, the blue LED lighting up randomly is strange... When it happens, please could you log back in, enter the line Please could you also check for shorts between pins A2 and A3 on Espruino (on the end of it) - that's about all I can think could be causing the random blue flashing... Posted at 2015-05-20 by @gfwilliams @eric to get a server, you just replace the The actual code should look a bit like this though: @stevie, yes the ESP8266 is a little unreliable as a server at the moment (I'm surprised about the 300 requests for a client though - I've left one going for days without problems). I'm hoping I can do something in the driver to make the server more reliable - but it may be that I have to come up with a way to update the firmware on the ESP8266... Posted at 2015-05-20 by Eric OK Thanks for the reply. I have just found Gordon's example of an interactive webpage http://www.espruino.com/Interactive+Web+UI which is exactly the sort of thing I was trying to do. On loading it just worked! This is so cool. Thanks again. Posted at 2015-05-20 by Eric Hello Gordon, I can't believe how helpful you have all been. DrAzzy and yourself have been great in responding so fast. Thank you for the trimmed down version it makes it perfectly clear now. One small question more I have is "Is it possible to take the wifi.getIP() function and make a request to a server passing the IP address as a part of the query string?" For example http://192.168.0.2/get_pico_ip.php?picoid=pico001&ip=192.168.0.171 So in other words, I have have my Pi listening out for requests from Pico's making connections to network. The request is an announcement what the IP address is of the Pico after connection. This get's logged as a dynamic IP and can then be used by the Pi server to remotely connect and make calls, set values etc just like in your interactive web page. If not, I would need to set up my router to issue the same IP address for the MAC ID following initial connection, which is OK, but a dynamic approach is better I think. Posted at 2015-05-20 by @gfwilliams Thanks! Well, as you're using PHP on the Pi, you can actually do But to do what you want on the Pico, you can do: Just in case it's helpful, there's also edit: just to add that this could be a bit more tricky because I'm not 100% sure you can have an HTTP server and a client at the same time on the ESP8266. You'd need to make sure you only started the server after the HTTP request closed. Posted at 2015-05-20 by Eric Thanks Gordon, It was actually the fact that you suggested in your guide that you are not able to have a server and client running at the same time that prompted the question. So, the php remote address is neat, I should of known that. But to stamp it to a unique ID (like the board SN) a client call would be needed first anyway. To make this work, I would call the function above first to establish the connection to the Pi / register with the Pi that the Pico exists and is available for communicating, then start the server and listen for commands. Sounds OK to me. Thanks for the tips, I will experiment... Posted at 2015-05-20 by Stevie @gfwilliams, I have tested it with 3 different modules, always the same. I stripped down to pretty much the example code, still had that. But I heard the same also from others. It is sufficient to reset the ESP to "heal" the problem, so I am pretty sure it is not Espruino. +1 for a way to update the firmware! Posted at 2015-05-21 by cool_acid Hey, guys! Thanks for all the help. I finally managed to make the ESP work. I ordered two modules with my kickstarter backing and I guess the first one that I soldered is damaged or something. When I tried with the other one, it worked like a charm the first time. Posted at 2015-05-21 by DrAzzy Have you seen the protoboard I'm working on? http://forum.espruino.com/conversations/265026/?offset=50 Posted at 2015-05-28 by Eric Has anyone tried to setInterval() to poll a server every 20 seconds or so and seen the following error after about 4 polls? ERROR: Socket error -1 while sending Posted at 2015-05-28 by Stevie That looks pretty much like what I was seeing. Only it took ~300 polls for it to happen, most of the time. Sometimes it also happened after a few tries. Interesting in that context: I was now able to use the ESP 8266 without the Espruino. Turned out that my old trusted Bub II FTDI board does not work with it. It works with pretty much everything else, but according to someone else a 1 MOhm resistor is keeping the ESP to work with it. I now use a Teensy as a passthrough serial adapter. With that I was able to use the AT commands and also update the firmware. I then installed NodeMCU on it and did the same test. Same result :-(. After about 300 requests it got stuck... Posted at 2015-05-28 by @gfwilliams What happens if you try every 60 seconds instead of 20? I know I was doing that as a test and it worked for days... It might help to narrow down the problem. Posted at 2015-05-28 by DrAzzy If you ever let the current ESP8266 driver attempt to open more than one request at a time, it will completely fall over. So if a request isn't finished completely before the next one gets fired, things will hit the fan - a brief perusal of the ESP8266WiFi module shows why - no provision has been made for handling more than 1 socket while communicating with the ESP8266. Posted at 2015-05-29 by @gfwilliams As @drazzy says, it could be a result of the connection not getting closed. Do you have the up to date firmware? The old one had some issues where connections didn't get closed if you requested a page with only one or two bytes on it. Posted at 2015-05-29 by Eric OK, so I tried 60 seconds in the interval and got 19 connections but then got the following error after the final response printout: Posted at 2015-05-29 by Eric Oh dear folks, the formatting has gone a bit pear shaped in my last post post! Sorry Posted at 2015-05-29 by @gfwilliams Ok, this is the problem with multiple connections... But then a connection really shouldn't still be open after 60 seconds. Do you have the latest Espruino firmware installed? It should be 1v79 Posted at 2015-05-29 by @gfwilliams I just fixed the formatting for you - just make sure you highlight code and click the 'code' button - and you need to make sure you keep the blank line before and after the code markers (```) that the editor puts in. Posted at 2015-05-29 by Eric Thanks Gordon, I do have the latest 1.79 firmware installed. Perhaps this is my service provider in Spain taking ages to complete the connection to your test URL? I can set up a local server and test again to rule out ISP delays etc. I will check back later. Posted at 2015-05-29 by DrAzzy Yup, you're running into trying to use two sockets at once. It tries to add a line handler for unlink, but there's already one there from the last socket. There is an analogous problem with a few other handlers Posted at 2015-05-29 by @gfwilliams There's a bug for this and I'll try and get a fix in soon. It shouldn't be too hard - although having said that the You could check if sockets are closing by doing something like: As a stop-gap you could do something similar to make sure you don't fire off multiple requests at once I guess. Posted at 2015-05-31 by Eric Hi Gordon, DrAzzy, I tried your suggestion to check the if the socket is closed before attempting a request. The results are varied. I can call around 30 requests in a row using a 10 second interval, but eventually the socket remains open and no further requests are possible. I tried using a local server, my Raspberry Pi to simply echo back a status check and being local the response was very fast but I was unable to request as many calls as using an external website. Strange. Will continue to test with other parameters. Posted at 2015-06-03 by Jorgen Hi guys, Posted at 2015-06-03 by @gfwilliams Right now, it should be possible to flash it if someone wrote some code that would control Espruino. Ideally it'd be in JavaScript and then I add the firmware updater to the Espruino Web IDE. I haven't had time for that yet though :( Theoretically you could just set Espruino up as a pass-thru, with: And then you can just point the flasher at Espruino's USB port - however I think there are some issues with lost bytes on USB when sending big chunks of data. As part of the USB HID work I've been rewriting the USB drivers to fix that, but it's proving very difficult to fix the lost characters - I think it might be an issue with ST's USB library :( Posted at 2015-06-03 by Jorgen ok. I'll try this tomorrow and give feedback. Posted at 2015-10-09 by Majkl Hello friends. I have a problem with When I was testing baud rates, only reasonable output was: What am I doing wrong? Red light is on. When I removed the "if(err) throw err;" the script continues and Blue light is sometimes blinking (when trying to connect) Posted at 2015-10-09 by MichaelPralow please try the baud test code with AT+RST instead of AT+GMR and post the result Posted at 2015-10-10 by @gfwilliams Personally I'd think about updating the firmware on your ESP8266. I haven't come across version 0.21 before and it may behave differently - 0.25 (linked off the ESP8266 page) is the one that we've been developing/testing with... Posted at 2015-10-10 by Ollie Was getting nowhere with my ESP8266 on a breadboard - nothing back from the firmware detection script save for empty quotes. Connected CH_PD to 3.3 on a whim (as out of ideas) and I got the expected return telling me what board version I have. Posted at 2015-10-11 by @gfwilliams The tables for wiring on http://www.espruino.com/ESP8266 do mention that you should connect CH_PD to 3.3v... Or were you looking somewhere else for wiring info? I think CH_PD stands for 'Chip Power Down' - it would have been nice if the board was set up so it powered on at startup, but unfortunately it looks like you do have to connect it to 3.3v to get it to start... Posted at 2015-10-11 by Ollie I've sent you a PR with the table that confused me amended. It did not show requirement for 3.3v on CH_PD in the Pico column, just the Espruino column. Posted at 2015-10-11 by @gfwilliams Thanks - looks like a bit of a copy/paste error on my part :) Posted at 2015-10-14 by Ollie I'm not able to connect to Wifi either, similar issue as others have had with the uncaught no ready. I have the 0.25 version ESP8266 (AT+GMR) am loading the right module and baud is set to 115200. I have a 10uF capacitor between ground and +3.3v at the connections on the ESP8266. I've logged the ouput of AT+RST below, I've no idea what I'm looking at but it seems to suggest a memory issue MEM CHECK FAIL. Can anyone help me move forwards? This is the output of AT+GMR Posted at 2015-10-15 by MichaelPralow i have the same problem, my findings so far:
.. in the end i gave up for now and ordered some ESP8266 ESP-01 from ebay, look for "tested", i am still waiting for them to arrive Posted at 2015-10-15 by @gfwilliams :( Sorry @ollie, you're not having much luck with this stuff at all! Since Posted at 2015-10-15 by Ollie Not your fault @gfwilliams!! I'll get there don't worry - will give your suggestion a try. What I would add, is unlike your experience, I've not had much back from the ESP8266 running other AT commands - for example for listing access points, and haven't been able to connect to anything by trying to talk to it directly with AT commands - as yet. Posted at 2015-10-15 by MichaelPralow
under the hood, the ESP8266 module uses reset a lot
that might be a problem with the pins (CH_PD needs 3.3v too) or not enough power, i had some strange behaviour while using the esp8266 directly with an espruino pico, powered by laptop usb, with one of those breadboard power supply thingies and 100uF it works reliable Posted at 2015-10-15 by Ollie Thanks. I've got CH_PD connected. I guess a bigger capacitor is worth a shot though. Posted at 2015-10-21 by Ollie 100uf capacitors in the post tonight when I got home - so back at it. Didn't help with the more advanced AT commands initially... but then in a stroke of "random" I upped the timeout in my test script - and started to get returns. So... I noticed the ESP8266 module calls the AT module with a timeout of 1000, which in my scripts couldn't do anything more than get a return from basic AT commands; other stuff like So at the risk of more noobness... could more generous timeouts in the ESP8266 js module help in the problems lots of folk seem to be seeing? Posted at 2015-10-22 by MichaelPralow you can test it out by yourself, save the module js https://github.com/espruino/EspruinoDocs/blob/master/devices/ESP8266WiFi_0v25.js in your WebIDE project/modules folder, rename it (e.g. My_ESP8266WiFi_0v25.js) and use that in your code with if that works, start hacking away and change the used timeout @gfwilliams it might be a good move to futureproofness (does that word even exist?) in adding some timeout argument to the modules methods (with 1000 as default), it really looks like the ESP8266 is a lottery @ollie can you test the power with a multimeter, as far as i remember with my breadboard power supply thingie (connected to wall power supply) i got enough to even work without capacitor Posted at 2015-10-22 by @gfwilliams If it is going past the timeouts, I'd be happy to increase them where needed? There's no real issue with them being longer if everything is working fine :) I'm not too convinced about adding an option to set the timeouts... I think if people have had an issue with the timeouts and have to google it and then figure out they need to increase a config parameter, something's gone horribly wrong :) Posted at 2015-10-22 by Ollie Thanks for the tip. I pulled the ESP8266 module as you suggested. Upping the timeouts made no difference, so I also pulled down the AT module and tried to replicate what I can do with Serial2 (so far list APs, connect to a network and get my IP address) using My AT command returns are two lines. I always get the issued command on the first line then OK on the line below. With Also, it always seems to be first line (the command) that is in the var getting evaluated for a match to "OK" in the Esp8266 module code. I'm not the best at following callback logic so I could be barking up the wrong tree - anyone confirm or deny that the timeout param in Posted at 2015-10-22 by @gfwilliams
Not sure I understand? The function will return immediately, but the callback gets called when a string is received or the timeout elapses.
You need to call Posted at 2015-10-22 by Ollie EDIT: Note all of the following actually had no bearing on issue. In end reflashing to the same firmware appears to have sorted it. @gfwilliams thanks for coming back on this thread, I'll try and explain what I mean. As I understand it the AT module wraps serial. So I've got two test functions now, one that is sending AT commands directly using Serial2 and another using the AT module. The first function (Serial2) and some calls with commented returns is/are below. Note the return on ATE0, but that's another story, though I'm starting to disagree :D Trying to test the AT module command When I added a few logging statements in the ESP module I downloaded and have locally I could see that in all cases I tested I doubt that has clarified things much, and it's fair to say I'm a bit out my depth here, so please tell me if I'm muddying the water ;) but I suppose the question I'm posing is why am I ok using Serial2 but not the AT module which wraps Serial. Is there an issue in there? Posted at 2015-10-22 by Moray For my 2p worth I was seeing c. 5% timeouts until I upped the timeout value. It is overkill given I can easily miss a few sensor readings, but I am retrying all failing ESP connects and as a final fallback hard resetting the chip by pulling RST low Posted at 2015-10-22 by Ollie @gfwilliams, whatever I had above please ignore - I cannot reproduce on another Wifi network tonight. Beyond AT, AT+GMR, & AT+RST, nothing now works even with the serialTest function that I got results from earlier. Breadboard/hardware setup unchanged. :/ Posted at 2015-10-23 by @gfwilliams Hmm, strange. Well, the I'd be careful when testing and setting up AT multiple times, as Had you tried Also, just in case, could you maybe try a breadboard power supply to supply 3.3v to the ESP8266? It could still be some power issue I guess? I know people have reported issues with breadboards and ESP8266 (I think because of the power draw), so you could try soldering a capacitor right across the ESP8266's power pins? @moray which timeouts did you have to increase? I'm happy to tweak them up - I'd just rather not increase the ones where Espruino should always be getting an immediate response from the ESP8266. Posted at 2015-10-23 by Ollie Success. Cap was on ESP8266 already, but in a last ditch attempt I decided to reflash it, even though I had revision 0.25 it seems flashing it with the 0.25 bin on the ESP8266 page has resolved. My serial and AT tests still behave as they did so they obviously have no bearing on the matter whatsoever, so I don't mind if you drop those posts, as I would not want to mislead others. Is it possible for flash to be loaded improperly? Moral is - flash it - even if you think you have good firmware! Don't think I've ever had to fight as hard for a hello world Posted at 2015-10-23 by @gfwilliams Great! I think the ESP8266 has some configuration settings it stores in flash, so I guess those could have been corrupted. Not good that the module came pre-installed with bad firmware though. Also, I didn't think about this before, but you made your own module loader? I'm not sure if you're using the minified version of the modules or not, but I'd advise it. They'll be a bit faster and will use less memory. Posted at 2015-10-24 by Ollie @gfwilliams you mean the Go console I made? Yes that pulls the minified versions. It works really well from my use of it so far but I've not actually been using that in this process - there where too many variables as it was - so have upgraded Mac to El Capitain - now Chrome IDE working very well (lots of other stuff on my Mac now doesn't quite work at all or as it did, but hey ho) Posted at 2015-10-26 by @gfwilliams Wow, great! Yes, I meant to Go console, but as you say it's probably less variables to use the Chrome IDE :) Did you just update the OS on the old mac then? Sorry to hear it broke lots of other stuff :( Posted at 2015-10-26 by Ollie Yes, it's available for 10.6.8 upwards and its a free upgrade (they've seen the light). I'm using the IDE for most stuff now it's functional for me. But the Go console was a good experiment that I'll come back to with some slightly different use cases in mind. Posted at 2015-11-07 by Dennis I'm trying to make Olimex's ESP8266 board (MOD-WIFI-ESP8266 Rev. A) work with the Pico. I'm using the 10 uF capacitor. I don't have a shim (and it doesn't fit Olimex's board anyways). The firmware version test revealed No this fun indeed. I figured that the best bet would be to update the firmware to one tested with Espruino, so I downloaded version 0.50.0.0. With regards to the module documentation:
In order to put the the ESP into boot mode on the Olimex board, I actually had to solder: the GPIO0 solder jumper needs to be put into position 0 (more about this). I successfully flashed the new firmware, soldered the jumper back to 1 and... nothing. Now the board doesn't respond anymore, also the firmware check program just returns 3 empty strings :( What did I do wrong? And what was I supposed to flash to where? The firmware zip files comes with many bin files, but the included readme is not clear. I flashed the Posted at 2015-11-08 by @allObjects I used the 0.25 on a ESP-01 that came with 0.18. And that was trivial, after I had to throw away the first broken one (it always failed sooner or later to write to the EEPROM). Now I got some - two - more with 0.40 version. What to do? Hope it complies with 0.25 or bump it up to 0.50. Because it was not very clear which files had to be place on it, so I down graded it to 0.25... and it works now most of the time. So give it a shot with 0.25. (I'm also interested in a bit more details about the 0.50 version.) Posted at 2015-11-08 by Dennis Did you flash two images or just one? And which ones? The firmware zip contains 5 bin files and it's not clear which ones to use and which addresses to flash them to. Posted at 2015-11-09 by @allObjects For 0.25, afaik, only one file has to be flashed. I cannot exactly recall the source I got the 0.25 from, but it seemed to me to be just 1 file. Not so with 0.50 taken from the ESP8266 site, where it is a zip with many files. Posted at 2015-11-09 by @gfwilliams Yes, afraid I'd use 0v25 - that's the version that's had the most testing done with Espruino and which seems reliable. It's just a single binary that flashes on and should just work out of the box. I'll try and update the docs with your suggestions (and a note recommending the 0v25 over the 0v50). Posted at 2015-11-10 by Dennis Thanks gentlemen... after soldering the GPIO0 jumper back and forth about 50 times in 2 days trying to awaken the ESP8266 with the 0v50 firmware in all its variations, I tried the 0v25 version as you suggested. It's counter-intuitive but it worked immediately! Now I can finally turn off the solder station and write some JavaScript :) Posted at 2015-11-10 by @allObjects ...put SMT resistor over the solder bridge... and when you need reset, you just touch the chip side with a (bread board) grounded wire... I'm sure it is not the last time you'f flashed. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-05-02 by gnz
Hi guys,
I got my Pico earlier this week and I've been trying to get it to work with some ESP8266s I bought a couple of months ago. I flashed the pico because 1v75 doesn't include NetworkJS, but to no avail. I tried with the two flash versions available, WIZNet and CC3000 (btw, why isn't there an ESP8266 build for 1v78?), but I get the following error after a few seconds:
Any hints? Am I doing anything obviously wrong? The ESP8266 lights up the red led when the Pico is connected, but that's about it (not sure if it is supposed to blink at some point thou).
Thanks!
gonzalo
Beta Was this translation helpful? Give feedback.
All reactions