Thanks, you are right. "oszlopdisp-mx.elf.ld" is regenerated even when Auto linker script is OFF. And this generated script has a recursive call: it has a line
INCLUDE "D:\MUNKA\Tekinvest\OszlopDisp\Prog\Projects\MDK-ARM\oszlopdisp-mx Configuration\oszlopdisp-mx.elf.ld"
to include itself.
I think the problem is that the single line
STARTUP("startup_stm32f4xx.o")
in that script gets doubled because of recursive include.  Is it a bug at script generation?
What to do?
- Is there any "#ifdef" kind of solution in linker scripting language to avoid double include?
- Can I disable re-generating this file (to keep manually edited script)?
- If I run ld.exe manually with parameters script will not be re-generated (is it done by Ride IDE)?

I attach the script "D:\MUNKA\Tekinvest\OszlopDisp\Prog\Projects\MDK-ARM\oszlopdisp-mx Configuration\oszlopdisp-mx.elf.ld":

/*
!!! Primary linker script file generated automatically !!!
This file contains the input and output files names
It also includes the secondary/main linker script that is specified in the Ride options (default or custom)
*/

SEARCH_DIR(".")
SEARCH_DIR("oszlopdisp-mx Configuration")
SEARCH_DIR("C:\Program Files\Raisonance\Ride\Lib\ARM")
STARTUP("startup_stm32f4xx.o")
INPUT("oszlopdisp-mx Configuration\bsp_driver_sd.o")
INPUT("oszlopdisp-mx Configuration\main.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_msp.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_it.o")
INPUT("oszlopdisp-mx Configuration\usb_device.o")
INPUT("oszlopdisp-mx Configuration\usbd_conf.o")
INPUT("oszlopdisp-mx Configuration\usbd_desc.o")
INPUT("oszlopdisp-mx Configuration\tft.o")
INPUT("oszlopdisp-mx Configuration\system_stm32f4xx.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_cortex.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_crc.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_dma.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_dma2d.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_dma_ex.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_flash.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_flash_ex.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_flash_ramfunc.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_gpio.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_iwdg.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_ltdc.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_nand.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_pcd.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_pcd_ex.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_pwr.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_pwr_ex.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_rcc.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_rcc_ex.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_sd.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_sdram.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_tim.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_tim_ex.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_hal_uart.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_ll_fmc.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_ll_sdmmc.o")
INPUT("oszlopdisp-mx Configuration\stm32f4xx_ll_usb.o")
INPUT("oszlopdisp-mx Configuration\diskio.o")
INPUT("oszlopdisp-mx Configuration\sd_diskio.o")
INPUT("oszlopdisp-mx Configuration\ff.o")
INPUT("oszlopdisp-mx Configuration\ff_gen_drv.o")
INPUT("oszlopdisp-mx Configuration\ccsbcs.o")
INPUT("oszlopdisp-mx Configuration\syscall.o")
INPUT("oszlopdisp-mx Configuration\usbd_hid.o")
INPUT("oszlopdisp-mx Configuration\usbd_core.o")
INPUT("oszlopdisp-mx Configuration\usbd_ctlreq.o")
INPUT("oszlopdisp-mx Configuration\usbd_ioreq.o")
GROUP(
"smallprintf_thumb_fpu.a"
"Cortex_SWV_io_putchar_thumb_fpu.a"
"libc_s.a"
"libm.a"

)
INCLUDE "D:\MUNKA\Tekinvest\OszlopDisp\Prog\Projects\MDK-ARM\oszlopdisp-mx Configuration\oszlopdisp-mx.elf.ld"
PROVIDE ( _Minimum_Stack_Size = 0x20 );
PROVIDE ( malloc_getpagesize_P = 0x1000 );
OUTPUT("oszlopdisp-mx Configuration\oszlopdisp-mx.elf")

and one more "anomaly" when firing up linker:

the last couple lines of Build log window after unsuccessful Make

Running: LD Linker
"C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-gcc.exe" -u _start -u _Minimum_Stack_Size  -mcpu=cortex-m4 -mthumb -specs=nano.specs -specs=nosys.specs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -Wl,-T -Xlinker "oszlopdisp-mx Configuration\oszlopdisp-mx.elf.ld" -Wl,-static -Wl,--gc-sections  -Wl,-Map -Xlinker "D:\MUNKA\Tekinvest\OszlopDisp\Prog\Projects\MDK-ARM\oszlopdisp-mx Configuration\oszlopdisp-mx.map" -N -nostartfiles -Wl,--warn-once 
c:/program files/raisonance/ride/arm-gcc/bin/../lib/gcc/arm-none-eabi/4.8.4/../../../../arm-none-eabi/bin/ld.exe: multiple STARTUP files 
collect2.exe: error: ld returned 1 exit status 
  Error Code: 0x1
 
Build failed

The "-Xlinker" option is doubled...I don't know if it causes a problem...but anomaly.

I only spread the breaking news of my "investigation":))

If I Auto generate linker script, my "oszlopdisp-mx.elf.ld" file has one include:
INCLUDE "oszlopdisp-mx Configuration\STM32F429_2048K_192K_FLASH.ld"
and compile+link is fine.

Now  I turn off auto linker script generation while Ride7 still running, and push F9 again,
"oszlopdisp-mx.elf.ld" is NOT re-generated, and "make" is still successful.

Sometimes, when "oszlopdisp-mx.elf.ld" is re-generated, the recursive line
INCLUDE "D:\MUNKA\Tekinvest\OszlopDisp\Prog\Projects\MDK-ARM\oszlopdisp-mx Configuration\oszlopdisp-mx.elf.ld"
is added, and Make ends up with "multiple STARTUP files " error.

Re-generation of "oszlopdisp-mx.elf.ld" sometimes happens after Clean Project, or manual deletion of "oszlopdisp-mx.elf.ld"...but I can't clearly see the condition whether re-generating or not.

I think this is an minor issue of Ride7 (v7.50.14.0185)

Hi,

The auto-generated .elf.ld primary script file includes the secondary file that you specified in Ride's "Script File" option. Your custom script is this secondary script file, not the primary.

If you see the primary file auto-including itself, it means that you have written the name of the .elf.ld file in Ride's "Script File" option. (and then of course the script auto-includes itself and the link has little hope to succeed )

You must change this "Script File" option (in Ride, not in a ld file) to use "STM32F429_2048K_192K_FLASH.ld" as your custom script. (and NOT the .elf.ld) Then the auto-generated script .elf.ld file will include STM32F429_2048K_192K_FLASH.ld, which itself includes three other sub-scripts. Then you'll have a custom script that provides the same result as the default script, and only then can you start modifying one or several of these four scripts. (the secondary and the sub-scripts, but not the primary .elf.ld, which will always be auto-generated.)

Concerning the fact that you see that the script is sometimes not generated, this is normal: the file is generated at every Link, not at every Make. Sometimes the Make process does not launch the link, which is what you'd expect from Make. (otherwise it would be a Build) I think that your observation of this behavior is disturbed by the fact that you have the wrong file referenced in the linker "Script File" option. Please first correct this option and the rest should be all right.

I hope it helps.

Best Regards,

Vincent