Upload Issues with Arduino IDE and ESP32

I have this esp32 modue "ESP32-C6" https://www.waveshare.com/product/arduino/boards-kits/esp32-c6/esp32-c6-touch-amoled-1.64.htm

I am also using the Arduino IDE to code and upload.

Yesterday I was uploading frequently trying to get one of the samples working.

Then I noticed that the IDE was telling me it was uploaded, when actually it was not uploaded at all. I then used the ESPLaunchPad to flash one of the Rainmaker samples to it to see if that worked and it did.

I then went back to the Arduino IDE and tried to upload. Again, the IDE told me the upload succeeded but in actual fact it did not and the code that ESPLaunchPad uploaded was still there.

I tried holding Boot and then Reset to see if that allowed the IDE to upload. It did not.

I tried holding Boot until I saw "connecting" in the IDE then letting go. No change in behaviour.

I have restarted the PC. No effect.

I have tried just uploading a simple script to turn on the blue light and even that won't upload even though the IDE insists that it did.

It seems as though the Arduino IDE is having the problem given ESPLaunchPad is able to upload.

Any help here would be greatly appreciated.

Thanks

Hi @griegs.

Sometimes people jump to this conclusion when in reality the situation is that the program was uploaded to the board, but the program's behavior does not match what you expected.

You were very wise to try the experiment of uploading a simple sketch program to the board. However, I'm not sure what you mean by "blue light". I'm not familiar with this board, but from looking at the documentation for the board I don't see anything about an LED that can be controlled by the sketch. Please provide a detailed explanation of what you mean by "the blue light".

There is a WS2812c connected to GPIO 8, It does of course require special code to make it blink or do whatever to it.

There is an example under File->Examples->ESP32->GPIO->BlinkRGB

/*
  BlinkRGB

  Demonstrates usage of onboard RGB LED on some ESP dev boards.

  Calling digitalWrite(RGB_BUILTIN, HIGH) will use hidden RGB driver.

  RGBLedWrite demonstrates control of each channel:
  void rgbLedWrite(uint8_t pin, uint8_t red_val, uint8_t green_val, uint8_t blue_val)

  WARNING: After using digitalWrite to drive RGB LED it will be impossible to drive the same pin
    with normal HIGH/LOW level
*/
//#define RGB_BRIGHTNESS 64 // Change white brightness (max 255)

// the setup function runs once when you press reset or power the board

void setup() {
  // No need to initialize the RGB LED
}

// the loop function runs over and over again forever
void loop() {
#ifdef RGB_BUILTIN
  digitalWrite(RGB_BUILTIN, HIGH);  // Turn the RGB LED white
  delay(1000);
  digitalWrite(RGB_BUILTIN, LOW);  // Turn the RGB LED off
  delay(1000);

  rgbLedWrite(RGB_BUILTIN, RGB_BRIGHTNESS, 0, 0);  // Red
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, RGB_BRIGHTNESS, 0);  // Green
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, 0, RGB_BRIGHTNESS);  // Blue
  delay(1000);
  rgbLedWrite(RGB_BUILTIN, 0, 0, 0);  // Off / black
  delay(1000);
#endif
}

I do have an example that uses the RMT peripheral directly but that has a lot of other code in it and i don't have time right now to clean it up.

There is also a BLUE LED on GPIO 15
try

const byte ledpin = 15;
uint16_t ms = 100;
bool increase = true;


void setup() {
  pinMode(ledpin, OUTPUT);
}


void loop() {
  digitalWrite(ledpin, HIGH);
  delay(ms);
  digitalWrite(ledpin, LOW);
  delay(ms);
  if (ms > 250) increase = false;
  if (ms < 20) increase = true;
  if (increase) ms = (ms * 10) / 9;
  else ms = (ms * 9) / 10;
}

We can't see what you see, post the verbose log in a < CODE/ > block.
BTW, the first upload should be the blink sketch for that board (maybe post a screen shot of the board selector like this