fix(examples): increase partition table offset for sysview heap log on ESP32-H4

The example enables CONFIG_ESP_SYSTEM_USE_FRAME_POINTER, which pushes the
bootloader to 0x6020 bytes on ESP32-H4. That exceeds the 0x6000 budget
available with the default partition table offset of 0x8000, breaking the
build for both the app_trace_jtag and app_trace_uart CI configurations.

Move the partition table to 0x10000 on ESP32-H4, same as already done for
ESP32-P4, and drop the now stale "only overflowed on P4" note. Tell OpenOCD
the matching app image offset so GDB can map flash on both chips.
This commit is contained in:
Marius Vikhammer
2026-09-03 11:06:31 +08:00
parent dd14ea0742
commit 632911cfb7
3 changed files with 5 additions and 2 deletions

View File

@@ -33,7 +33,8 @@ def _test_examples_sysview_tracing_heap_log(openocd_dut: 'OpenOCD', idf_path: st
time.sleep(1) # Wait for the USJ port to be ready
dut.expect_exact('example: Ready for OpenOCD connection', timeout=5)
with openocd_dut.run() as oocd:
if dut.target == 'esp32p4':
# PARTITION_TABLE_OFFSET=0x10000 moves the factory app to 0x20000
if dut.target in ('esp32p4', 'esp32h4'):
oocd.write('esp appimage_offset 0x20000')
with (
open(gdb_logfile, 'w') as gdb_log,

View File

@@ -0,0 +1,2 @@
# Increase size of bootloader due to frame pointer.
CONFIG_PARTITION_TABLE_OFFSET=0x10000

View File

@@ -1,2 +1,2 @@
# Increase size of bootloader due to frame pointer. Only overflowed on P4.
# Increase size of bootloader due to frame pointer.
CONFIG_PARTITION_TABLE_OFFSET=0x10000