Search found 12 matches

by espnoob
Mon Feb 06, 2023 3:28 pm
Forum: ESP-IDF
Topic: The C++17 version of the Xtensa C++ compiler supports designated initializers?
Replies: 2
Views: 1712

Re: The C++17 version of the Xtensa C++ compiler supports designated initializers?

GNU extensions? You could try to pass "-pedantic" to g++. That would prohibit extensions to the Standard.
by espnoob
Mon Dec 12, 2022 12:39 pm
Forum: ESP-IDF
Topic: [Solved] Read flash memory in debugger (incl. reserved regions)
Replies: 5
Views: 2805

Re: Read flash memory in debugger (incl. reserved regions)

Hello Sprite, thanks for the pointers. Indeed, some data can be dumped with "mon flash read_bank"; for just printing to the screen "mon flash mdb" seems to work fine, too. I still seem to miss something: suppose I have a custom partition table with an entry for data at offset 0xF000 and suppose that...
by espnoob
Mon Dec 12, 2022 6:30 am
Forum: ESP-IDF
Topic: [Solved] Read flash memory in debugger (incl. reserved regions)
Replies: 5
Views: 2805

Re: Read flash memory in debugger (incl. reserved regions)

Nothing?
Printing flash memory should be possible (for internal memory, but also for external memory because it is mapped into address space).

Maybe the MMU interferes during runtime?
by espnoob
Fri Dec 09, 2022 11:00 am
Forum: ESP-IDF
Topic: [Solved] Read flash memory in debugger (incl. reserved regions)
Replies: 5
Views: 2805

[Solved] Read flash memory in debugger (incl. reserved regions)

Hi,

is it, in principle, possible to read flash memory in GDB?

I have tried to print the partition table at address 0x8000. But only zeros are returned.
The chip in question is an ESP32S3 with 32MB external flash memory.

Maybe some lowlevel openocd command can be used?

Thanks!
by espnoob
Fri Nov 04, 2022 10:45 am
Forum: ESP-IDF
Topic: [Solved] ESP32S3 SPIRAM: Reading memory in GDB returns always zeros
Replies: 10
Views: 6276

Re: ESP32S3 SPIRAM: Reading memory in GDB returns always zeros

Just add `mon xtensa set_permissive 1`
Thanks. Can confirm that this works around the issue: memory is now readable and writable.
by espnoob
Thu Nov 03, 2022 11:58 am
Forum: ESP-IDF
Topic: [Solved] ESP32S3 SPIRAM: Reading memory in GDB returns always zeros
Replies: 10
Views: 6276

Re: ESP32S3 SPIRAM: Reading memory in GDB returns always zeros

I modified the "hello-world" example to make the issue visible. It allocates a buffer and sets the first byte. Then it continues to dump a region from the buffer. Note, that the modified example uses `heap_caps_malloc` but it behaves the same with plain malloc. /* Hello World Example This example co...
by espnoob
Thu Nov 03, 2022 9:58 am
Forum: ESP-IDF
Topic: [Solved] ESP32S3 SPIRAM: Reading memory in GDB returns always zeros
Replies: 10
Views: 6276

Re: ESP32S3 SPIRAM: Reading memory in GDB returns always zeros

Sorry to check the obvious things too late, but with the latest release version of openocd the issue persists. And further infos/test results: The allocated buffer is part of a struct, and the struct is in internal memory `0x3fcb1298` From GDB I cannot set any value in the malloc'd buffer: "Cannot a...
by espnoob
Thu Nov 03, 2022 8:53 am
Forum: ESP-IDF
Topic: Replacing encrypted app, causes "No MD5" partition error: why?!
Replies: 16
Views: 9253

Re: Replacing encrypted app, causes "No MD5" partition error: why?!

Sorry to hijack the thread, but there is an interesting question that I did not see an explicit answer for. This "encryption-aware" concept really does not make any sense. You are suggesting if you have a working "plain text" app installed, and then you turn on the built-in encryption process, the w...
by espnoob
Wed Nov 02, 2022 1:15 pm
Forum: ESP-IDF
Topic: [Solved] ESP32S3 SPIRAM: Reading memory in GDB returns always zeros
Replies: 10
Views: 6276

Re: ESP32S3 SPIRAM: Reading memory in GDB returns always zeros

Hi Alexey, thanks for the info. What OpenOCD version do you use? The version of openocd is `Open On-Chip Debugger v0.11.0-esp32-20220411` from the latest stable IDF 4.4.2. I allocate memory with 'heap_caps_malloc', initiliaze it with 'memset' to '0xEA'. OK, that is another difference: I use plain `m...