Debugging ESP32-S3-DevKitC-1.1 on native USB interface misses print output
Posted: Thu Jun 06, 2024 9:15 pm
Hi,
I am debugging ESP32-S3-DevKitC-1.1 with a single USB cable, connected to the native USB connector of the Kit (not UART).
I can upload compiled code, obtain output on the Serial Monitor (printf using HWCDC) and invoke the debugger.
If I leave the code to run without breakpoints on the debugger I will get all the printf output the code is generating, on Serial Monitor.
My problem is that when I do interactive debug (the usefull debug), which includes stopping, resuming and changing breakpoints, I loose almost all output from the Serial.printf(..) commands. First I thought I had to use Serial.flush() after each group of Serial.printf(..) commands, but this did not solve it. I tried with different handshake options on Serial Monitor and on the PC COM port, without any better behaviour.
Any idea if interactive debugging and Serial.Printf can coexist without loosing characters or strings?
Regards
I am debugging ESP32-S3-DevKitC-1.1 with a single USB cable, connected to the native USB connector of the Kit (not UART).
I can upload compiled code, obtain output on the Serial Monitor (printf using HWCDC) and invoke the debugger.
If I leave the code to run without breakpoints on the debugger I will get all the printf output the code is generating, on Serial Monitor.
My problem is that when I do interactive debug (the usefull debug), which includes stopping, resuming and changing breakpoints, I loose almost all output from the Serial.printf(..) commands. First I thought I had to use Serial.flush() after each group of Serial.printf(..) commands, but this did not solve it. I tried with different handshake options on Serial Monitor and on the PC COM port, without any better behaviour.
Any idea if interactive debugging and Serial.Printf can coexist without loosing characters or strings?
Regards