ESP8266 Community Forum

- Thu Oct 02, 2014 1:53 pm #1128

Firmware '.922' (0018000902 modified) found here : http://www.electrodragon.com/w/Wi07c
(Firmware Log : 0.9.2.2 AT Firmware.bin.zip")

Thanks al1fch!
XTCOM doesn't seem to work for me while esptool happily connects. Can i write the flash file with esptool to the device like this?

Code: Select allesptool --port COM3 write_flash 0x000000 0922.bin

I don't like to brick this little guy so soon

- Thu Oct 02, 2014 2:19 pm #1131 Well, i thought i give it a go.
I've used the 0.9.9.2 image mentioned above. After flashing the image the device reverts to 9600 baud and prints the following during boot:

Code: Select all[System Ready, Vendor:www.ai-thinker.com]

But doesn't seem to react to the console typing. Characters are does echoed back to me but this might just my terminal doing local echo. Seems like after a while it reboots on it's own (watchdog kicks in?). I'm using PuTTY on Windows to connect via UART. I've tried changing CRLF settings as others recommended. Doesn't seem to change anything.

I think flashing was not complete, esptool wrote this for me:

Code: Select allc:\esp8266>esptool.py --port COM3 write_flash 0x000000 0922.bin
python dll
kernel32
kernel32
Connecting...
Erasing flash...
Writing at 0x0007ec00... (99 %)
Leaving...
Traceback (most recent call last):
  File "C:\esp8266\esptool.py", line 351, in <module>
    esp.flash_finish(False)
  File "C:\esp8266\esptool.py", line 188, in flash_finish
    raise Exception('Failed to leave Flash mode')
Exception: Failed to leave Flash mode

That 99% worries me Seems like esptool has some kind of issue with this: https://github.com/themadinventor/esptool/issues/1

I'm trying to flash the Cloud ROM from Electrodragon.

- Thu Oct 02, 2014 3:46 pm #1134

Well, i thought i give it a go.
I've used the 0.9.9.2 image mentioned above. After flashing the image the device reverts to 9600 baud and prints the following during boot:

Code: Select all[System Ready, Vendor:www.ai-thinker.com]

But doesn't seem to react to the console typing. Characters are does echoed back to me but this might just my terminal doing local echo. Seems like after a while it reboots on it's own (watchdog kicks in?). I'm using PuTTY on Windows to connect via UART. I've tried changing CRLF settings as others recommended. Doesn't seem to change anything.

I think flashing was not complete, esptool wrote this for me:

Code: Select allc:\esp8266>esptool.py --port COM3 write_flash 0x000000 0922.bin
python dll
kernel32
kernel32
Connecting...
Erasing flash...
Writing at 0x0007ec00... (99 %)
Leaving...
Traceback (most recent call last):
  File "C:\esp8266\esptool.py", line 351, in <module>
    esp.flash_finish(False)
  File "C:\esp8266\esptool.py", line 188, in flash_finish
    raise Exception('Failed to leave Flash mode')
Exception: Failed to leave Flash mode

That 99% worries me Seems like esptool has some kind of issue with this: https://github.com/themadinventor/esptool/issues/1

I'm trying to flash the Cloud ROM from Electrodragon.

i reported the same issue above, but at least one other has been able to get it to work. with the Windows tool I get 99% and "failed to leave" message, but the flash is fine. if you boot it up and get 9600 baud stuff, you are good. Now we need to sort out this CRLF issue. I will be working on it shortly and will report back. (I guessed I missed the PY script. I want to use it on my MAc so I am not PC dependent. Link please?)

EDIT:

I downloaded GUI terminal client and with CR+LF my chip works great.

Mac CoolTerm and Settings - 0018000902

Firmware still reads "0018000902"

also, was able to get the baud up to 230400 (my emulator does not go higher)

AT+CIOBAUD?

+CIOBAUD:230400

OK

Last edited by Samighi11 on Thu Oct 02, 2014 4:27 pm, edited 2 times in total.

- Thu Oct 02, 2014 4:02 pm #1135 Strange. If i flash other firmware to the module it's working correctly. With 0.9.9.2 it reboots endlessly if i try to connect to my AP, like half the time.

For the CRLF issue: PuTTY is dumb. You cannot configure it to send CRLF when pressing <ENTER>, it always sends CR only. Moved on to IVT terminal where i can configure this by terminal settings.
For testing purposes I've connected the module to my Arduino using SoftwareSerial. Things works until the module not starts sending massive amount of data to the arduino. Then it drops like half of the incoming data So it seems i have to use the hardware UART and leave software serial for debug printing.