ESP8266 Developer Zone

Re: Initial loading of AT firmware on blank flash

2014-12-23T20:37:44+08:00

Is this problem solved now?

Statistics: Posted by ESP_Faye — Tue Dec 23, 2014 8:37 pm

Re: Initial loading of AT firmware on blank flash

2014-11-20T06:23:53+08:00

Wow! Will test immediately.

Statistics: Posted by guan — Thu Nov 20, 2014 6:23 am

Re: Initial loading of AT firmware on blank flash

2014-11-19T02:36:57+08:00

SOLVED!!
SEE =======> viewtopic.php?f=7&t=25&p=70#p70

Statistics: Posted by costaud — Wed Nov 19, 2014 2:36 am

OT: please include pictures without https / or validate

2014-11-15T19:50:22+08:00

hi guan
OT:
it seams there is no valid / right https certifikate or binding to your https ...
can u please change your https to http - or validate your https?
append not valid zertifikates is not possible .. understand please -
and will allways show placeholder in IE like i attached.

can try

Code:

https://guan.dk/

write to

Code:

https://www.guan.dk/

but this not helps here.

txs!
rudi

Statistics: Posted by rudi — Sat Nov 15, 2014 7:50 pm

Re: Initial loading of AT firmware on blank flash

2014-11-15T05:54:48+08:00

Ah, thanks. Now I get the same error messages.

I tried both the traditional download tool and the wxPython one. Traditional tool:

wxPython tool:

For both tools, I get this output at 75000 baud:

Code:

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

load 0x40100000  len 612  room 16 
tail 4
chksum 0x12
load 0x3ffe8000  len 788  room 4 
tail 0
chksum 0x50
load 0x3ffe8314  len 264  room 8 
tail 0
chksum 0x4a
csum 0x4a

2nd boot version : 1.1
  SPI Speed      : 80MHz
  SPI Mode       :   SPI Flash Size : 4Mbit
jump to run user1

Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000
Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000
Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000
Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000
Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000

where the last two lines repeat forever:

Code:

Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000

I would be interested if you have an obvious answer. I am also going to try to assemble a second board in case it is a board problem.

Statistics: Posted by guan — Sat Nov 15, 2014 5:54 am

Re: Initial loading of AT firmware on blank flash

2014-11-14T01:19:12+08:00

your download address is not correct.See below

Statistics: Posted by costaud — Fri Nov 14, 2014 1:19 am

Re: Initial loading of AT firmware on blank flash

2014-11-11T02:37:48+08:00

I tried to load the 0.9.1 AT binary. That boots, but doesn’t work. Never mind, I should be at 0.9.2 anyway.

I then tried to load the binary at http://bbs.espressif.com/viewtopic.php?f=5&t=13. It seems to load correctly:

Now it does not appear to boot, Here’s the message from the UART bootloader at 75000 baud:

Code:

 ets Jan  8 2013 rst cause:1  boot mode:(3 7)

ets_main.c

And then nothing happens after that.

I also tried to load using my understanding of how to do the mode without cloud upgrades. I put user1.bin at 0x00000 and eagle.app.v6.irom0text.bin from espressif_iot_esp8266_updated_files_20141024 at 0x40000:

(What is irom0text? Is it something specific to the code that is being loaded, or general to all firmware?)

This results in the following bootloader messages at 75000 baud:

Code:

 ets Jan  8 2013 rst cause:1  boot mode:(3 7)

load 0x40100000  len 23972  room 16 
tail 4
chksum 0xc9
load 0x3ffe8000  len 3136  room 4 
tail 12
chksum 0xa0
ho 0 tail 12 room 4
load 0x3ffe8c40  len 6212  room 12 
tail 8
chksum 0xcb
csum 0xcb
Fatal exception (28): 
epc1=0x402114a8  epc2=0x00000000  epc3=0x00000000  excvaddr=0x040001a2  depc=0x00000000
Fatal exception (28): 
epc1=0x402114a8  epc2=0x00000000  epc3=0x00000000  excvaddr=0x040001a2  depc=0x00000000
Fatal exception (28): 
epc1=0x402114a8  epc2=0x00000000  epc3=0x00000000  excvaddr=0x040001a2  depc=0x00000000
Fatal exception (28): 
epc1=0x402114a8  epc2=0x00000000  epc3=0x00000000  excvaddr=0x040001a2  depc=0x00000000
Fatal exception (28): 
epc1=0x402114a8  epc2=0x00000000  epc3=0x00000000  excvaddr=0x040001a2  depc=0x00000000

Where the last two lines repeat forever.

Statistics: Posted by guan — Tue Nov 11, 2014 2:37 am

Re: Initial loading of AT firmware on blank flash

2014-11-07T03:18:14+08:00

Thanks again. I managed to get the 0.9.1 AT firmware loaded. Now there’s another problem, and one with 0.9.2, which I’ll try to debug.

Statistics: Posted by guan — Fri Nov 07, 2014 3:18 am

Re: Initial loading of AT firmware on blank flash

