ESP8266 Community Forum

- Sat Jun 06, 2015 12:57 pm #19667

After many headaches I finally found it!

Yup but for those interested, what is the URI??

I must admit that I don't see what is the problem of just doing:

Code: Select allesptool write_flash 0x00000 0x00000.bin 0x10000 0x10000.bin


Please see my Developer FAQ for Q&A on nodeMCU Lua before asking a question here that's already been answered. This and the other official documentation should be your first reference for developing Lua Apps

- Sat Jun 06, 2015 7:25 pm #19704

Yup but for those interested, what is the URI??

I found it here.

I must admit that I don't see what is the problem of just doing:

Code: Select allesptool write_flash 0x00000 0x00000.bin 0x10000 0x10000.bin


The reason I wanted to know how to make a single FW file is because in this thread I wanted a simple easy to burn file with some debug code in it that made sure there was no residuals from the previously burned FW, That way I could make sure that he started off with a blank chip and that I had the same FW so I could duplicate the errors on my end so I could maybe track down and fix the problem.

Also, uploading just 0x00000.bin and 0x10000.bin doesn't erase the list of APs stored in the flash and in my experience it also won't recover a chip that has been soft-bricked by a failed burn or something else.
That's why I now burn with:

Code: Select allesptool --port /dev/ttyUSB0 --baud 460800 write_flash 0x00000 0x00000.bin 0x10000 0x10000.bin 0x7c000 esp_init_data_default.bin 0x7e000 blank.bin

460800 Baud because a burn time of ~18s is better than ~43s