Hello everyone.
const char my_custom_text[32] instead of const char *my_custom_text has moved from the 0x3000+ range to 0x120.
Thank you all for your support.
Search found 3 matches
- Thu Oct 02, 2025 1:38 pm
- Forum: General Discussion
- Topic: Unexpected offset when using .rodata_custom_desc section
- Replies: 5
- Views: 1995
- Mon Sep 22, 2025 4:25 pm
- Forum: General Discussion
- Topic: Unexpected offset when using .rodata_custom_desc section
- Replies: 5
- Views: 1995
Re: Unexpected offset when using .rodata_custom_desc section
I can find the "Hello World 123" string in the generated .bin file, but not at the offset expected according to the Espressif documentation.
At what offset did you expect to find the string? According to what documentation?
As you don't specify a section to place the string literal in, it ...
- Fri Sep 19, 2025 11:41 am
- Forum: General Discussion
- Topic: Unexpected offset when using .rodata_custom_desc section
- Replies: 5
- Views: 1995
Unexpected offset when using .rodata_custom_desc section
Hi everyone,
I’m planning to use the .rodata_custom_desc dedicated memory section to store basic device information. The goal is to allow a third-party software to read the generated .bin and identify this information.
Following the Espressif official documentation, I implemented the following ...
I’m planning to use the .rodata_custom_desc dedicated memory section to store basic device information. The goal is to allow a third-party software to read the generated .bin and identify this information.
Following the Espressif official documentation, I implemented the following ...