Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

boot: espressif: iram_loader_seg overlapping with Zephyr app RAM #2191

Open
naNEQ opened this issue Jan 28, 2025 · 1 comment
Open

boot: espressif: iram_loader_seg overlapping with Zephyr app RAM #2191

naNEQ opened this issue Jan 28, 2025 · 1 comment
Assignees
Labels
area: espressif Affects the Espressif port

Comments

@naNEQ
Copy link

naNEQ commented Jan 28, 2025

I'm only referring to the esp32s3 SOC, but this might be relevant for other Espressif SOCs too.

The bootloader iram_loader_seg is defined to start from 0x403BA000 (which translates to 0x3FCCA000).

In Zephyr, starting from releases 3.7.0 and onwards, the DRAM section of the app finishes at 0x3FCD6400 (it used to be 0x3FCCA000 up until releases 3.6.0).

That creates a not allowed overlap, since "the app may use RAM for static allocations up to the start of iram_loader_seg" (link).

I suggest changing the memory allocation for the bootloader to (keeping the section sizes the same):

iram_seg (RWX) :                  org = 0x403BC400, len = 0xA000
iram_loader_seg (RWX) :      org = 0x403C6400, len = 0x6000
dram_seg (RW) :                   org = 0x3FCDC400, len = 0x9A00
@almir-okato
Copy link
Collaborator

I'll take a look. It's on the plans improving this memory map acknowledge to the OSes.

@de-nordic de-nordic added the area: espressif Affects the Espressif port label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: espressif Affects the Espressif port
Projects
None yet
Development

No branches or pull requests

3 participants