I need to relocate the entire .data section of my code to a different portion of RAM. I can use my own .ld linker scripts for that, but then it won't work with redlib, and therefore my flasher will not flash using the onboard LinkServer compatible flashing circuitry.
So I need to be able to do this and keep redlib in the mix. The problem is that I am already reallocating everything significant that I have access to using __attribute__((section(...)). to do it manually, but it's not enough.
What can I do here? The simplest thing - which compiles and links, but won't flash, seems to be to use a custom linker script, but again it won't flash with that option.
Curiously, the build output shows -T"mylinkerscript.ld" even though it's not using it.
Maybe my other option is to use a different flashing mechanism, probably involving reflashing the bootloader to use something else, but I have no idea where to begin and it seems less than ideal.
Any help would be appreciated
Memory region Used Size Region Size %age Used
SRAM_DTC_cm7: 389804 B 256 KB 148.70%
SRAM_ITC_cm7: 167324 B 256 KB 63.83%
SRAM_OC1: 57984 B 512 KB 11.06%
SRAM_OC2: 160 KB 512 KB 31.25%
SRAM_OC_ECC1: 0 GB 64 KB 0.00%
SRAM_OC_ECC2: 0 GB 64 KB 0.00%
SRAM_OC_cm7: 0 GB 128 KB 0.00%
collect2.exe: error: ld returned 1 exit status
Make sure to follow the steps shown on the following blog post in order to better manage your linker scripts and prevent errors when changing them: Placing Code in Sections with managed GNU Linker Scripts | MCU on Eclipse
I hope this helps.
BR,
Edwin.