Hi @dgroch,

It is known issue with tracing on ESP32-S3 we are investigating it. Unfortunately there is no solution or workaround for it right now.
Will let you know if there is a progress on it.

Ok. Probably I see the reason. Looks like OpenOCD forbids reading from region `0x3d00000` because it is not mentioned in the esp32-s3 memory config. Workaround is to disable memory access check in OpenOCD. Just add `mon xtensa set_permissive 1` in your `gdbinit` file or somewhere in IDE debug ...

Could you collect OpenOCD log by adding `-d3 -l oocd.log` to its command line? Post it here please.

Hmm, looks like in my example heap_caps_malloc returns address from different address range "3c030900".

void *p = heap_caps_malloc(spi_block_sz, MALLOC_CAP_DEFAULT|MALLOC_CAP_SPIRAM);
assert(p);
printf("Allocated SPIRAM @ %x\n", p);
memset(p, 0xEA, spi_block_sz);


But acc to the docs it ...

Hi espnoob,

I checked this with the latest OpenOCD (https://github.com/espressif/openocd-esp32/releases/tag/v0.11.0-esp32-20221026) and it works at my side. I allocate memory with 'heap_caps_malloc', initiliaze it with 'memset' to '0xEA'.


(gdb) p/x p
$1 = 0x3c030900
(gdb) x/32bx p
0x3c030900 ...

HI,

As far as I remember we had some problems with SPIRAM data corruption on ESP32. We will check this for ESP32-S3.

Ok.

1) Could you provide information about IDF and OpenOCD versions you use?
2) What is the exact wire connection between ESP-Prog and board? Do you connect ESP-Prog's UART to module's one?
3) How board is powered up?
4) What ESP32 module do you use on ESP32-CAM and ESP32-devkitC?
5) Does problem ...

Hi sid,

Sorry for late reply.
I see that you use 500 KHz adapter clock. Do you have any special concerns on not using default 20 MHz clock?

Regards
Alexey

Hi Michael

The third unanswered question: The interface file "interface/ftdi/esp32_devkitj_v1.cfg" sets the clock speed to 20000 kHz, the board file "board/esp32s3-ftdi.cfg" changes it to 5000 kHz, is this clock changing really necessary?

No. This ambiguity will be removed in the next OpenOCD ...

Hi

Yes but in my case I don't have uart options provided in the PCB. trying via JTAG. Can anyone help??

You can use OpenOCD flash read commands http://openocd.org/doc/html/Flash-Commands.html#Erasing_002c-Reading_002c-Writing-to-Flash.

For example you can read flash with flash read_bank 0 ...