ideaspark® ESP32 Development Board 16MB Integrated 1.9 inch ST7789 170x320 TFT LCD Display,WiFi+BL Wireless Module,CH340 Driver USB Type-C for Arduino Micropython

Once I found the rightbflash program, it worked flawlessly for what I intended it for. Solo bitmining. *Note* USB-C to USB-C doesn't work to power on, I needed USB-A to USB-C. Will definitely be buying more. They will look awesome on my desk at work and wall at home.

I bought a couple of these and had only the usual difficulty plugging the module into a standard solderless breadboard. Getting all 30 pins inserted into a breadboard, particularly a new one, takes patience, but the pin spacing is correct so this is no worse than any other ESP32. The module is wide enough that to make connections to the GPIO pins it's easiest to combine two breadboards, side by side (see photo). I've gotten the display working with the Adafruit TFT libraries and look forward to using the display for viewing real time trace messages of what's going on inside the ESP32. This should be a big help in debugging and, with 16MB of flash, there will be room for lots and lots of code. Or, maybe, have a couple of these around the house to show real-time status of the home security system I'm going to build. Someday soon ....

Ok I have been having a problem with this board becasue GPIO2 Shares the WIFI with the DC on the Display Port. After working a day and a 1/2 with ChatGPT, we have found a work around that is not hard to fix. When doing your sketch you need to run the WIFI command first and then do the display work after it connects, if you do not do this the display locks up and the board goes into constant reboots. Here is an example. // ✅ WiFi FIRST (CRITICAL for your board) WiFi.mode(WIFI_STA); WiFi.setSleep(false); WiFi.begin(ssid, password); Serial.print("Connecting to WiFi"); while (WiFi.status() != WL_CONNECTED) { delay(500); Serial.print("."); } Serial.println(); Serial.println("WiFi Connected"); // ✅ Lock GPIO2 AFTER WiFi is done with it pinMode(2, OUTPUT); digitalWrite(2, HIGH); // ✅ Backlight pinMode(32, OUTPUT); digitalWrite(32, HIGH); // ✅ Display init AFTER WiFi tft.init(); tft.setRotation(1); tft.fillScreen(TFT_BLACK); tft.setTextColor(TFT_YELLOW, TFT_BLACK); tft.setTextSize(2); tft.setCursor(10, 10); tft.println("WiFi OK"); tft.println(WiFi.localIP()); Chat GPT also had me add a 10K Ohm resister between the 3.3v pin and the D2 pin WiFi briefly pulls GPIO2 into unstable states during RF startup The 10kΩ pull-up keeps DC from floating Keeps the display in DATA mode instead of random COMMAND mode Prevents the freeze most of the time Now to be honest, I did this before we tried the code to start WIFI first, so you may not need this. But with this board D2 being tied to the WIFI and the display was a bad Hardware mistake. The displays DC should have been tied to pin D16 or something that is not tied to the wifi. Needless to say the board works great now after figuring that out.

Solid product. Was able to quickly roll out my RFID application using this kit.

You know how when you buy a quality item, and you go on to uncover nice features you didn't think of? Well, this ain't that. It might be in a negative way. First it looks like it fits those dev boards. Did you count the pins to be sure? I thought matching the count and pins would work? It will not. Prepare for this board to not actually fit anything you have - except the most obtuse proto board. THE WORST part is that I cannot get WiFi to work, unless there's a serial cable (monitor) connected and listening. The other ESP32s don't do that. I have no idea what the connection is, but this board's wifi requires an active monitor (???) and is utter garbage. Save yourself the headache, buy a cheaper ESP32 and a separate display - you will not be sorry. Avoid this awful thing.