This post is for you if you can get the esp32 blink project to load and run and blink the blue light, but debugging with hardware is a problem, and using printf has issues with the “monitor.”<\/p>\n\n\n\n
I was able to get the blink program to run under Arduino, but debugging was a pain.<\/p>\n\n\n\n
With the older ESP32, you have to use an external JTAG Debugger. Unfortunately, the latest ESP32 units cannot handle classic bluetooth.<\/p>\n\n\n\n
Quick Note: VSCodium will work with platformio, but the clangd massively errors out. I was getting 18 to 36 errors from clangd (similar in features to Intellisense C\/C++), along with no ability to look at library header files (even though the compile was error free). Switching to VSCode fixed that. Turn off Telemetry if you use VSCode (in settings), unless you are ok with MS getting real time snapshots of what you are doing.<\/p>\n\n\n\n
Under PlatformIO, I loaded the bluetooth example and had garbage print on the “monitor” before the Serial.println() came out, when using a classic bluetooth example project. I never saw that with the standard blink project.<\/p>\n\n\n\n
I saw several posts out there that had that particular issue. The solution for me was to add a couple of lines to the platform.ini file for my esp32 board. Those lines are monitor_dtr and monitor_rts. Once I did this, it appeared to stop the garbage printing before my debug printf() lines were able to print my messages.<\/p>\n\n\n\n
Inside the PlatforIO.ini file for jlink:<\/p>\n\n\n\n
[env:esp32doit-devkit-v1]\nplatform = espressif32\nframework = arduino\nboard = esp32doit-devkit-v1\nmonitor_speed = 115200\nmonitor_dtr =0\nmonitor_rts = 0\n# JLINK to ESP32 pins\n# Signal. JlinkPin ESP32Pin\n# TDI. 5 D12\n#. TMS. 7 D14\n# TCK. 9 D13\n#. TDO. 13. D15\n#JLINK CAN INTERRUPT. PROG2 CAN also\ndebug_tool = jlink\n#leave upload_protocol undefined to use UART upload\nupload_protocol = jlink<\/code><\/pre>\n\n\n\nNOTE1: (deja vu:) If jlink does not initially work to upload or debug, upload a beginning program to the ESP32 using the serial port. I use the arduino Blink example for my board, because there is an LED on it.<\/p>\n\n\n\n
NOTE2: If you have a SECOND VSCode (or VSCodium) window open, jlink debugging will fail. I have also seen esp-prog2 debugging fail. Close VSCode or VSCodium and run a terminal window. In the terminal, run <\/p>\n\n\n\n
ps ax | grep code<\/code><\/pre>\n\n\n\nIf you see a lot of <\/p>\n\n\n\n
12632 ?? S 0:01.42 \/Users\/me\/.platformio\/penv\/bin\/python -m platformio -c vscode home --port 45359 --host 127.0.0.1 --session-id 1977e5a6f3ba6a985ea3fa538cad367ec1382c6c --shutdown-timeout 3600 --no-open\n<\/code><\/pre>\n\n\n\nthen use <\/p>\n\n\n\n
kill 12632<\/code><\/pre>\n\n\n\nto stop those python sessions, where 12632 is the number at the far left of the line that grep showed. Run VSCod* again and then you should be able to debug.<\/p>\n\n\n\n
Currently Programmed ESP being Repurposed<\/h3>\n\n\n\n
For some reason, a lot of the programs available for the ESP32 seem to disable jlink. This may be due to a pin being use as an output (where JTAG needs it as an input), and the reset on the EN line may or may not overcome that preset. It could also be that jlink sees activity and refuses to operate. (I have also been able to use the “boot” button, but that is a pain and not always available or reliable.)<\/p>\n\n\n\n
To fix this, upload the blink program (or the hello world program) over the usb serial port and restart the esp32. You may or may not need to restart VSCode. VSCode can get lost to the point the whole machine needs to be rebooted. The upload of a simple demo progarm has fixed jlink debugging for me nearly every time.<\/p>\n\n\n\n
Once the garbage printout was resolved, I started working on debugging hardware. Note that garbage is probably due to the echo of the Serial Port firmware update. Once you switch to jlink or esp-bridge (or esp-builtin) the garbage does not seem to show up. The PlatformIO still has a way to go.<\/p>\n\n\n\n
I used jumper wires to go from the jlink connector to the ESP32 on a plugin breadboard. After many trials, I finally was able to get jlink working with PlatformIO at home. I brought the project to the office, and it worked. The project I created at the office still does not work with jlink. Don’t know why, and don’t care.<\/p>\n\n\n\n
PlatformIO does not know about ESP-PROG2, but no worries. Use esp-bridge. That worked for me.<\/p>\n\n\n\n
Again, inside the PlatformIO.ini file:<\/p>\n\n\n\n
[env:esp32doit-devkit-v1]\nplatform = espressif32\nframework = arduino\nboard = esp32doit-devkit-v1\nmonitor_speed = 115200\n# esp-bridge allows ESP-PROG2 to work\n# esp-prog2 allows for breakpoint setting while running.\n# that does appear to work with jlink, also.\ndebug_tool = esp-bridge\n#upload_protocol = esp-bridge\ndebug_init_break = tbreak setup\n\n<\/code><\/pre>\n\n\n\nThe “tbreak setup” causes a temporary breakpoint at the setup() function in the blink project.<\/p>\n\n\n\n
Warning About Bluetooth<\/h3>\n\n\n\n
I loaded the Arduino bluetooth project and compiled it and loaded it. Disaster. Monitor program showed lots of trash. Serial.println() did not work well. Single Step failed a lot. Bluetooth did not work. <\/p>\n\n\n\n
There were lots of posts on the internet complaining that Bluetooth Classic did not work. Some complaints of trash on the monitor.<\/p>\n\n\n\n
After about a dozen search queries, I found a github page that I should have located from the beginning with bluetooth classic functionality for Arduino. The project linked below contained an ino file that I was able to pull from. I ignored it at the beginning because I was using ESP-IDF and had not yet understood the .ino file format.<\/p>\n\n\n\n
(For you classic “C++” programmers, a file with .ino ending is a CPP file that is managed by the Arduino project manager. It is simply another way to package a source code file. Underneath that file is a “main.cpp” that sets up the base environment in the app_main() function which calls setup() and loop(). For ESP32, the environment running the ‘system’ is FreeRTOS. You can immediately start using FreeRTOS calls, etc. <\/p>\n\n\n\n
The main difference between original FreeRTOS and this version (which was modified to support dual-core processors) is a processor core affinity. You chose which core you want your task to run on. Be mindful to use flags and semaphores to coordinate data transfers.)<\/p>\n\n\n\n
Include the <Arduino.h> in your file and the correct bluetooth includes, and you can start using Bluetooth. You may or may not have to use PlatformIO to bring in libraries. After a certain amount of mucking around, stumbling in the dark, I was able to get bluetooth to work.<\/p>\n\n\n\n
Here is the page and project link: <\/p>\n\n\n\n