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

Allow to specify maximum ROM size #2042

Closed
fooker opened this issue Feb 4, 2020 · 2 comments
Closed

Allow to specify maximum ROM size #2042

fooker opened this issue Feb 4, 2020 · 2 comments

Comments

@fooker
Copy link
Contributor

fooker commented Feb 4, 2020

The new mechanism to generate linker scripts does not allow to specify a maximum ROM size.

I used to limit the irom0_0_seg length to (1M / 2 - 0x2010) which allows to ensure that the first rom will now overwrite the second one. For me, both ROMs should have the same 0x2010 offset from the base addresses (0x00000 for ROM 0 and 0x80000 for ROM 1). The remaining space between the two ROMs is used to store some persistent data.

It would be nice to have a way to specify this limit again. Or as an alternative, overwrite the generative linker scripts with provided ones.

@fooker
Copy link
Contributor Author

fooker commented Feb 5, 2020

See #2044 for a possible solution.

@slaff
Copy link
Contributor

slaff commented Mar 26, 2021

With the arrival of (partition tables)[https://sming.readthedocs.io/en/latest/_inc/Sming/Components/Storage/index.html] this should be possible. Feel free to re-open this ticket if you have problems achieving what you want with the latest develop version.

@slaff slaff closed this as completed Mar 26, 2021
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

2 participants