-->
Page 1 of 1

AT library binaries in lastest 1.01 SDK (ESP-12)

PostPosted: Sat May 09, 2015 12:48 pm
by halherta
I downloaded the latest sp_iot_sdk_v1.0.1_15_04_24 sdk, extracted the sdk, cd'ed into the 'bin' directory and then used the following command to program the AT binaries on my ESP-12 (nodeMCU board):

Code: Select allpython esptool.py   --port /dev/ttyUSB0 --baud 115200 write_flash 0x00000 boot_v1.3\(b3\).bin 0x01000 at/user1.1024.new.bin 0x81000 at/user2.1024.new.bin 0x3fc000 esp_init_data_default.bin 0x3fe000 blank.bin


This initially seems to flash the board successfully and the AT command set is functional until power is cycled or the software reset command is executed. After power cycling/software reset the ESP-12's blue led is constantly on and I receive lots of junk when I attach the device to my serial terminal i.e. its non functional/bricked.

When I use the same procedure with the esp_iot_sdk_v1.0.1_b1_15_04_02 version of the SDK, everything works just fine. Since the ESP-12 has a 32MBit flash part (0xEF winbond 4016) I doubt that this issue has anything to do with memory limitations.

for now I'll use the functional AT binaries in the esp_iot_sdk_v1.0.1_b1_15_04_02 , but I do appreciate any insights into why this is happening and how to flash the latest v1.0.1 AT binaries onto the ESP-12 successfully.