cancel
Showing results for 
Search instead for 
Did you mean: 

different ld files generated, file name xx.ld (lower case) vs XX.ld

Mario Luzeiro
Senior

STM32CubeMX generates by default a xx.ld file.

It has copyrights from 2023. However, if I set "Apply Application Regions Settings to Linker File", it will generate a file with 2025 copyright, different template, also with XX.ld case, which on Linux, will give issues.

 

Version 6.16.1

1 ACCEPTED SOLUTION

Accepted Solutions

Hello @Mario Luzeiro 

Your contribution is much appreciated.

ticket 226560 has been escalated to dev for further investigation.

I will keep you posted with updates.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

8 REPLIES 8
Ghofrane GSOURI
ST Employee

Hello @Mario Luzeiro 

I'm currently investigating this behavior. I will get back to you ASAP.

Could you please explain what issue you are facing because of this behavior?

Thx

Ghofrane 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.


Could you please explain what issue you are facing because of this behavior?

Its the inconsistency of the case in the file name.

Eventually, I can workaround it and it wont cause issues, but:

 


X.ld case, which on Linux, will give issues.

STM32CubeMX by default generates a MCU_xx_FLASH.ld file.

With "Apply Application Regions Settings to Linker File", it will generate a MCU_XX_FLASH.ld

STM32CubeMX cmake uses MCU_xx_FLASH.ld file.

On Linux, case file name matters.
I have to delete MCU_xx_FLASH.ld and rename MCU_XX_FLASH.ld to MCU_xx_FLASH.ld (also because I'm already tracking MCU_xx_FLASH.ld), every time I generate code on STM32CubeMX.

Eventually I can start use upper case version

 

mfgkw
Senior III

As a workaround (until ST solves it) you could try:

- delete one of the files

- replace it with a sym link (ln -s remaining_file deleted_file) to the other file OR make a hard link (cp -l remaining_file deleted_file)

 

Hello @Mario Luzeiro 

Which toolchain and MCU that you are using ?

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

toolchain? does not matter, I guess? I'm using latest version of STM32CubeMX on Linux, which is what generates the files.

MCU: STM32H562

 

This is no big deal, no need for workarrounds, I was just reporting the issue, hopping it will be fixed.

Hello @Mario Luzeiro 

To clarify, which of those options did you choose for code generation?

GhofraneGSOURI_0-1770127735594.png

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Hello @Mario Luzeiro 

Your contribution is much appreciated.

ticket 226560 has been escalated to dev for further investigation.

I will keep you posted with updates.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.