Dear Brian, thank you so much for the amazing and useful video tutorial! We added it to our video collection and our documentation. We hope to see more videos about PlatformIO. They are very important for our Community!
Finally got an ESP-PROG. Searched RU-vid. Found your Video. Now I’m all set to go. 🙂 PlatformIO should be grateful. You provide a clear and concise guide that they probably don’t have the time to produce, or that Espressif can even be bothered to provide. Better even than that guy with the the Swiss accent - who I also subscribe to. 👍🏼 Many thanks.
Not sure how, but I've missed this video and just watching it now. PlatformIO is something that I've been eyeing with for a long time, but I haven't yet tried, so this vid is pretty cool to see.
Very helpful tutorial, thank you! I confused VCC with 5V and mistakenly connected VCC from esp-prog to 5V on the ESP32 dev board. It took me a while to realize that VCC is 3.3V. Luckily none of the boards burn. Actually the VCC line should not ne connected at all. I connected both esp-prog and esp32 dev board to the micro USB connectors, so they both get power from USB and then only connected the ground of both boards. Not sure that connecting the grounds is necessary because it is connected through the USB, but I connected them anyhow. Then eventually I was able to debug. I find the debugger very useful but I got various problems that I don't know yet how to overcome. The most annoying problem is that at some point the debugger stops going in "step over" mode and always doing "step into" even if I hit "step over". I still have a long way to go to master this tool, but it seems worth making the effort. Thanks again!
Nice tutorial. Well done. I had some trouble with missing libraries and could not start debug. I checked them at the debug console after hitting f5. After I installed them in the terminal, everything went fine.
Would be great to show the exact wiring setup during upload and debug. It's not clear from your video but I figured it out from reading comments below. Thanks!
Brian, nice clear video and I will have debugging working in a fraction of the time it would have taken me to get this inofrmation on my own. You mention that when the board is connected that sometimes it dosn't load. I have this promblem on one of my boards without anything attached. If I place a 2.2 / 3.3 microfarad capacitor from GND to EN port the problem goes away. It may be that the capacitence of the enable pin is changing when it mounted, or it could be something completley different. It may be worth a try though and if it sorts out the issue, all good. Thanks for the effort you put in.
thank you for the video Brian. I can confirm that upload via JTAG works. However I found putting "build_type = debug" and "debug_init_break = tbreak setup" ini file caused me issues. So I recommend not putting them in at the start. Then work your way from there.
It looks like you don't sell a ESP32 DevKit V1 debug shield? I just made one with a protoboard but I'd rather have a more permanent smaller form factor version.
Thank you Brian, verry helpfull. My experience is, that the hardware setup, especially the connection is very critical. Starting the debugger only worked reliable, when i used very short cables betwenn ESP32 and the debugger. That means: Only direct and short connection with single Dupont cables (10 cm) worked for me. On the other hand, a self-made adapter cable (15 cm) with an IDC connector on the debugger-side and Dupont connectors on the ESP32-side did not work reliable. I have not looked at the specification of the JTAG interface. But I can imagine that there is a timing problem with too long cables. Do you know, if there is a possibility to reduce the JTAG speed to make the communication more robust? I also suspect that the problems during downloading the program via the USB interface are related to the cable length at the JTAG port of the ESP. Maybe the port catches interference via long cables.
BEWARE...If you refer to Zadig::USB ID..The hexadecimal numbers 0403 and 6010 are the USB vendor and product ID of the FT2232HL chip and OpenOCD looks for them. Unfortunately, the FT232H chip has the vendor/product ID 0403/6014.
Brian, thank you for the great tutorial. I am having problems getting the debugger running. When I connect TDI to GPIO 12, the code won't upload. Do you know how I could fix this. I already did the update that you recommended in video.
Brian, many thanks for the video. It's unclear how things are connected. Do you plug both devices into your computer via two separate USB cables? or are you just connecting via a single USB connection through the esp-prog ?
Hey Kieran I've been using two cables, but I think 1 should be ok. Once the code is uploaded, you could plug out the esp32 and plug in the esp-prog. The esp-prog even supplies 3.3v Another commenter mentioned that you can upload via the esp-prog too, but I've never tried it
Disclosure: The pinout for the ESP32-S2 board is different. In my testing, you MUST have both boards connected for debugging to work (shame, thought you could upload over jtag). TDO: GPIO40 TDI: GPIO41 TCK: GPIO39 TMS: GPIO42
Dear Brian. If the Debugger is running, is it possible to see some variable running too at the left tab "watch"? Or ALWAYS, in this condition, the variable content would be "not availabre as has showed in your video? Regards.
Tanks for this guide. Do you think JTAG debugging will be useful for figuring out problems with a sketch half crashing after 6-24 hours of running? (By half crashing I mean, serial monitor and MQTT messages stop sending, but web interface continues to work.)
The ESP32-C3 (Single Risc-V Core) shows it has JTAG/USB support, but can it also be debugged using PlatformIO and even VSCode? Or would the C3 need to be flashed with something that enables SWD debugging? BTW, in terms of debugging, any thoughts between VSCode and Visual Studio + VisualGDB ?
Hi, Brian. I am running by VSCode/PlatformIO on Ubuntu (version 20.04 LTS). Are there any difference in instructions for Linux (except for serial port names)?
@@pankajcooldudeful Sir, you won the Internet today. I've been trying to get my new ESP-PROG to upload the code and this is the first time anyone has ever mentioned this. My eternal gratitude.
I may be missing something obvious, but can't the ESP-PROG power the board to be debugged via the pin you colored red (VCC), meaning you wouldn't have to connect the board itself via USB at all?
Power wise yes, I was connecting both so I could program the board via USB. People have mentioned since it can be done via esp-prog using JTAG but I have never tried it
@@BrianLough Wow, I didn't expect to get a reply to this within the hour! Cheers, thanks a lot for this video and your quick reply. Did you notice any issues with your ESP-PROG clone? Amazon.de does list one genuinely manifactured by espressif, but not sure if it's worth the extra cost
You need to switch the project to `debug` profile ( docs.platformio.org/en/latest/projectconf/build_configurations.html ) . Otherwise, PlatformIO will automatically rebuild your project from "release" into "debug" with each debugging session.
Brian, thanks a lot for this tutorial. Now, I want to share with all of you a little experience that I had when I tried to start the debugging process: This process just didn't start and the debugger console said me that the problem was an error in GDB and OpenOCD settings... After searching for a long time, finally I could found someone who gave me the answer ( ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-fvOzpKJY2gM.html ) and this answer is unexpectedly simple: REMOVE THE JUMPER FROM THE IO0_ON/OFF PINS when you want to use the JTAG port of the ESP-Prog. I hope this information can save time for someone with the same problem
Whoops! Thank you for letting me know! The link to the one I bought is wrong, I'll fix it in a few minutes, but here it is #Aliexpress US $18.00 | ESP-Prog (JTAG Debug & Program Downloader) a.aliexpress.com/_dUyYZGo
I would do a back before doing anything. There is a reasonable chance this will corrupt a Windows system. I lost all keyboard use and had to restore from a restore point and after recovering the system VS studio code would not launch and it required a reinstall of VS. I suspect the drivers that are suggested for download are defective and the lists of drivers don't match those in the video. 2/9/2024 Just be very careful!
Your vid is a bit deceiving. You start of by creating the impression that you only need the JTAG interface but then casually plug in the USB bridge programmer like its no small matter at all. What you should have said is that you need RX0/TX0/EN/BOOT plus JTAG signals on top of that to accomplish this task. I found this to be extremely annoying since if you design a project with RX0/TX0 used for a product interface you are pretty much plucked since you will then have to hack RX0/TX0 lines in order to download code and not cause a meltdown
