Install MIcroPython Firmware on ESP8266-12E chip

agaomnagaomn Registered Users Posts: 1 ■□□□□□□□□□
I am trying to install MIcroPython Firmware on my ESP8266-12E chip. I am using esptool.py to flash the firmware. I have successfully uploaded the firmware esp8266-20170612-v1.9.1.bin followed by a flash_erase. I have used following commands to flash the chip.
$ sudo esptool.py --port /dev/ttyUSB0 erase_flash
  esptool.py v2.0.1
  Detecting chip type... ESP8266
  Chip is ESP8266
  Uploading stub...
  Running stub...
  Stub running...
  Erasing flash (this may take a while)...
  Chip erase completed successfully in 13.0s
  Hard resetting...

$ sudo esptool.py --port /dev/ttyUSB0 write_flash --flash_mode qio --flash_size detect 0x0 esp8266-20170612-v1.9.1.bin --verify
  esptool.py v2.0.1
  Detecting chip type... ESP8266
  Chip is ESP8266
  Uploading stub...
  Running stub...
  Stub running...
  Configuring flash size...
  Auto-detected Flash size: 4MB
  Flash params set to 0x0040
  Compressed 598432 bytes to 390604...
  Wrote 598432 bytes (390604 compressed) at 0x00000000 in 34.5 seconds (effective 138.8 kbit/s)...
  Hash of data verified.

  Verifying just-written flash...
  (This option is deprecated, flash contents are now always read back after flashing.)
  Flash params set to 0x0040
  Verifying 0x921a0 (598432) bytes @ 0x00000000 in flash against esp8266-20170612-v1.9.1.bin...
  -- verify OK (digest matched)
  Hard resetting...

As you can see verification of flash process is OK. And I can see a new wifi ssid on my wifi list.

Now when I am trying to access REPL via picocom it is hanging on following:
picocom v1.7

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,

Terminal ready

I also tried screen, putty and minicom same behaviour on them as well. Also encountered a strange behaviour that it is working perfectly via ESPlorer.

Is there anything that I am missing? Or any suggestion to hunt this situation?

Sign In or Register to comment.