Skip to content

Conversation

@danielRep
Copy link
Member

This PR replaces the pad_load output section for a datanocopy section that has two goals:

  • Hold data to be initialized and used during early stages of the boot (e.g., barriers, img_addr) that can be rewritten in non-unified platforms, since data is typically copied from a non-volatile memory to a data RAM
  • Force the alignment in the end of the section to ensure the loadable portion of the image is page-aligned to avoid gaps. These gaps have seen to create issues on platforms such as Tricore.

@josecm josecm self-assigned this Sep 25, 2025
@josecm
Copy link
Member

josecm commented Sep 25, 2025

@danielRep are we sure aarch64 and riscv boot does not require this either?

@danielRep
Copy link
Member Author

@danielRep are we sure aarch64 and riscv boot does not require this either?

I think we should create a PR adding those changes as soon as we have platforms to test it, no?

@josecm
Copy link
Member

josecm commented Sep 25, 2025

@danielRep are we sure aarch64 and riscv boot does not require this either?

I think we should create a PR adding those changes as soon as we have platforms to test it, no?

I think we can just check data sections written during boot and move them to datanocopy

@josecm josecm merged commit 36d16d5 into main Sep 26, 2025
31 checks passed
@josecm josecm deleted the fix/datanocopy branch September 26, 2025 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants