- Sun Aug 20, 2017 5:55 pm
#69341
Since the checksum and size above are exactly the same as the one in your initial post, this module contains the blink-demo (flashed by you?) and not the default Espressif NON-OS SDK firmware.
Like eduperez already said: once you flash your ESP with other firmware, the old firmware will be overwritten.
If the old firmware was "AT-command" (called "NON-OS SDK") firmware, it will be overwritten and isn't available anymore, so you can't use AT-commands anymore, until you reflash it with "NON-OS SDK" firmware (but then you'll lose your own, or the blink-demo, firmware) again.
If you do have NON-OS SDK firmware flashed on the ESP and you don't get the "2nd boot version" stuff at startup, set the baudrate to 115200 baud, reset the ESP and at the prompt type "AT+GMR" (all capitals, no quotes) followed by a CR and LF.
This will give you a cryptic version number like: "0018000902-AI03".
Bill Weis wrote:ets Jan 8 2013, rst, cause:2, boot mode:(3,6)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09f0c112
~1d
Since the checksum and size above are exactly the same as the one in your initial post, this module contains the blink-demo (flashed by you?) and not the default Espressif NON-OS SDK firmware.
Like eduperez already said: once you flash your ESP with other firmware, the old firmware will be overwritten.
If the old firmware was "AT-command" (called "NON-OS SDK") firmware, it will be overwritten and isn't available anymore, so you can't use AT-commands anymore, until you reflash it with "NON-OS SDK" firmware (but then you'll lose your own, or the blink-demo, firmware) again.
If you do have NON-OS SDK firmware flashed on the ESP and you don't get the "2nd boot version" stuff at startup, set the baudrate to 115200 baud, reset the ESP and at the prompt type "AT+GMR" (all capitals, no quotes) followed by a CR and LF.
This will give you a cryptic version number like: "0018000902-AI03".
Assumption is the mother of all f*ckups. At least: that's what I'm assuming.
