1

I am trying to get started with a ESP8266 using Arduino and Sparkfun thing, non dev board. I have cut a trace and an fitted uploading jumper. My FTDI device is one marked 'Deek Rodot'.

I can upload and run programs (blink etc), but if I connect to serial monitor, I have tried Arduino and putty, I get:

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

with the jumper on and 

ets Jan  8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v09f0c112
~ld
È

with the jumper off (after switch off / on)

I've been trying to find a solution for a few days and am wondering if anyone else has gotten through the same problem.

This happens with several different bootloaders I have tried.

Improve this question
35
  • "ets Jan 8 2013,rst cause:2, boot mode:(3,6) load 0x4010f000" etc. is normal, it's the boot loader making itself known (google it). So what is the actual problem your are having? Commented Jul 6, 2016 at 10:32
  • normal ??? not according to other reports i've read on the web, after showing the error in terminal it will go no further i cannot send it AT commands i've been through it with Sparkfun tech who say they have seen the problem before but never offered me an explanation. Commented Jul 7, 2016 at 17:20
  • Well, what I mean is the start looks like a relatively normal ESP boot, and you say that you can upload and run programs, which suggests both serial and the ESP do work. What you pasted is output of the bootloader I think (the bit before your main firmware), admittedly it is rather cryptic, so there might be something wrong in there, but I can't spot any actual error message, tho I'm not sure what v09f0c112 means, everything before it looks like a small program is loaded, blink? Commented Jul 7, 2016 at 18:04
  • Can you possibly describe what you did exactly, in the cleanest example you can think of? Did you erase the flash fully, what parts did you upload to the flash, to which addresses, can you show a screenshot or the command you used, and the name/source of the firmware, bootloader, and other parts you used? You mention AT commands, so I assume you're using the SDK's AT firmware. Which baudrate do you set putty or other clients to? Commented Jul 7, 2016 at 18:06
  • And am I correct when I understand the actual problem you are seeing is that you do not get any (legible) output on the serial port, when running a firmware that should provide output? (SDK's AT firmware, NodeMcu firmware, etc.) and also are not seeing any reaction to input on the serial port? Commented Jul 7, 2016 at 18:08

2 Answers 2

Reset to default
1

I solve this problem by increasing the input power of my breadboard power supply which I use to power my ESP8266-12E with 3.3V. I guess the ESP8266 requires more current to operate properly. Hope this helps.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

According to my GitHub Page You can solve this problem by using timer instead of direct function call. The reason is ESP8266 need to run some commands every 1000 clock so if the function is a callback and it taking too long it needs to break into other function and called by a timer otherwise following error appears.

rst cause:2, boot mode:(3,6)

I suggest that change the title. This is NodeMCU bug (probably not ESP8266 or arduino) in my case at least.

  • Be aware that this is a workaround and absolutely not a solutiion.
Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.