Timeline for Arduino nano to esp8266 level shifting needed?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2016 at 23:21 | comment | added | Chris Stratton | It might boot up that way, but all it takes is mistakenly making that pin an output (perhaps while trying to make another pin one) to damage the ESP8266. In the Arduino world, mistakes (especially purely software ones) should be considered normal, so it is unfortunate if one can cause damage. And yes, it is even more a risk with SPI where the MISO pin is even more likely to be used for a different purpose in code that might be loaded with insufficient thought. There's a difference between a cost-optimized solution, and an experimenter-friendly one. | |
| May 9, 2016 at 23:00 | comment | added | SoreDakeNoKoto | @ChrisStratton I dont get what you mean. One would assume that Arduino's RX pin is already configured as an input in firmware, when its used for serial comms. The risk here is no more than the usual when you connect the serial pins of 2 5V devices together. | |
| May 9, 2016 at 18:03 | comment | added | Gerben | Well, that goes for a lot of thing. The same could be said for the MISO pin on an SPI device connected to an Arduino. I've seen any protection on SPI lines, except maybe a resistor. | |
| May 9, 2016 at 17:04 | comment | added | Chris Stratton | Yes, but for signals going in the other direction you have to also do something similarly, or hope that the pin the Arduino is receiving on never accidentally gets configured as an output instead and driven high. | |
| May 9, 2016 at 9:07 | history | answered | Gerben | CC BY-SA 3.0 |