WOW....you have just saved my day! Followed the steps and my board is blinking. I now know its connected and takes programs. A++ for this video. Thanks a bunch
no, it didnt work, in my case (esp32 wroom_v1) this is what worked for me: int LED_BUILTIN = 2; void setup() { pinMode (LED_BUILTIN, OUTPUT); } void loop() { digitalWrite(LED_BUILTIN, HIGH); delay(1000); digitalWrite(LED_BUILTIN, LOW); delay(1000); }
@@ichbinderroboter The BLUE LED is controlled by pin 2 when WiFi not configured. Pin 1 is the TXD0 pin, so you do NOT want to configure that as an LED controller, because in fact, with cycling pin 1 (TXD0) a person may have a problem reprogramming their board due to it being flip flopped by prev. code. Or was that your Point? LOL Are you one of those guys who, back in the day, told people to hold the CTRL +F4 key on their computers? ROFL NOT THAT I'VE EVER DONE THAT! _cough cough cough_ 😉😁
After spending hours to pull my hair, I realized the cable I was using was not able to transfer data and was not visible as /dev/ttyUSB0. Make sure you have a correct cable...
Thank you for the tutorial video! For 'ESP-WROOM-32', I had to keep the 'boot' button on my board pressed while flashing the program; otherwise the flashing process gave an error "Failed to connect to ESP32".
@@gerdsfargen6687 Now that's interesting. I too saw that pin 2 for the built in BLUE LED. What's interesting on my 38-pin WROOM boards, is that LED_BUILTIN is not declared as part to the compiler like it is for Arduinos and perhaps other ESP boards. If you try to compile it with just digitalWrite(LED_BUILTIN,!digitalRead(LED_BUILTIN)); the compiler fails, complaining that LED_BUILTIN was not declared. So either I have to just use 2 or declare it first. Also, it's useless, at least on the boards I have. The BLUE LED is used for WiFi (radio communications of any kind) so it's on a lot and/or high speed flashing during major data send/receive. Fun times.
I believe you are correct. But I haven't done this myself yet. Sometimes inverted logic is used, but I don't think so here. I think he simply misspoke.
WOW....you have just saved my day! Followed the steps and my board is blinking. I now know its connected and takes programs. A++ for this video. Thanks a bunch
Thx, just starting with ESP. Helped a lot! Deserves a like :D
Thank you. Just what I needed to figure out pinouts.
Thanks for you help, worked perfectly
no, it didnt work, in my case (esp32 wroom_v1)
this is what worked for me:
int LED_BUILTIN = 2;
void setup() {
pinMode (LED_BUILTIN, OUTPUT);
}
void loop() {
digitalWrite(LED_BUILTIN, HIGH);
delay(1000);
digitalWrite(LED_BUILTIN, LOW);
delay(1000);
}
For the 38 Pin version you need to use LED_Builtin = 1
@@ichbinderroboter yes, thats true 👍
@@ichbinderroboter THANK YOU very much
@@ichbinderroboter Thanks!
@@ichbinderroboter The BLUE LED is controlled by pin 2 when WiFi not configured.
Pin 1 is the TXD0 pin, so you do NOT want to configure that as an LED controller, because in fact, with cycling pin 1 (TXD0) a person may have a problem reprogramming their board due to it being flip flopped by prev. code.
Or was that your Point? LOL
Are you one of those guys who, back in the day, told people to hold the CTRL +F4 key on their computers? ROFL
NOT THAT I'VE EVER DONE THAT! _cough cough cough_ 😉😁
After spending hours to pull my hair, I realized the cable I was using was not able to transfer data and was not visible as /dev/ttyUSB0. Make sure you have a correct cable...
Thanks man, this helped!
Thank you for the tutorial video!
For 'ESP-WROOM-32', I had to keep the 'boot' button on my board pressed while flashing the program; otherwise the flashing process gave an error "Failed to connect to ESP32".
thanks man, that was helpful
That's strange...my 2022 wroom esp32 doesn't require this yet doesn't blink the on-board led despite defining the builtin as 2.
@@gerdsfargen6687 Now that's interesting. I too saw that pin 2 for the built in BLUE LED.
What's interesting on my 38-pin WROOM boards, is that LED_BUILTIN is not declared as part to the compiler like it is for Arduinos and perhaps other ESP boards.
If you try to compile it with just digitalWrite(LED_BUILTIN,!digitalRead(LED_BUILTIN)); the compiler fails, complaining that LED_BUILTIN was not declared.
So either I have to just use 2 or declare it first.
Also, it's useless, at least on the boards I have. The BLUE LED is used for WiFi (radio communications of any kind) so it's on a lot and/or high speed flashing during major data send/receive.
Fun times.
What do you mean with HIGH to turn off but LOW to turn on? I'm confused and not sure if i should switch to ESP if it is this unintuitive...
I believe you are correct. But I haven't done this myself yet. Sometimes inverted logic is used, but I don't think so here. I think he simply misspoke.
What programmer do you suggest
Thank you bro
How do I make it stop it just keeps blinking
unplug it or flash another code that doesn't make it blink
bro u sayed turn off and you used high -_-