john_m wrote:Programmer.png
AgentSmithers wrote:I know this sounds silly but I had the same issue when I upgraded my SDK. Have you tried doing an eraseflash with your esptool.py?
Run that command and see if that resolves it after refreshing your firmware, I know it sounds crazy but I did it I think three times before it resolved my issue.
Thanks for your suggestions so far. I tired this as well. Not working. I tried AT firmware also. No luck.
But it is working perfectly with another SDK(superhouse esp-open_rtos).
Kindly confirm the programming addresses (for ESP12E Node MCU module) from the attached
Ahhh oooo esshh, I am not sure about your addresses. Im a NonSDK guy, We only use 0x1000 for OTA firmware. For standalone we use 0x10000. One thousand vs. Ten thousand. But if your boots and you can see your PrintF's then I couldnt see why it wont work. The only thing I can imagine is your init data being wrong but even then... I flash my init to 3FC000 as well though, so the difference I see here is your blank.bin is being flashed to 3fe000, on mine I am doing 0xFE000 and 0x7e000. I don't have notes on me at the moment on why I did that but our main address is different for sure (the 1000 vs 10000).
I tried to look up the external SPI size of the ESP12E and cant seem to easly find it. Ensure that 32Mbit = 4MB is correct.
Note: Mb = Megabits and MB = MegaBytes. I apologize if you are already aware of this.