-
Notifications
You must be signed in to change notification settings - Fork 100
Generate layout.ld from templates + data #408
base: master
Are you sure you want to change the base?
Conversation
1 similar comment
Looks like rebuilding everything for every example is starting to bit us in the butt a little. Might have to split each example in to it's own travis matrix now, which would... suck to say the least. Or at least provide a way to build example subsets until we could finally use cargo's |
@farcaller I'm gonna hold off on this until we can fix the build times issue, especially since it doesn't truly add a ton of value quite yet until the generator can get more advanced. |
@@ -0,0 +1,3 @@ | |||
--- | |||
vectors: rom | |||
memories: [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This naming is slightly awkward. Why not memory_ranges
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. Much better.
Fix #329
Obvously,
k20
is still a special case, but I think this gives a good base on which to build a generator that will work generically accross all supported MCUs. (We still have #109) to track thek20
layout in.I would make an attempt, but I don't have a k20 board or anything, so maybe @bgamari could take a look at some additions to this generator?
I think the way forward is to have like
flash_config: Option[McuFlashConfig]
inMcuLayout
and thenstruct McuFlashConfig { ... }
elsewhere... but that could be a naive solution that I just came up with at first glance.