I'm at the very beginning of a project, new to OpenBuilds. I have a 38pin ESP32 from Aitaiao that has the Silicon Labs CP2101 USB to UART chip. The chip is still on the foam packing that it was sent with. No pins are connected. A USB-C cable that came with a Sandisk USB-C SSD drive is plugged into the ESP32 USB-C Port. The USB-A end of the cable is plugged directly into the Motherboard USB port. A red LED is lit on the controller. When I first opened OpenBuilds CONTROL v1.0.376, the only com port shown was COM1 on the motherboard. A driver was downloaded from CP210x USB to UART Bridge VCP Drivers - Silicon Labs. The CP210x_VCP_Windows driver was downloaded and installed on the Windows 10 machine. Now COM3 Silicon Labs USB to UART is one of the drop downs. Using Device Manger, the COM3 port was configured for Baud 115200, 8 bits, No Parity, one stop bit with no flow control. When the Connect button is pressed in OpenBuilds CONTRO, the following is shown in the Log/Serial Console: [15:21:38] [ 3D Viewer ] WebGL Support found! success: this application will work optimally on this device! [15:21:38] [ websocket ] Bidirectional Websocket Interface Started Succesfully [15:21:39] [ update ] Checking for Updates [15:21:40] [ update ] You are already running OpenBuilds CONTROL 1.0.376 [15:21:43] [ connect ] PORT INFO: Port is now open: COM3 - Attempting to detect Controller... [15:21:43] [ connect ] Attempting to detect Controller (1): (Autoreset) [15:21:44] [ connect ] Attempting to detect Controller (2): (Ctrl+X) [15:21:44] [ connect ] Attempting to detect Controller (3): (others) [15:21:47] [ connect ] ERROR!: No Response from Controller - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for troubleshooting information. Closing port COM3 [15:21:47] [ disconnect ] PORT INFO: Port closed I also tried to connect using a macbook without success. Also tried to use a different 38-pin ESP32 without success. To verify serial communication was working, Putty was downloaded and installed on the Windows 10 machine and a connection was made to the ESP32. A stream of data was sent indicating that serial communication was working properly. configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 modeIO, clock div:2 load:0x3fff0030,len:7672 load:0x40078000,len:16432 load:0x40080400,len:3704 entry 0x4008067c I (27) boot: ESP-IDF qa-test-v4.3.3-20220423 2nd stage bootloader I (27) boot: compile time 11:11:52 I (27) boot: chip revision: 3 I (31) boot_comm: chip revision: 3, min. bootloader chip revision: 0 I (38) boot.esp32: SPI Speed : 40MHz I (43) boot.esp32: SPI Mode : DIO I (48) boot.esp32: SPI Flash Size : 4MB I (52) boot: Enabling RNG early entropy source... I (58) boot: Partition Table: I (61) boot: ## Label Usage Type ST Offset Length I (69) boot: 0 phy_init RF data 01 01 0000f000 00001000 I (76) boot: 1 otadata OTA data 01 00 00010000 00002000 I (83) boot: 2 nvs WiFi data 01 02 00012000 0000e000 I (91) boot: 3 at_customize unknown 40 00 00020000 000e0000 I (98) boot: 4 ota_0 OTA app 00 10 00100000 00180000 I (106) boot: 5 ota_1 OTA app 00 11 00280000 00180000 I (113) boot: End of partition table I (118) boot_comm: chip revision: 3, min. application chip revision: 0 I (125) esp_image: segment 0: paddr=00100020 vaddr=3f400020 size=295d8h (169432) map I (195) esp_image: segment 1: paddr=00129600 vaddr=3ffbdb60 size=04474h ( 17524) load I (202) esp_image: segment 2: paddr=0012da7c vaddr=40080000 size=0259ch ( 9628) load I (206) esp_image: segment 3: paddr=00130020 vaddr=400d0020 size=111630h (1119792) map I (614) esp_image: segment 4: paddr=00241658 vaddr=4008259c size=1b568h (111976) load I (660) esp_image: segment 5: paddr=0025cbc8 vaddr=400c0000 size=00064h ( 100) load I (660) esp_image: segment 6: paddr=0025cc34 vaddr=50000000 size=00010h ( 16) load I (680) boot: Loaded app from partition at offset 0x100000 I (680) boot: Disabling RNG early entropy source... GGGGGGGGGGGGuuuuuGrrrrrruuuuurrrrrrrrr uuuuu I would appreciate any suggestions on what to try next or pointers to tutorials or troubleshooting documents that could help
This issue is resolved. After viewing the output from PuTTY, it was evident that the firmware needed to be flashed BEFORE connecting to the device. Once this was done, I could connect to the ESP32. Perhaps this thread will help someone else who tries to Connect first.
