This is a ESP8266-12E on a ESP 13 Shield. Mounted on a UNO - but right now the UNO is just providing 5V power.
Trying to get the original AT Firmware V2.0.1 ( the latest on to the chip ) Using the Original; Espressif flasher tool Version 3.4.9.2 on a Windows 10 PC.
I have no problem connecting up to the chip, start downloading but then for some mysterious reason the operation fails at random at some point with a message "Invalid head of packet('') "
Attaching the screen shot. Any idea what is going wrong - the firmware , flasher - all are the latest. And yet this woe. Is something broke ??
( I know i could have asked this in the Espressiff forum, but for sure the response in this forum is fast )
Maybe try a slower baud rate. I don't use that flasher tool but when I upload to my ESP's they sometimes get grumpy with high baud rates.
Another random try might be to change the SPI mode to DIO.
Riva:
Maybe try a slower baud rate. I don't use that flasher tool but when I upload to my ESP's they sometimes get grumpy with high baud rates.
Another random try might be to change the SPI mode to DIO.
This ESP8266 is a good one but the support available to use it is pretty low. The complication is more because there are zillion variants and you never really know what is it you have on hand. And till date I have been trying to understand who the AI-Thinker is but could not !! As you can see there is nothing that can be spotted as wrong in the screen shot I sent and yet it does not succeed ( as suggested by the vendor I even tried using the NODE MCU flasher. It completes but with the progress at 50% mark and of the ESP8266 does not respond to most AT commands.
OK ... there is a development though not a very happy one. Tried to use the MODE MCU flasher. The download went and the progress bar reached the end - Stopped - waited and then said ERROR.
When i connected the ESP13 module to a terminal program, i get the following message that keeps repeating like crazy ... is there anything to learn from this ??
Finally i can see that it is upset that some rf_cal[0] is not 0x05 and instead reads 0xff. I am sure i did not monkey with this.
OK with the same setup i tried with a Node MCU module. Works first time and any time - downloads start and finish without issues.
So this leads to a question - is it that companies who supply the NODE MCU and Sparkfun etc take care to use quality passed ESP8266 modules and the other non descript ones just use untested modules ?
What a waste of time .. really when a firmware download stops or aborts there is precious little that you can do apart from retrying endlessley and by changing one or other setting ( hoping it will work ). What a waste of time ?
