RIOT/cpu/msp430/ldscripts/riot-msp430f1612.ld

INCLUDE msp430f1612.ld
INCLUDE msp430_common.ld
INCLUDE msp430_x1xx.ld
INCLUDE xfa.ld
cpu/msp430_common: Fix linking with binutils 2.40 An `INSERT AFTER` directive no longer can refer to a different linker script included with `-T path/to/script.ld`. Instead, this adds wrapper linker scripts that just `INCLUDE` the three individual linker scripts. This way, the xfa.ld can safely refer back to sections defined in the vendor linker script. For some reason, this approach cause the exact issue it fixes for binutils 2.40 with the binutils in the CI. We stick with the old linker flags with binutils prior 2.40 to be compatible with both conflicting behaviors. The best approach would be to come up with something that works across different versions of binutils; but no such solution materialized. 2023-04-19 17:46:17 +02:00			`INCLUDE msp430f1612.ld`
			`INCLUDE msp430_common.ld`
cpu/msp430: make use of vendor header files The MSP430 vendor files already provide macros containing register constants and symbols (provided via linker scripts) containing addresses of peripheral registers. So lets make use of that rather than maintaining a long list of constants. 2023-06-14 16:18:15 +02:00			`INCLUDE msp430_x1xx.ld`
cpu/msp430_common: Fix linking with binutils 2.40 An `INSERT AFTER` directive no longer can refer to a different linker script included with `-T path/to/script.ld`. Instead, this adds wrapper linker scripts that just `INCLUDE` the three individual linker scripts. This way, the xfa.ld can safely refer back to sections defined in the vendor linker script. For some reason, this approach cause the exact issue it fixes for binutils 2.40 with the binutils in the CI. We stick with the old linker flags with binutils prior 2.40 to be compatible with both conflicting behaviors. The best approach would be to come up with something that works across different versions of binutils; but no such solution materialized. 2023-04-19 17:46:17 +02:00			`INCLUDE xfa.ld`