WROOM02 - Always in reset mode - never entering Application
Posted: Thu Feb 16, 2017 2:07 pmI've embedded a WROOM2 on to another cpu board.
The second cpu does the programming. I have implemented the protocol used by most of the stand-alone flashers - I do not think I have an issue there.
I am using the latest RTOS SDK with a simple program that acquires AP's as a test.
Reset is clean - no glitches - and has an RC circuit to the pin.
The following is a snippet of the output acquired from UART1.
ets Jan 8 2013,rst cause:1, boot mode:(3,6)
load 0x3ffe8000, len 928, room 16
tail 0
chksum 0x94
load 0x3ffe83a0, len 872, room 8
tail 0
chksum 0xb8
load 0x40100000, len 29340, room 8
tail 4
chksum 0xb1
csum 0xb1
OS SDK ver: 1.5.0-dev(950076a) compiled @ Nov 4 2016 19:29:32'254'
ets Jan 8 2013,rst cause:1, boot mode:(3,6)
load 0x3ffe8000, len 928, room 16
tail 0
chksum 0x94
load 0x3ffe83a0, len 872, room 8
tail 0
chksum 0xb8
load 0x40100000, len 29340, room 8
tail 4
chksum 0xb1
csum 0xb1
OS SDK ver: 1.5.0-dev(950076a) compiled @ Nov 4 2016 19:29:32'254'
ets Jan 8 2013,rst cause:1, boot mode:(3,6)
load 0x3ffe8000, len 928, room 16
tail 0
chksum 0x94
load 0x3ffe83a0, len 872, room 8
tail 0
chksum 0xb8
load 0x40100000, len 29340, room 8
tail 4
chksum 0xb1
csum 0xb1
OS SDK ver: 1.5.0-dev(950076a) compiled @ Nov 4 2016 19:29:32'254'
This continues forever.....
Question 1 -- How do I interpret the "tail" and "chksum" values to see if they are telling me an error exists?
Question 2 -- How do I interpret the "load" and "length" and "room" values to see if they are telling me an error exists?
Question 3 -- what should be the proper SPI memory size used in the flasher tool?
I experienced similar resetting issues when working with other ESP platforms (ESP-12, ESP-07, ESP12E NodeMcu) and resolved it by changing the flash size parameter of the flashing tool.
The WROOM02 documentation states that the SPI flash memory is a 2M device -- I'm using that as the flash tool parameter.
The same program runs on a ESP12-E NodeMcu that I use for testing with standard flash tools to program it - making me believe there is no code related issue.
Any thoughts or comments on what's happening and how to resolve it - please.
Thanks.
Joe
The second cpu does the programming. I have implemented the protocol used by most of the stand-alone flashers - I do not think I have an issue there.
I am using the latest RTOS SDK with a simple program that acquires AP's as a test.
Reset is clean - no glitches - and has an RC circuit to the pin.
The following is a snippet of the output acquired from UART1.
ets Jan 8 2013,rst cause:1, boot mode:(3,6)
load 0x3ffe8000, len 928, room 16
tail 0
chksum 0x94
load 0x3ffe83a0, len 872, room 8
tail 0
chksum 0xb8
load 0x40100000, len 29340, room 8
tail 4
chksum 0xb1
csum 0xb1
OS SDK ver: 1.5.0-dev(950076a) compiled @ Nov 4 2016 19:29:32'254'
ets Jan 8 2013,rst cause:1, boot mode:(3,6)
load 0x3ffe8000, len 928, room 16
tail 0
chksum 0x94
load 0x3ffe83a0, len 872, room 8
tail 0
chksum 0xb8
load 0x40100000, len 29340, room 8
tail 4
chksum 0xb1
csum 0xb1
OS SDK ver: 1.5.0-dev(950076a) compiled @ Nov 4 2016 19:29:32'254'
ets Jan 8 2013,rst cause:1, boot mode:(3,6)
load 0x3ffe8000, len 928, room 16
tail 0
chksum 0x94
load 0x3ffe83a0, len 872, room 8
tail 0
chksum 0xb8
load 0x40100000, len 29340, room 8
tail 4
chksum 0xb1
csum 0xb1
OS SDK ver: 1.5.0-dev(950076a) compiled @ Nov 4 2016 19:29:32'254'
This continues forever.....
Question 1 -- How do I interpret the "tail" and "chksum" values to see if they are telling me an error exists?
Question 2 -- How do I interpret the "load" and "length" and "room" values to see if they are telling me an error exists?
Question 3 -- what should be the proper SPI memory size used in the flasher tool?
I experienced similar resetting issues when working with other ESP platforms (ESP-12, ESP-07, ESP12E NodeMcu) and resolved it by changing the flash size parameter of the flashing tool.
The WROOM02 documentation states that the SPI flash memory is a 2M device -- I'm using that as the flash tool parameter.
The same program runs on a ESP12-E NodeMcu that I use for testing with standard flash tools to program it - making me believe there is no code related issue.
Any thoughts or comments on what's happening and how to resolve it - please.
Thanks.
Joe