-->
Page 2 of 3

Re: How can floating GPIO2 pin damage the controller?

PostPosted: Sun Sep 13, 2020 12:09 pm
by indrek84
Thank you all for the responses!

As I understand, it is OK to leave the GPIO2 floating, although it is best practice to pull it up to VCC with a resistor.

The note under the boot mode table probably wanted to say that you should use a resistor rather than making a direct connection to VCC.
But probably due to some unfortunate edits to the sentence, it currently says that leaving GPIO2 floating is dangerous.

Re: How can floating GPIO2 pin damage the controller?

PostPosted: Wed Sep 16, 2020 1:03 pm
by eriksl
It IS dangerous, but in another way, the state is undefined so it may leave you with an esp8266 that won't boot, in that sentence.

Re: How can floating GPIO2 pin damage the controller?

PostPosted: Wed Sep 16, 2020 4:32 pm
by btidey
GPIO0, GPIO2, GPIO15 that determine boot mode are internally pulled up (through ~36K) during the boot phase at the point they are tested.. They are not intrinsically floating at this point.

For normal operation these must be high, high, low, So GPIO15 is the only one that must be pulled low by an external resistor e.g. 4k7 to 0V. Of course if either GPIO0 or GPIO2 is connected to an external circuit then this must ensure they are high during the reset boot phase.

Re: How can floating GPIO2 pin damage the controller?

PostPosted: Thu Sep 17, 2020 4:36 am
by eriksl
That may not be the cause with all models. The pull-up is not in the ESP8266 itself anyway, so you'll have to rely on the boards manufacturer. I'd advise to always use a pull-up. I've had contexts where I really needed to have them to get it working.