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

riscv-rt: adapt linker file to look more like cortex-m-rt's #238

Open
romancardenas opened this issue Nov 1, 2024 · 1 comment
Open

Comments

@romancardenas
Copy link
Contributor

romancardenas commented Nov 1, 2024

I suggest adopting part of cortex-m-rt structure:

Make link.x include memory.x

In this way, PACs and BSPs would have to provide a memory.x linker file that defines the memory layout and regions.

End users would need to do something like RUSTFLAGS="-C link-arg=-Tlink.x when building binaries, regardless of the final target.

Keep using region aliases

I think the current riscv-rt approach is quite versatile and I don't see any advantage in limiting sections to FLASH and RAM.

Use __ to define start and end of sections

I think it is a good idea to follow the same naming convention as in cortex-m-rt (__stext, __etext...).

@romancardenas
Copy link
Contributor Author

More information in #236

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

No branches or pull requests

1 participant