2014-11-05T02:31:39+08:00

20 MHz might be too slow...

try choosing 40Mhz or 80mhz and dout mode for w25x series.

Statistics: Posted by costaud — Wed Nov 05, 2014 2:31 am

Re: Initial loading of AT firmware on blank flash

2014-11-05T02:02:53+08:00

costaud wrote:
Mention that W25X series flash do not support quad i/o mode , please TRY CHOOSING "DOUT" IN THE CONFIG PANEL.

Many thanks for pointing this out. I switched it to DIO and the flash speed to 20 MHz just in case that was an issue. Here’s what I get:

Code:

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

load 0x40100000  len 612  room 16 
tail 4
chksum 0x12
load 0x3ffe8000  len 788  room 4 
tail 0
chksum 0x50
load 0x3ffe8314  len 264  room 8 
tail 0
chksum 0x4a
csum 0x4a

2nd boot version : 1.1
  SPI Speed      : 20MHz
  SPI Mode       : DIO
  SPI Flash Size : 4Mbit
jump to run user1

Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000
Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000
Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000
Fatal exception (0): 
epc1=0x401001a2  epc2=0x00000000  epc3=0x00000000  excvaddr=0x00000000  depc=0x00000000

It seems that the second stage bootloader runs, so that’s some progress. The last two lines with Fatal exception repeat indefinitely. I will try other combinations now to see if anything works.

What setting do you guys usually use for flash speed? Is there anything else that could be wrong?

Statistics: Posted by guan — Wed Nov 05, 2014 2:02 am

Re: Initial loading of AT firmware on blank flash

2014-11-04T08:25:07+08:00

guan wrote:
I should add that my flash chip is W25X40CLSNIG.

Mention that W25X series flash do not support quad i/o mode , please TRY CHOOSING "DOUT" IN THE CONFIG PANEL.

Statistics: Posted by costaud — Tue Nov 04, 2014 8:25 am

Re: Initial loading of AT firmware on blank flash

2014-11-04T03:54:11+08:00

I should add that my flash chip is W25X40CLSNIG.

Statistics: Posted by guan — Tue Nov 04, 2014 3:54 am

Re: Initial loading of AT firmware on blank flash

2014-11-04T02:35:58+08:00

Nice board you got there.

I have started another thread with a similar problem
viewtopic.php?f=7&t=21

Of course I started off with an ESP-01 module and not blank.
hope that we can get this figured out soon.

Fadi

Statistics: Posted by Fadi — Tue Nov 04, 2014 2:35 am

Initial loading of AT firmware on blank flash

2014-11-04T02:19:25+08:00

I have been trying to load the AT firmware onto a fresh PCB that I have designed, and it is not working I am wondering if I am doing anything wrong. Here is my board:

For comparison, I have been using an ESP-01 module I bought from an Aliexpress vendor. I am using a Saleae logic analyzer because my USB-to-UART module is not capable of the 75000 baud that the bootloader talks.

I am using the flash tool and binaries from version 0.9.2 included with espressif_iot_esp8266_development_kit_20140929.

First of all, the flash tool loaded the 4 bin files successfully at the addresses required for the configuration without cloud upgrade:

I took these flash addresses from the document "7-Espressif IOT Flash 读写说明_v0.2.pdf", page 7. I believe that the flash load was successful because there were no error messages, and the tool displayed my chip's MAC address correctly.

Now, the problem is that when I put GPIO0 back to HIGH (with MTDO still LOW and GPIO2 still HIGH), and I try to boot the AT firmware, the AT "ready" message does not start up. Here is what is displayed from my module at 75000 baud:

Code:

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

load 0x40100000  len 612  room 16 
tail 4
chksum 0xef
load 0x00000000  len 0  room 4 
tail 0
chksum 0xef
ho 12 tail 0 room 4
load 0x00000000  len 0  room 12 
tail 0
chksum 0xef
csum 0xef
csum err
ets_main.c

And nothing happens after that.

Here is what is displayed with my Aliexpress module:

Code:

 ets Jan  8 2013 rst cause:1  boot mode:(3 7)

load 0x40100000  len 24236  room 16 
tail 12
chksum 0xb7
ho 0 tail 12 room 4
load 0x3ffe8000  len 3008  room 12 
tail 4
chksum 0x2c
load 0x3ffe8bc0  len 4816  room 4 
tail 12
chksum 0x46
csum 0x46

(After that the AT firmware starts talking at 115200 baud.)

The flash tool appears to have loaded the firmware correctly. My questions are:

Why does it not boot into the AT firmware as it is supposed to?
Why is "boot mode" listed as (3, 6) instead of (3 7) as with my functional Aliexpress module?
I have MTDO=0, GPIO0=1 and GPIO2=1 when I try to boot from flash. Is there something additional I need to do?
Why are the lengths and checksums apparently wrong?
Is there something additional I have to do to make the ESP8266 chip boot from the AT firmware I have loaded?

Statistics: Posted by guan — Tue Nov 04, 2014 2:19 am