Did I brick my ESP8266 ESP01 on Pico? #5081
Replies: 1 comment
-
Posted at 2020-06-23 by @gfwilliams Hi - sorry for the delay, I was away last week. How did you update the firmware? Using the instructions for 'Use Espruino' at http://www.espruino.com/ESP8266#use-a-separate-usb-ttl-adaptor ? So actually doing the connection via the Pico? First I'd make sure your Pico firmware is up to date, then did you make the changes to ESP_RAM_BLOCK/ESP_FLASH_BLOCK ? Posted at 2020-06-24 by tarmo888 Yes, I used the http://www.espruino.com/ESP8266#use-espruino instructions on Pico, I have shim v1 and I ordered 10 days ago new shims for Pico too, but I guess you haven't got time to process them yet, I only got the automated order email. Posted at 2020-07-02 by @gfwilliams Do you have a USB TTL converter? I'd maybe try using that to flash the ESP8266. You'd have to solder wires onto the ESP8266 pins but it's worth a try. When the Pico is connected to power, A2/A3 should be open circuit so if you've got them connected to the USB TTL converter you should be fine. Posted at 2020-07-02 by tarmo888 I think I don't have, but I have this USB programmer https://www.sparkfun.com/products/12924 and I have Arduino Uno, for which I found this guide https://dzone.com/articles/programming-the-esp8266-with-the-arduino-ide-in-3 Posted at 2023-02-19 by MichaelS I had the same issue as @tarmo888 (I also had no I've come back to my Pico after some years (kickstarter backer supplied with ESP8266 & v1 shim). I soldered the ESP8266 & shim to the Pico, and it originally worked. The firmware versions reported the 0018000902-AI03 version, so I wanted to upgrade, but no matter what I tried (via the IDE or esptool) I couldn't get it to work. I think I completely clobbered the driver by trying So here's what worked for me - the tool espFlasher mentioned on the page in the last link on Gordon's instructions worked (I used the 64-bit version). The 0.25.0.0 FW version could be loaded provided the "Connect to Espruino" instructions on Use Espriuno (I ignored the digitalWrite lines since those are for the new shim), enabled the ESP8266 bootloader as per the instruction, and instead of running esptool.py, run the espFlasher with baud set to 115200 (via Advanced tab). After restarting, and trying the firmware versions routines, you'll see the 0.25.0.0 version reported. Posted at 2023-02-20 by @gfwilliams Thanks for letting us know what fixed it for you, and glad you got it sorted in the end! Did you ever manage to try the IDE to update, or did that not work at all? http://www.espruino.com/ESP8266#use-the-espruino-ide Posted at 2023-02-20 by MichaelS Thanks @gfwilliams. I did originally try that since it was recommended, but I couldn't get it to work. After I shorted GPIO0 to GND, the process seemed to start, but it failed prematurely with a 'sync error' (or similar, so I can't recall the precise error). I also tried shorting the reset pin, but I think that's unnecessary/undesireable(?), but when I did that I seemed to get further (the block writing started) but it crashed out about half way (at around block 500). This is when I gave up using the IDE, and opted for the "Espruino as a makeshift USB-TTL adaptor" which eventually worked for me. I was wondering whether the '0.25.0.0 FW version' is the best one to use, but I guess it is since the 512kB ESP01 modules are not compatible, and I think those are the ones that were given out during the Pico kickstarter campaign? I am hoping for a new wifi-capable Espruino model in the future (maybe with an antenna connector option) as I found the ESP-01/shim approach a bit fiddly especially if a firmware update is required (but totally understandable as that was what's available at the time). Posted at 2023-02-22 by @gfwilliams Did Thanks - yes, I do have plans for a WiFi Espruino - but it'll be some time later this year I'm afraid as I have a few other things I need to sort out first. Posted at 2023-02-22 by MichaelS The link associated with Posted at 2023-02-23 by @gfwilliams Ahh! I just checked and it seems possible that even 2.0.0.0 should work: https://bbs.espressif.com/viewtopic.php?f=46&t=2451 The ESP01 modules are (as far as I know) 1MB (8Mbit) modules (whereas the other modules are 4MB (32Mbit). So the I'm not sure where the 0.40.0.0 firmware is I'm afraid - I think it's likely I never had it (apart from pre-installed on modules) which is why it wasn't linked. I did however just try to install the 1.1.0.0 firmware via the Web IDE on a Pico with an ESP01 on a shim and that worked fine, so I'm not sure what's up. I think it's possible that earlier shims didn't include the pins for boot mode, or maybe just that your shim's soldering might not have made a connection there - and I guess that would have really messed things up for you unless you had manually connected GPIO0 Posted at 2023-02-23 by MichaelS I recall reading that the v1 shims (which I have) didn't include those pins for boot load, so I had to ground GPIO0 and then momentarily ground the reset pin for the process to work with the espFlasher. When I tried the same process with the IDE, writing could only get halfway before it crashed out with an error message. At the time, I didn't record the message, but if it's helpful I can try that again to reproduce it. To confirm, is it correct that in order to flash the ESP01 via the IDE it's required to ground GPIO0 and then momentarily ground the reset pin, or is it sufficient to just ground the GPIO0 (which is what I recall reading, but that didn't work either as reported before). Thanks for the v2 info, I'll give that a go later. Posted at 2023-02-23 by MichaelS I just tried flashing via the IDE again - here's what I did:
BTW I have wondered about those later versions which appear to contain a boot loader and other code, so I guess the IDE is only loading the needed part. I'll keep looking into the later version as an experiment. Posted at 2023-02-24 by @gfwilliams Hi,
I think you would have to ground GPIO0 and then reset (or I guess just ground it and plug the Pico in). If connected with the shim then the IDE would automatically do the GPIO0+reset, but it sounds like in your case we don't have that. Posted at 2023-02-24 by MichaelS if I do the following:
The Firmware update failed: Unexpected response {"dir":1,"cmd":3,"len":2,"data":"\u0001\b"} @gfwilliams, what do you think? Posted at 2023-02-24 by @gfwilliams Oh wow, ok. So it would seem that the firmware update process does workbut your module is the 512k variant, so it's uploading the wrong firmware. I'm sorry about this - I checked with a Pico+ESP01 I had on my desk here assuming it was the same and it worked, but it must have been a 1M variant and I got confused between 0.5M/1M and 4M ones. I just had a quick google and found this tidbit:
And it looks like I must have supplied the blue 512KB ones with the KickStarter campaign (at least that's what is in the picture on http://www.espruino.com/ESP8266) Sorry - it's possible I was aware at one point but in the years since this I must have forgotten. I did manage to find this though: https://www.sevarg.net/2016/11/20/installing-latest-at-firmware-on-4mbit/ It seems to imply that you can use AT firmware 1.3.0.0 with 'noboot' - the firmware link doesn't work now, but this seems to be the new one: https://github.com/espressif/ESP8266_NONOS_SDK/releases/tag/v2.0.0 I checked and Posted at 2023-02-24 by @gfwilliams Quick update: I've now pushed an update to the IDE. It will now update to AT firmware 1.3.0.0 (SDK 2.0.0) which I think is the latest available for 512k. I dug out a Pico with a blue ESP8266 and it does seem to work! Hope that fixes things for you - I'll push an update to the docs as well later on. Posted at 2023-02-27 by MichaelS Thanks alot Gordon. I indeed have the blue ESP01 board. I tried again the IDE method of flashing that board, grounded GPIO0 and momentarily grounded the reset pin, and I got the same result in post #15 above (i.e. interrupted write). So I reviewed that article, and found I could successfully flash the v2.0.0 firmware via the previously-described process using the espflasher application, with the 4 files each placed at respective addresses as pointed out in that sevart article (Installing the Non-Boot Firmware section) you pointed out. Thanks alot for locating that article. I'm wondering in the IDE update whether you're applying the v2.0.0 update as per the info in that section (for that ESP01 board). Posted at 2023-02-27 by @gfwilliams
What I did was completely erased an ESP8266, did it as per those docs and then downloaded one big 512k binary. It should have basically the same effect. It's an odd one because I dug out a blue ESP8266 on a Pico and flashed via the Web IDE to check that it'd be ok, and it was fine - so I wonder what's different in your case... Still, at least you have it working now with the latest firmware! Posted at 2023-02-27 by MichaelS Agree - it's good to have the latest. FWIW here's the package lettering on the chip - is it the same as your test one? ESP8266EX I understand from quick research, there's some variation on the package labelling (whether it makes a difference however). Posted at 2023-02-28 by @gfwilliams Yes, it's the same! The flash chip could be different I guess, but I think there's a good chance that they are from the same batch. The upload issues could actually be based on us having different operating systems though - I'm using Ubuntu here |
Beta Was this translation helpful? Give feedback.
-
Posted at 2020-06-14 by tarmo888
I realized that I was still using
0018000902-AI03
firmware, so I decided to update it. I made a mistake of doing it on Windows because esptool.py kept timing out. Then I read about--no-stub
option and added that to my command. Reading/writing started to work, but got slower and slower and timed out before reaching even 20% of flashing. I finally realized that I could have flashed it through Raspberry Pi 3+, but even there it doesn't work without--no-stub
and flashing fails anyways. Whats my options?Beta Was this translation helpful? Give feedback.
All reactions