I'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 (esptool.py) - 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'
This continues forever..... as if a continuous loop.
Question 1 -- Can someone explain this behavior?
Question 2 -- How do I interpret the "tail" and "chksum" values to see if they are telling me an error exists?
Question 3 -- How do I interpret the "load" and "length" and "room" values to see if they are telling me an error exists?
Question 4 -- what should be the proper SPI memory size used in the flasher tool? -- I currently using 2M
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.
I have taken another board where I have not yet programmed the ESP. I wanted to make sure I did not have a hardware circuit design issue -- I don't think I do as the following is the debug text from a virgin WROOM02 booting in my embedded board
Decoded Protocol Result
ets Jan 8 2013,rst cause:1, boot mode:(3,6)
load 0x40100000, len 2408, room 16
tail 8
chksum 0xe5
load 0x3ffe8000, len 776, room 0
tail 8
chksum 0x84
load 0x3ffe8310, len 632, room 0
tail 8
chksum 0xd8
csum 0xd8
2nd boot version : 1.6
SPI Speed : 40MHz
SPI Mode : QIO
SPI Flash Size & Map: 16Mbit(512KB+512KB)
jump to run user1 @ 1000
Thanks.
Embedded WROOM02 - Never Jumps to User code
Who is online
Users browsing this forum: No registered users and 60 guests
Login
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
Latest SDK
Documentation
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!
- All times are UTC+08:00
- Top
- Delete all board cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. We are the manufacturer of ESP8266EX.