Page 1 of 1

升级SDK到2.0后不断重启应当如何解决?

Posted: Thu Aug 04, 2016 12:36 am
by wsptr
把SDK升级到2.0,重新编译程序后生成的eagle.flash.bin烧到0x00000,eagle.irom0text.bin烧到0x40000,esp_init_data_default.bin烧到0x7C000,blank.bin烧到0x7E000。烧完后片子不断重启,并打印如下信息:

Code: Select all

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 30984, room 16
tail 8
chksum 0x47
load 0x3ffe8000, len 968, room 0
tail 8
chksum 0x84
load 0x3ffe83d0, len 1856, room 0
tail 0
chksum 0xc9
csum 0xc9
E:M 830521632
E:M 831924384
E:M 831924384
E:M 831924384
E:M 831924384
E:M 831924384
E:M 831924384
rf_cal[0] !=0x05,is 0xFF

请问这个问题应当如何解决?

Re: 升级SDK到2.0后不断重启应当如何解决?

Posted: Thu Aug 04, 2016 1:27 am
by zaxl
Hi,

I'll guess that you haven't flashed blank.bin on your RF cal sector - see SDK 2.0 release notes

Re: 升级SDK到2.0后不断重启应当如何解决?

Posted: Thu Aug 04, 2016 9:19 pm
by wsptr
zaxl wrote:Hi,

I'll guess that you haven't flashed blank.bin on your RF cal sector - see SDK 2.0 release notes



Hi,
I have already falshed blank.bin into flash, even I generated a file that is 1MB filled with 0xFF and flashed that in. But the issue is still there. I tried to flash an old version built on an erlier SDK, then flash the new one directly without blank.bin, it worked. Why this happen?

Thank you.

Re: 升级SDK到2.0后不断重启应当如何解决?

Posted: Thu Aug 11, 2016 6:19 pm
by wawaii
楼主解决了吗?
我用1.5.4也遇到了同样的问题。
但相同的bin文件烧到nodeMCU的开发板上可以工作,在我们自制的板上就会出现这个问题。

Re: 升级SDK到2.0后不断重启应当如何解决?

Posted: Fri Aug 12, 2016 3:05 pm
by haojinghuan
我也遇到这个问题了,我用mqtt下的历程,烧录,第一次运行正常,断电之后就一直不停输出大量乱码,不知道是复位还是什么。其余的例子下载都很正常。

Re: 升级SDK到2.0后不断重启应当如何解决?

Posted: Fri Aug 12, 2016 3:45 pm
by ESP_Rubin
将eagle.irom0text.bin烧录地址改为0x10000试试

Re: 升级SDK到2.0后不断重启应当如何解决?

Posted: Fri Aug 12, 2016 11:51 pm
by wsptr
这个问题解决了,原因是esp_init_data_default.bin和blank.bin烧的地址不对。这两个文件需要根据使用的Flash的大小确定烧写的位置。我的ESP8266外接的是1MB的Flash,所以esp_init_data_default.bin烧到0xFC000,blank.bin烧到0xFE000。另外eagle.irom0text.bin烧录地址确实应该是在0x10000,之后就一切正常了。