Skip to content

Consider read-only data when determining where flash starts #92

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

Open
pekangas opened this issue May 28, 2025 · 0 comments · May be fixed by #93
Open

Consider read-only data when determining where flash starts #92

pekangas opened this issue May 28, 2025 · 0 comments · May be fixed by #93

Comments

@pekangas
Copy link

The current logic to determine flash start address finds the first executable segment and considers that as the start of data that goes into flash. This breaks if the CRT0 header goes into a data segment instead. The easiest fix seems to be to consider all read-only segments, not just executable ones, as flash.

This works for all the use cases I have, but there may be unintended consequences if I missed something?

@pekangas pekangas linked a pull request May 28, 2025 that will close this issue
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 a pull request may close this issue.

1 participant