3 ms·
The most thoroughly commented linker script (probably)
- cozzyd 6y agoThis would have been really useful for me about a year ago :). (although https://interrupt.memfault.com/blog/how-to-write-linker-scripts-for-firmware https://interrupt.memfault.com/blog/how-to-write-linker-scri... is pretty good too)). One thing I see not mentioned here is setting up a section specifically for debug functions you don't want to be dropped by the linker (functions you never call, except when abusing gdb as a repl for debugging).
- jaytaylor 6y agoIn case, for some weird reason, you prefer Twitter format to blog: https://twitter.com/theavalkyrie/status/1349458442734469123 https://twitter.com/theavalkyrie/status/1349458442734469123 Also as a github README: https://github.com/theacodes/Winterbloom_Castor_and_Pollux/blob/main/firmware/scripts/samd21g18a.ld https://github.com/theacodes/Winterbloom_Castor_and_Pollux/b...
- dmitrygr 6y ago> The Cortex-M allows changing > the vector table after > initialization This is actually an optional feature, and not all Cortex-M parts implement it. All Cortex-M0 do not, some Cortex-M0+ also do not. Most Cortex-M3+ do. But Author keeps saying "Cortex-M0" which do not. Also, the part she is talking about is a Cortex-M0+ not a Cortex-M0 (big difference)