ESP32-DevKitC V4 ESP32 Development Board with USB Cable, ESP32-32D

I have 4 of these and they all work fine when powered by the USB port.I like that they have two models (internal or external antenna) with the same pinouts, so I can swap depending on the installation requirements.-1 star: they don't work when powered via the 5v pin. My program boots, tries to enable WiFi and then reboots (again and again.) I suspect the 5v pin is wired as an output and doesn't use the onboard voltage regulator (5v to 3.3v) that the USB port uses. I have other esp32's that can be powered from the 5v pin. Only removing one star for this, because it just means I have to either do some resoldering on the board or add a usb connector to the ac/dc converter I'm using (search for HLK-PM01 AC-DC 220V to 5V Step-Down Power Supply.)UPDATE 15 Dec 2020: +1 star: It's working now with 5v input (from the HLK-PM01). A google search discovered that starting the WiFi draws more power. The fix is to add 10uF capacitors as close as possible to the 5v and 3.3v pins. I added these to a separate board where the dev board is mounted (along with other components), I didn't try to modify the esp32 dev board itself. The caps provide the short burst of power required. I also added 1uF caps to settle the ripple voltage.Also, as others have noted, these are wider that other dev-kits and on a breadboard only one row of pins is accessible. You can around this by using header blocks to raise it up high enough to get access to the other row of pins. (Search for Female Pin Headers.)

The media could not be loaded. I've put on a video of blink program connecting to I/O Pin 2. This unit does not have an onboard led connected to pin 2, but not a deal breaker for me.Program :int LED_BUILTIN = 2;void setup() {pinMode (LED_BUILTIN, OUTPUT);}void loop() {digitalWrite(LED_BUILTIN, HIGH);delay(1000);digitalWrite(LED_BUILTIN, LOW);delay(1000);}

I read the other reviews, they worried me.When I first got it they didn't work and I thought maybe the reviews were right, but I Google the other and it looks like I just needed some drivers for the chip to show up on the com ports. I don't have a link to them on hand, but as a heads up look in device manager and look under coms, if it doesn't show up when you plug it in, look for drivers. I may update this review if I find the link again.I used this chip for a GitHub project called BlueRetro and it works great with my Nintendo 64.

I have a lot, but not much at all to say about this product.I don't know how many times I've purchased this pack of ESP32s - but it's been a lot.The value you get for two ESP32-DOWD modules is great. These things are solid chips, and flash easily, never had a dud in any of the packs that I've bought.The only downside is that they are 10 pins wide in a 2.54mm/0.1" board. I don't mind it all too much though, because if you've got a solderable board, you can run wires under/around it. Plus, for the price, really not that huge of a problem.10/10 A+

These are the wider ones at 1.1 inch NOT the .9 inch wide. They work great with both Arduino and Micropython. I needed the .9 inch wide ones, but still kept these 1.1 inch wide ones for other projects because I tested them and worked great.

I bought a handful of ESP8266 and ESP32s from different vendors, to test several varieties. I had seen that nearly every seller and product had the occasional dead-on-arrival item review, but I had no DOAs from any order. I prepared for this product by reviewing documentation and reading others' questions/answers, and by reading example programs others wrote.My MELIFE ESP32s both successfully ran test webserver programs after the very simple addition of the board libraries to the Arduino software, a process similar for any board besides the basic Arduino options. Windows 10 did not require any driver installation.

So far so good. These boards work great with the screw terminal break out boards.Headers are pre soldered on bottom.

One out of the two boards did not work, so far! Kept getting "brownout detector was triggered" message which meant either the cable or the power through the usb port is not right or just a plain hardware fault. I put it down to a hardware fault because the other board is signalling properly, so far. Oh and the other thing - you have to keep booting and enabling each time you upload code......how can you design a board like that???? For a beginner hobbyist this is/was frustrating and I won't recommend the boards I received.