-
Notifications
You must be signed in to change notification settings - Fork 56
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
Remove CCM SRAM definitions for devices without this memory type #6
Comments
Have you considered splitting the
That
Each of these files would contain a |
I found a different approach for this. See the GH-6-refactor-linker-files branch. The linker files specific to devices contain only memory regions that the device actually has. They also contain separate regions for the different flash banks a device might have. A little bit more thought needs to go into how one may use two memory banks as one when they're next to each other in the address space. There should be an additional This also allows for defining custom sections on project level for memories like CCM. Let me know what you think of this approach. |
Well, I had seen that branch, but hadn’t known, what that I think providing some default |
Yep. Templates should work out of the box after completing the setup guide. This means that the templates will have to be updated to include a default config.ld. And there needs to be documentation on how to make changes to the config.ld. |
That is, that default |
Yes, I think there will be actual |
All linker scripts currently contain a definition for CCM SRAM. A lot of devices do not have this type of SRAM.
Look into the possibilities of omitting this definition for devices without CCM SRAM. For example, does
ld
throw an error when it is omitted? Or are there options to conditionally execute parts of linker scripts?The text was updated successfully, but these errors were encountered: