- Thu May 28, 2015 10:45 am
#18740
looking at your links you are indeed after the AT firmware. There is a wrinkle with one that is shipped with the new SDKs - it won't fit on older devices with 512kB flash (most devices out there right now are like this). I am in the process of doing a write-up on this. Give me a few more days.
- Thu May 28, 2015 12:01 pm
#18748
Just retried it with another esp-1 using an external power source to give it exactly 3.3v.
When I tried to download the first bin file, it said invalid head of packet or something like that.
Now the chip is in the same state as the other one. I can't get any response from the terminal and the esptool can't connect to it.
When I tried to download the first bin file, it said invalid head of packet or something like that.
Now the chip is in the same state as the other one. I can't get any response from the terminal and the esptool can't connect to it.
- Mon Jun 01, 2015 12:23 pm
#19138
Why don't you try NodeMCU to see if that works for you. Maybe when you downloaded the firmware the file was corrupt. With the NodeMCU flasher everything is fairly automated so that would eliminate some potential problems and once the module is breathing again you can try to flash the AT firmware again.
- Tue Jun 02, 2015 1:56 am
#19190
here's that promised writeup on how to build/update to the latest (1.1.0) AT firmware for 512kB flash ESP modules
