Unable to upload and debug the Blink code on ESP32 S3

[Saad01]

I have been trying to run simple default blink code on ESP32 S3 using Arduino Project Wizard.
I am using only usb for the debugging.
But it keeps saying unable to load failed while trying to start flasing code and debug.

The same debugging step worked on esp idf.
But can’t even be able to upload the code and debug .
Can you please help..

[bflannery]

You may have already seen this, but this tutorial has some helpful info. https://visualgdb.com/tutorials/arduino/esp32/spiffs/

• This reply was modified 1 year, 8 months ago by bflannery.

[Saad01]

ok Iam gonna try, but which i am facing load failed error while trying to click on start button on esp32 s3 ?

[Saad01]

By the way, same error facing

[support]

Unfortunately, it is hard to suggest anything specific based on the description you provided.
In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
Please provide complete and detailed steps to reproduce the issue as described below:

1. The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
2. Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch. See this page for more information and detailed examples.
3. The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.

You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.

[Saad01]

Please check this. I have uploaded the video.

https://drive.google.com/file/d/1dR7ITP7Y-n–W6IEc_WoZxCY6qpiFbnn/view?usp=sharing

[support]

Hi,

This looks just fine. The program has been uploaded and started.  The errors shown by OpenOCD should not prevent it from working.

You can double-check it by setting a breakpoint inside loop() – it should trigger soon after the program has started.

That said, please make sure that you do not modify the original sample code in any way until you confirm that you can debug it. Changing some parameters (e.g. controlling JTAG pins directly) would indeed stop debugging from working.

[Saad01]

but the led is not blinking & program is not flashed

• This reply was modified 1 year, 8 months ago by Saad01.

[support]

If the breakpoint is working, the FLASH should be programmed just fine (otherwise that code would never get executed).

If the LED is still not blinking, it’s something for you to figure out. All VisualGDB does is builds the code from the Arduino examples using Arduino build rules, and runs the result on the target using the ESP32 debugging tools. VisualGDB does not understand the code it is building/debugging and cannot fix it, or check that it makes sense for a particular target.

[Saad01]

The issue is if i just flash the program via the com port, code uploads, led blinks.
but if i try to do this on the debugger , it doesn’t work at all.
It’s at arduino wizard only

[support]

This could be a bug in the Arduino framework, Espressif’s build of OpenOCD. You can try running OpenOCD and gdb manually to debug the same code – if the problem persists, the issue is caused by these tools, and using VisualGDB to launch them will not automatically fix the issue.

 

[Saad01]

is there any way, flashing the code via com port, then manually debug the process through usb without uploading again?
Iam new to this

[support]

We can point it out for you, however it would go through a different queue with a current turnaround of 2 business days. If you would like to get it done faster, please consider looking through the pages of VisualGDB Project Properties – most settings are placed very intuitively there.

[Saad01]

i will be waiting.

[support]

Hi,

Please find the answers to your questions below:

1. You can program the memory via COM port by right-clicking on the project in Solution Explorer and selecting “Program FLASH Memory“
2. You can prevent VisualGDB from programming FLASH memory during debugging via VisualGDB Project Properties -> Debug Settings -> Program FLASH Memory -> Never.

[Author]

Posts