You can chat about native SDK questions and issues here.

User avatar
By Zaszigre
#76061 Hello everyone,

I'm using the esp8266 Luncher, compiling C code with the RTOS SDK V2.0.0 and flashing the code with esptool.py.
After flashing the spiffs_test exemple, at boot, the chip now enter a panic loop. I tried flashing an other code but it's all the same. Using esptool.py, I have erased the flash and used the ESP8266 DOWNLOAD TOOL v3.6.3 to flash the esp_init_data_default.bin.

Doing this I have noticed something. When flash the esp init, I get a different message rather if I then upload a code or not.

without flashing anything but the esp_init thing:
Code: Select all ets Jan  8 2013,rst cause:1, boot mode:(3,2)

load 0x40100000, len 2592, room 16
tail 0
chksum 0xf3
load 0x3ffe8000, len 764, room 8
tail 4
chksum 0x92
load 0x3ffe82fc, len 676, room 4
tail 0
chksum 0x22
csum 0x22

2nd boot version : 1.7(5d6f877)
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size & Map: 16Mbit(1024KB+1024KB)
jump to run user1 @ 1000

rf_cal[0] !=0x05,is 0xFF


after flashing a code of mine:
Code: Select all ets Jan  8 2013,rst cause:1, boot mode:(3,2)

load 0x40100000, len 2592, room 16
tail 0
chksum 0xf3
load 0x3ffe8000, len 764, room 8
tail 4
chksum 0x92
load 0x3ffe82fc, len 676, room 4
tail 0
chksum 0x22
csum 0x22

2nd boot version : 1.7(5d6f877)
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size & Map: 128Mbit(1024KB+1024KB)
jump to run user1 @ 1000

OS SDK ver: 2.0.0(e271380) compiled @ Mar 30 2018 18:54:06
rf_cal[0] !=0x05,is 0xFF


Do you kow how could end this and return to a factory deflaut ?

thank you ♥
You do not have the required permissions to view the files attached to this post.
User avatar
By Solomon Candy
#76194 Just a shot in the dark here but perhaps you can try including this file (attached) in your source. I haven't ever used the esp8266 Launcher or know what it is so what I'm saying may not be very sensible.
The attached file is supposed to automatically glean the cal sector. Good luck!
You do not have the required permissions to view the files attached to this post.
User avatar
By Cicero
#76264 Looks like you're using the OTA firmware, which means the esp_init_data_default needs to be flashed into a different address than the non-OTA.

Try flashing init_data to 0xFFC000 for 16MB