Has anyone had this problem:
I can upload the BLE_notify sketch to my Node MCU board but get an error message when I attempt uploading to my Doit board:
” Failed to execute script esptool the selected serial port Failed to execute script esptool”
I’ve attempted reassigning port numbers and changing transfer speeds.
Also with the BLE_notify sketch running on the Node MCU board, my Galaxy 8 only once and briefly recognized the ESP32 as a client. I attempted changing physical locations to rule out any type of electrical interference.
Does that error message happen with all the sketches that you try to upload? Can you try upload a different sketch?
Thanks!
The same error occurs with all the sketches using the DOIT board but not the Node board.
I have used the DOIT board for the Web Server sketch and it performed as expected.
It sounds like you have the CP210x driver missing for the DOIT board.
Did you install it? Do you see a new COM Port available when you plug the ESP32 to your computer?
Yes I can see the driver in my device manager. I did some further internet searches. This fixed the uploading issue:
Hold down the EN and BOOT button, click on the Arduino UPLOAD icon. at the Arduino message “connecting….” release the EN button, then release the BOOT button.
Now that I get the sketch to upload, I do not see the ESP BLE server on the nRF Connect Application nor on the Galaxy 8 Bluetooth connection screen (I do see other connected devices). I do not see that anyone else has reported that. Any ideas?
Thanks for letting me know. I think newer boards don’t come with a circuit that automatically puts the ESP in flashing/uploading mode.
You don’t even need to press the EN button. You just need to hold down the BOOT button when you start seeing the message “connecting….” and your ESP should go into flashing mode.
I’ve added those instructions to the course that was just updated today: https://rntlab.com/module-1/learn-esp32-welcome/
Or here (at the end there’s a section “Troubleshooting Tip #1”): https://rntlab.com/installing-the-esp32-board-in-arduino-ide-windows-instructions/
What do you see in your Arduino IDE serial monitor?
(Restart your ESP32 board and let it run for a few seconds, let me know what you see there)
For the MCU board the monitor reads and repeats over and over:
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:812
load:0x40078000,len:0
load:0x40078000,len:11572
entry 0x40078a5c
Brownout detector was triggered
The DOIT board serial monitor reads (only one transmission):
ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:812
load:0x40078000,len:0
load:0x40078000,len:11572
entry 0x40078a5c
For the DOID board I need to press the EN button to start the program after the sketch is uploaded. Also the transmission only runs once and then stops whereas the MCU board the transmission continuously runs
Hello Thomas, that error message:
Brownout detector was triggered
Means that the ESP is constantly crashing and rebooting. That often happens with a bad USB cable or when the ESP32 is not running with enough power (causing a constant crash)…
Looks like you are right again. A new cable was the trick to get the sketch to properly upload. I must still be doing something wrong. The monitor indicates it is “Waiting a client connection to notify…” nRF Connect shows the counting activity, but the monitor is not showing the counting. I open the monitor after the sketch is uploaded. I’ve tried opening it before uploading the sketch. I have the baud set at 115200. Any thoughts why the monitor is not showing the counting?
Those problems are very frustrating, but for some USB cables don’t give a good connection to the ESP built-in USB connector or something and results in that problem.
If you see the number increasing in the nRF connect and if it’s ESP is connected to the app, I don’t have any idea why it’s not printing in the Serial monitor… It should definitely be printing that message