kinetis: Share ldscripts between CPUs#2393
Conversation
|
See https://github.com/gebart/RIOT/tree/wip/k60-initial for a working example (cpu/k60 and boards/mulle) |
|
This may be something that we will want to change: In this ldscript, the heap is its own section which uses up all remaining memory, so the .bss size will seem very high when using |
|
@gebart It's not as easy as I thought. What do you think of this:
If it's ok, then I will open a PR against your branch. |
OK
I agree
I agree
I agree However, there is a distinction between sram_l and sram_u in hardware, but I think it will only be of importance if you use ramcode. You can open a PR against this branch with your changes. |
|
The proposed changes from @jfischer-phytec-iot is now merged into this PR. |
|
yep |
28b436a to
29d3959
Compare
|
squashed and rebased on latest master |
kinetis: Share ldscripts between CPUs
We decided it would be a good idea to share the base of the linker scripts between the different Kinetis CPUs since they share the same memory layout.
Use the following as a template for the CPU-specific part of the ldscript:
sram_l is currently only used for accelerating code execution, .ramcode section.
sram_u is used for all variables (.data and .bss)
Add the following to the cpu-specific Makefile.include: