Debugging ESP32P4 Issue

[NevynSelby]

TLDR; I am attempting to use GDB with an ESP32P4 and I am having problems stepping through code.

ESP IDF: 5.4.1
Platform: M5Stack Tab 5
Chip: ESP32P4 revision 1.0
GDB version: GNU gdb (esp-gdb) 14.2_20240403

I am using the M5Stack User demo code https://github.com/m5stack/M5Tab5-UserDemo in order to understand the hardware on the device. I have managed to build and deploy the code no problems. Next up, using the debugger to step through some of the code.

I use the command idf.py openocd gdb to kick off a debugging session and the debugger connects fine. So I set a breakpoint and continue, the breakpoint is hit and the debugger shows the code to be executed.

So far, so good.

I have then tried to step through the code using step and next and these both fail. GDB appears to indicate that it is still on the same line of code as the breakpoint.

I have also tried to use the continue command to continue the application and this also fails.

Another thing I have tried is to delete the breakpoint I created when the debugger stops and then stepping or continuing the code. This does not work either.

Any suggestions would be welcomed.

Thanks in advance,
Mark

[michalk]

Which board are you using? If you are connected via UART, you won't get the usb-jtag capability. You need to connect to the native USB D+, D- pins.
Also, it's not clear to me at the moment that the P4 firmware supports JTAG even though the hardware is there. It's something I'm working through myself.

[NevynSelby]

I am using the M5Stack Tab5 https://docs.m5stack.com/en/core/Tab5.

Looking at the schematic and block diagram, the USB C connector is connected to USB1 D+/D- (block diagram, page 1) and this maps to GPIO24 and 25 (schematic, Page 2, bottom right corner of the chip).

I have UART output from the application and debugging through the same USB port.

Regards,
Mark