wener

Most recent activity

• NodeMCU v3 not working, always report 1396, room 16

  @wener started

  • 2 comments
  • 1,701 views

  @wener replied
• NodeMCU v3 not working, always report 1396, room 16

  in ESP8266 • 7 years, 5 months

  

  This is caused by esptool v1.1, after I use the latest esptool, everything is ok now.

• NodeMCU v3 not working, always report 1396, room 16

  in ESP8266 • 7 years, 5 months

  

  This what I done

  Flashed by flasher.js https://github.com/thingsSDK/flasher.js 1v87

  After flashed I

  screen /dev/cu.wchusbserial1410 9600
  

  Give me

   1396, room 16
  tail 4
  chksum 0x89
  load 0x3ffe8000, len 776,
  

  I don't know what happen.

  I also tried espruino.com/binaries/travis/b3dc05b5378­a9182eea44e8c47b15c54e788037d/espruino_1­v87.tve_master_b3dc05b_esp8266.tgz this build

  $   esptool.py --port /dev/cu.wchusbserial1410 --baud 115200 write_flash \
  >       --flash_freq 80m --flash_mode qio --flash_size 32m \
  >       0x0000 "boot_v1.6.bin" 0x1000 espruino_esp8266_user1.bin \
  >       0x3FC000 esp_init_data_default.bin 0x37E000 blank.bin
  esptool.py v1.1
  Connecting...
  Running Cesanta flasher stub...
  Flash params set to 0x004f
  Writing 4096 @ 0x0... 4096 (100 %)
  Wrote 4096 bytes at 0x0 in 0.4 seconds (80.0 kbit/s)...
  Writing 471040 @ 0x1000... 471040 (100 %)
  Wrote 471040 bytes at 0x1000 in 40.9 seconds (92.2 kbit/s)...
  Writing 4096 @ 0x3fc000... 4096 (100 %)
  Wrote 4096 bytes at 0x3fc000 in 0.4 seconds (80.1 kbit/s)...
  Writing 4096 @ 0x37e000... 4096 (100 %)
  Wrote 4096 bytes at 0x37e000 in 0.4 seconds (80.1 kbit/s)...
  Leaving...
  

  But still give me

  load 0x40100000, len 2408, room
  

  What should I do ?