Debugging Support on ESP32-P4 Functional EV BoardV1.5.2

SachinGowda
Posts: 1
Joined: Wed Jul 23, 2025 2:49 pm

Debugging Support on ESP32-P4 Functional EV BoardV1.5.2

Postby SachinGowda » Wed Jul 23, 2025 3:10 pm

Hello,
I am currently working with the ESP32-P4 Functional EV board (version 1.5.2) and attempting to enable debugging via the inbuilt USB Serial JTAG interface(port) using Visual Studio Code and the ESP-IDF environment.

I have followed the steps outlined in your documentation for JTAG debugging:
https://docs.espressif.com/projects/esp ... -interface


I was able to run OpenOCD successfully and reached the expected output as mentioned. Please refer the attached image from my terminal output(has somme error for cpu 1): I have attached my terminal output

Next step, I proceeded with configuring debugging in Visual Studio Code, following the guide below:
https://docs.espressif.com/projects/vsc ... oject.html
The required drivers were installed automatically. However, when I attempt to start the debugger (after selecting the appropriate board/esp32p4-builtin.cfg), I encounter persistent errors in the debug console

I am using ESP-IDF Debug:Launch for debugging(in launch.json), I have also tried using Eclipse CDT GDB adaptor, but still throws similar issue
I have attached the settings.json to show how I have configured

I have carefully applied the suggested configurations in both settings.json and launch.json, as per the document. I have also worked around board/esp32p4-builtin.cfg file and other related settings in these files and I’ve also tried multiple launch configurations, but all attempts lead to similar errors

Could you help me identify any potential misconfigurations or limitations that may be causing this issue?

Any insights or guidance would be greatly appreciated, as resolving this would significantly support our development workflow.
Attachments
settings_json.txt
it is a json file changed it to txt for uploading purpose
(2.3 KiB) Downloaded 16 times
debug_console.png
Debug console output
debug_console.png (14.88 KiB) Viewed 1096 times
terminal_output.png
Terminal output file
terminal_output.png (48.18 KiB) Viewed 1096 times

Jörg1063
Posts: 3
Joined: Tue Dec 02, 2025 3:20 pm

Re: Debugging Support on ESP32-P4 Functional EV BoardV1.5.2

Postby Jörg1063 » Tue Dec 02, 2025 4:33 pm

I have the same problem. Is there any solution? Is there any step-by-step advice? A working example?
I'm using ESP_Brookesia_Phone.
Thank you for any help!
I'm using the
launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "ESP-IDF Debug: Launch",
"type": "espidf",
"request": "launch",
"logFile": "${workspaceFolder}/gdb.log"
}
]
}

Errormessage:
Memory Map (6 regions):
----------------------------------------
Type Start Addr
Length BlockSize
----------------------------------------
FLASH 0x00000000 0x01000000 0x00001000
R/W 0x01000000 0x4ec00000 0x00000000
ROM 0x4fc00000 0x00020000 0x00000000
R/W 0x4fc20000 0x004e0000 0x00000000
ROM 0x50100000 0x00004000 0x00000000
R/W 0x50104000 0xafefc000 0x00000000
----------------------------------------

❌ Error: [esp32p4.hp.cpu0] Failed
❌ to read memory (addr=0x48192f80)
Error: [esp32p4.hp.cpu0] progbuf=failed, sysbus=failed, abstract=failed

❌ Error: [esp32p4.hp.cpu0] Failed to r
❌ ead memory (addr=0x48192f94)
Error: [esp32p4.hp.cpu0] progbuf=failed, sysbus=failed, abstract=failed

Info : JTAG tap: esp32p4.tap0 tap/device found
: 0x00012c25 (mfg: 0x612 (Espressif Systems), part: 0x0012, ver: 0x0)
Info : JTAG tap: esp32p4.tap1 tap/device found: 0x00012c25 (mfg: 0x612 (Espressif Systems), part: 0x0012, ver: 0x0)

Who is online

Users browsing this forum: ChatGPT-User and 11 guests