-
• #2
Yay, I found the source of the problem. I found a README in the Espruino repo with more specific instructions for my 1MB device.
https://github.com/espruino/Espruino/blob/master/targets/esp8266/README_flash.txt
Here's the exact command that worked for me:
$ ~/.local/bin/esptool.py --port /dev/ttyUSB0 --baud 115200 write_flash --flash_freq 40m --flash_mode dout --flash_size 1MB 0x0000 "boot_v1.6.bin" 0x1000 espruino_esp8266_user1.bin 0xFC000 esp_init_data_default.bin 0xFE000 blank.bin
Note that this did not work with flash modes
qio
ordio
. Onlydout
worked. -
• #3
Great to hear you solved it and shared the solution!
This is the crazy part of such a cheap device, lot's of companies sell them and just change a tiny bit and then they behave different ...
I'm able to flash my ESP8266 without errors, but connecting to the interactive console over serial does not work. Instead of getting a prompt, I see only garbled text, and then no ability to type anything.
Exact product link: https://www.sparkfun.com/products/13678
Here's my chip info:
I've reset the flash entirely:
And flashed like so:
I'm not sure I got the exact addresses for my chip (1MB flash), because the instructions only have addresses for 512KB and 4MB.
http://www.espruino.com/ESP8266_Flashing#initial-flashing
But I'm using the 512KB version, hoping that works. I was recommended on Gitter to use dio flashing mode instead of qio as the instructions indicate, but neither of those options change the behavior.
After flashing, I connect with screen.
And this is what shows up on my screen
Using different baud rates will change how long this garbed output is. The specific wiring I'm using matches the "Definitive Wiring Guide" instructable.
https://www.instructables.com/id/FTDI-ESP8266-Definitive-Wiring/
Any ideas what's wrong here?