ESP8266 Community Forum

I have a 12E Module (on an ElectroDragon breakout board R2)
I've successfully interfaced with a terminal program (Mac CoolTerm) and played with the AT+ codes.
I've also used esptool to update flash the 12E, to a newer version of the AT cmd set just to verify that I could successfully flash the device. Tested AT+ cmds again, no problems.

I've added the boards package for the ARDUINO IDE and opened the WiFiScan Example program.
I was able to compile and successfully (?) flash the 12E with the program. It completes successfully, it appears.

My problem is that the module does continuous reboots. The WiFiScan example sets baud rate to 115k, but I see in the serial window continuous junk.
I tried other baud rates, and see that this junk spew is at 78k and is a constant restart message over and over. Occasionally I see the WiFiScan msgs interspersed (if I'm at 115k) but still constant reboots.

I see the reboot reason code is 1 - ie power reset.

I assumed the board wasn't getting enough current from the USB feed from my FTDI 5V output, so I used a separate external supply capable of an amp or so, and powered it up with that. It looks like it's drawing 70-80mA before cycling back to zero (not sure meter is catching the peak spike).

Any thoughts on why I can't run even this simple sketch without reboots? Is it a defective 12E? I've built the code for both "generic 8266 module' and also for "nodeMCU 1.0 (12E)" with similar results.
I also tried using the cmdline esptool to erase flash before using the Arduino IDE to load the code, with same results.

Running Arduino IDE 1.6.9 and the 'stable' version of the 8266 boards directory.

-Thx for any hints.
- Ross.

The clue is this section "and see that this junk spew is at 78k and is a constant restart message over and over." If what you say is accurate then the most likely issue is that you did not correctly flash the module with your code. The 78k data rate is the default data rate for the serial loader. The two ways to get there and be stuck is when you don't flash a valid image and the IO pins are not pulled up correctly to prevent the module from jumping to the boot loader. Since you've run code before I suspect the pins are in the proper state and that the flash image is toast.